Re: [EXTERNAL SENDER]: Re: Update IANA registry in advance of errata resolution for Issue #113?

"Kennedy, Smith \(Wireless & IPP Standards\) via ipp" <[email protected]> Mon, 8 Aug 2022 20:22:56 +0000
Newsgroups	gmane.ietf.ipp
Message-ID	<[email protected]>
Hi Mike,

> On Jul 27, 2022, at 7:52 AM, Michael Sweet <[email protected]> wrote:
> 
> 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.
> 
> From: Michael Sweet <[email protected]>
> Subject: [EXTERNAL SENDER]: Re: [IPP] Update IANA registry in advance of errata resolution for Issue #113?
> Date: July 27, 2022 at 7:52:01 AM PDT
> To: Michael Sweet <[email protected]>, PWG IPP Workgroup <[email protected]>
> Cc: "Kennedy, Smith (Wireless & IPP Standards)" <[email protected]>
> 
> 
> 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...
> 
> 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).

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?

> 
> 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.
> 
> 
> > All,
> >
> > 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...
> >
> >
> >> On Jun 23, 2022, at 4:50 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected]> wrote:
> >>
> >> Signed PGP part
> >> Greetings,
> >>
> >> In advance of an erratum resolution in PWG 5100.7 for Issue #113 (https://www.pwg.org/dynamo/issues.php?L113+P-1+S-2+I0+E0+Z67+Q <https://www.pwg.org/dynamo/issues.php?L113+P-1+S-2+I0+E0+Z67+Q>), 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.
> >>
> >> The current registration listed on pages 58 and 60 of PWG 5100.7-2019 are:
> >>
> >> media-col-database (1setOf collection)
> >> <Any "media-col" member attribute>
> >> media-source-properties (collection)
> >> media-source-feed-direction (type2 keyword)
> >> media-source-feed-orientation (type2 enum)
> >>
> >> media-col-ready (1setOf collection)
> >> <Any "media-col" member attribute>
> >> media-source-properties (collection)
> >> media-source-feed-direction (type2 keyword)
> >> media-source-feed-orientation (type2 enum)
> >>
> >> media-size-supported (1setOf collection)
> >> x-dimension (integer(1:MAX) | rangeOfInteger(1:MAX))
> >> y-dimension (integer(1:MAX) | rangeOfInteger(1:MAX))
> >>
> >> If HP Inc.'s requests are followed, the IANA IPP Registry would be updated like so (changes in red if you can see color):
> >>
> >> media-col-database (1setOf collection)
> >> <Any "media-col" member attribute>
> >> media-size (collection)
> >> x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >> y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >> media-source-properties (collection)
> >> media-source-feed-direction (type2 keyword)
> >> media-source-feed-orientation (type2 enum)
> >>
> >> media-col-ready (1setOf collection)
> >> <Any "media-col" member attribute>
> >> media-size (collection)
> >> x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >> y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >> media-source-properties (collection)
> >> media-source-feed-direction (type2 keyword)
> >> media-source-feed-orientation (type2 enum)
> >>
> >> media-size-supported (1setOf collection)
> >> x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >> y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >>
> >>
> >> Doing this registration sooner rather than later will help systems that generate code from the IANA IPP Registry, such as "jipp".
> >>
> >> Let me know if there are any objections to this registration via email or we can discuss at the next IPP Workgroup call.
> >>
> >> Cheers,
> >>
> >> Smith
> >>
> >> /**
> >> Smith Kennedy
> >> HP Inc.
> >> */
> >>
> >>
> >>
> >
> > ________________________
> > Michael Sweet
> >
> >
> >
> >
> 
> ________________________
> Michael Sweet
> 
> 
>

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
signature.asc (application/pgp-signature, 833 B)