attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Mike,<div class="">
<div><br class=""><blockquote type="cite" class=""><div class="">On Jul 27, 2022, at 7:52 AM, Michael Sweet <<a href="mailto:msweet@msweet.org" class="">msweet@msweet.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">CAUTION: EXTERNAL SENDER WARNING. This email originated from outside of the HP organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.<br class=""><br class=""><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Michael Sweet <<a href="mailto:msweet@msweet.org" class="">msweet@msweet.org</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[EXTERNAL SENDER]: Re: [IPP] Update IANA registry in advance of errata resolution for Issue #113?</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">July 27, 2022 at 7:52:01 AM PDT<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Michael Sweet <<a href="mailto:msweet@msweet.org" class="">msweet@msweet.org</a>>, PWG IPP Workgroup <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">Cc: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"Kennedy, Smith (Wireless & IPP Standards)" <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>><br class=""></span></div><br class=""><br class=""><div class="">Following up to my own post (and thanks to Steven Young for finding this for me :) - PWG 5101.1 does actually talk about a long dimension of 0 for roll sizes in sections 5.1 and 5.1.3. Specifically, when the roll size is unknown or unbounded, a Printer should report a long dimension of 0 in the ready media. If your roll printer keeps track of the remaining length then it should report the appropriate range instead of 0...<br class="">
<br class="">
So, it looks like media-col-ready/media-size/y-dimension should have a syntax of integer(0:MAX)|rangeOfInteger(1:MAX) while all of the other x-dimension and y-dimension member attributes should be integer(1:MAX)|rangeOfInteger(1:MAX).<br class=""></div></div></blockquote><div><br class=""></div>Since media-col-ready/media-size/y-dimension will have a syntax of integer(0:MAX)|rangeOfInteger(1:MAX), that means that media-col-database/media-size/y-dimension will have the same syntax, since media-col-ready is a subset of media-col-database, correct?</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">
<br class="">
And of course I will make sure the updated test in 5100.7 mirrors the wording in 5101.1 and makes it explicitly clear for everyone.<br class="">
<br class="">
<br class="">
> All,<br class="">
> <br class="">
> OK, so I've looked through MSN2, the original PPA, and JOBEXT2.0 and can't find a reason for the media-size members having a range of 0:MAX. Since the media-size-supported values have a range of 1:MAX then that is what the other media-size values should have as well. And honestly I'm not sure what a media size of 0x0 would represent...<br class="">
> <br class="">
> <br class="">
>> On Jun 23, 2022, at 4:50 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:<br class="">
>> <br class="">
>> Signed PGP part<br class="">
>> Greetings,<br class="">
>> <br class="">
>> In advance of an erratum resolution in PWG 5100.7 for Issue #113 (<a href="https://www.pwg.org/dynamo/issues.php?L113+P-1+S-2+I0+E0+Z67+Q" class="">https://www.pwg.org/dynamo/issues.php?L113+P-1+S-2+I0+E0+Z67+Q</a>), HP Inc. is requesting updating the registration of the "media-size" members of "media-col-database" and "media-col-ready" to also list the "rangeOfInteger" syntax in addition to the current "integer" syntax. HP Inc. is also requesting that the definitions specify a lower bounds of 0 instead of 1 for the "x-dimension" and "y-dimension" members of "media-col-database" and "media-col-ready" to match the member definitions in the "media-col" Job Template attribute.<br class="">
>> <br class="">
>> The current registration listed on pages 58 and 60 of PWG 5100.7-2019 are:<br class="">
>> <br class="">
>> media-col-database (1setOf collection)<br class="">
>> <Any "media-col" member attribute><br class="">
>> media-source-properties (collection)<br class="">
>> media-source-feed-direction (type2 keyword)<br class="">
>> media-source-feed-orientation (type2 enum)<br class="">
>> <br class="">
>> media-col-ready (1setOf collection)<br class="">
>> <Any "media-col" member attribute><br class="">
>> media-source-properties (collection)<br class="">
>> media-source-feed-direction (type2 keyword)<br class="">
>> media-source-feed-orientation (type2 enum)<br class="">
>> <br class="">
>> media-size-supported (1setOf collection)<br class="">
>> x-dimension (integer(1:MAX) | rangeOfInteger(1:MAX))<br class="">
>> y-dimension (integer(1:MAX) | rangeOfInteger(1:MAX))<br class="">
>> <br class="">
>> If HP Inc.'s requests are followed, the IANA IPP Registry would be updated like so (changes in red if you can see color):<br class="">
>> <br class="">
>> media-col-database (1setOf collection)<br class="">
>> <Any "media-col" member attribute><br class="">
>> media-size (collection)<br class="">
>> x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))<br class="">
>> y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))<br class="">
>> media-source-properties (collection)<br class="">
>> media-source-feed-direction (type2 keyword)<br class="">
>> media-source-feed-orientation (type2 enum)<br class="">
>> <br class="">
>> media-col-ready (1setOf collection)<br class="">
>> <Any "media-col" member attribute><br class="">
>> media-size (collection)<br class="">
>> x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))<br class="">
>> y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))<br class="">
>> media-source-properties (collection)<br class="">
>> media-source-feed-direction (type2 keyword)<br class="">
>> media-source-feed-orientation (type2 enum)<br class="">
>> <br class="">
>> media-size-supported (1setOf collection)<br class="">
>> x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))<br class="">
>> y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))<br class="">
>> <br class="">
>> <br class="">
>> Doing this registration sooner rather than later will help systems that generate code from the IANA IPP Registry, such as "jipp".<br class="">
>> <br class="">
>> Let me know if there are any objections to this registration via email or we can discuss at the next IPP Workgroup call.<br class="">
>> <br class="">
>> Cheers,<br class="">
>> <br class="">
>> Smith<br class="">
>> <br class="">
>> /**<br class="">
>> Smith Kennedy<br class="">
>> HP Inc.<br class="">
>> */<br class="">
>> <br class="">
>> <br class="">
>> <br class="">
> <br class="">
> ________________________<br class="">
> Michael Sweet<br class="">
> <br class="">
> <br class="">
> <br class="">
> <br class="">
<br class="">
________________________<br class="">
Michael Sweet<br class="">
<br class="">
</div>
<br class=""><br class=""></div></blockquote></div><br class=""></div></body></html>