attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Hi Mike,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Michael Sweet <msweet@msweet.org> <br>
<b>Sent:</b> Tuesday, March 2, 2021 1:13 PM<br>
<b>To:</b> Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com><br>
<b>Cc:</b> PWG IPP Workgroup <ipp@pwg.org><br>
<b>Subject:</b> Re: [IPP] IPP Registration Request for Addition: New keywords for the "media" attribute<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Smith,<br>
<br>
At first blush I see some duplicated sizes from the registry:<br>
<br>
na_arch-c_18x24in<br>
na_arch-d_24x36in<br>
<br>
and the MSN2 spec doesn't allow those...<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><i><span style="color:#1F497D">[Smith K.] I know we have in the past agreed to not register certain new media keywords because their dimensions were redundant with others already registered. The recent discussion
about media “family” grouping has made me question that. (I’m also having a hard time finding the clauses in PWG 5101.1-2013 that mandates the “no size redundancy” restriction.)<o:p></o:p></span></i></b></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><i><span style="color:#1F497D">If a Client were implemented to present supported media using a hierarchical system where families are grouped together (e.g. Architectural, Photo, etc.) and the Printer vendor
wanted that Client to offer the user both an “Architectural C” in the Architectural family and a “Super C” in the Photo family, this would be impossible using only the “media-supported” attribute without the Client knowing a-priori that na_arch-c_18x24in should
be shown in two different places and with two different strings (which the Client presumably provides since the Printer can only provide one localized string in its message catalog for a given keyword).<o:p></o:p></span></i></b></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><i><span style="color:#1F497D">If the Client were implemented to use “media-col-database” rather than “media-supported”, the “media-key” value for the two variants could both use “na_arch-c_18x24in” and then
I suppose the “Super C” could have some suffix on it (‘na_arch-c_18x24in_photo-super-c’) to make it unique, and that would then provide a unique key in the message catalog so it could have a different label. But we would still have no standard solution for
the family problem, though.</span></i></b><br>
<br>
Also, while I appreciate keeping the na_WIDTHxHEIGHT_WIDTHxHEIGHTin form for those dimensional sizes, if they are primarily for photo/art printing I'd like to see a 'photo' prefix in the name portion, e.g.:<br>
<br>
oe_photo-16x20_16x20in<br>
<br>
Similarly, the om_photo sizes should include the dimensions if there is no corresponding well-known name:<br>
<br>
om_photo-300x400_300x400mm<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><i><span style="color:#1F497D">[Smith K.] I don’t have a problem with this recommendation in principle, but I’d like to see it codified in an update to MSN2. Seeking information on the “oe_10x12_10x12in”
and such – more soon.<o:p></o:p></span></i></b></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
> On Mar 2, 2021, at 12:29 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <<a href="mailto:ipp@pwg.org">ipp@pwg.org</a>> wrote:<br>
> <br>
> Greetings,<br>
> <br>
> HP Inc. is requesting the registration of additional keywords for the “media” attribute [STD92] for some standard sizes that aren’t yet registered. Here is the registration template and the keywords to be added:<br>
> <br>
> Attributes (attribute syntax)<br>
> Keyword Attribute Value Reference<br>
> -------------------------------------------------------- --------------<br>
> media (type2 keyword | name(MAX)) [RFC8011]<br>
> na_arch-e1_32x40in [HP20210302]<br>
> na_super-c_18x24in [HP20210302]<br>
> na_super-d_24x36in [HP20210302]<br>
> oe_10x12_10x12in [HP20210302]<br>
> oe_10x15_10x15in [HP20210302]<br>
> oe_14x18_14x18in [HP20210302]<br>
> oe_16x20_16x20in [HP20210302]<br>
> oe_20x24_20x24in [HP20210302]<br>
> oe_22x28_22x28in [HP20210302]<br>
> oe_24x30_24x30in [HP20210302]<br>
> om_photo_300x400mm [HP20210302]<br>
> om_photo_300x450mm [HP20210302]<br>
> om_photo_350x460mm [HP20210302]<br>
> om_photo_400x600mm [HP20210302]<br>
> om_photo_500x760mm [HP20210302]<br>
> om_photo_600x900mm [HP20210302]<br>
> media-supported (1setOf (type2 keyword | name(MAX))) [RFC8011]<br>
> < all name values > [RFC8011]<br>
> <br>
> Let me know if there are any issues.<br>
> <br>
> Cheers,<br>
> Smith<br>
> <br>
> /**<br>
> Smith Kennedy<br>
> HP Inc.<br>
> */<br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> ipp mailing list<br>
> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
> <a href="https://www.pwg.org/mailman/listinfo/ipp">
https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br>
________________________<br>
Michael Sweet<br>
<br>
<b><i><span style="color:#1F497D"><o:p></o:p></span></i></b></p>
</div>
</div>
</body>
</html>