Subject: [IPP] RFC: Deprecate "pages-per-subset" and related attributes

From: Michael Sweet via ipp <[email-masked]>
Date: Thu, 09 May 2019 17:22:15 -0400

All,

As previous noted, PWG 5100.1: IPP Finishings v2.1 (FIN) and PWG 5100.13: IPP Job and Printer Extensions - Set 3 (JPS3) both define an attribute that specifies the number of pages in a document that constitute a set for finishing (stapling, binding, etc.)

The "job-pages-per-set (integer(1:MAX))" attribute (5100.1) has broad adoption and clearly-defined semantics for shipping printers.  The "pages-per-subset (1setOf integer(1:MAX))" attribute (5100.13) has no known shipping implementations and interacts with the "multiple-document-handling" attribute and multiple-document jobs.

During today's IPP workgroup conference call, the consensus was to deprecate "pages-per-subset" since the "job-pages-per-subset" provides the necessary functionality and is implemented by printers that need it.

Please provide feedback ASAP if you disagree with this decision.  The plan is to publish this deprecation on the IANA IPP registry after the May 23, 2019 IPP workgroup conference call.

.......

Registration template:

Job Template attributes:	Reference
--------------------------	---------
pages-per-subset(deprecated) (1setOf integer(1:MAX))	[PWG5100.13]

Printer Description attributes:	Reference
------------------------------	---------
pages-per-subset-supported(deprecated) (boolean)	[PWG5100.13]

_________________________________________________________
Michael Sweet, Senior Printing System Engineer

_______________________________________________
ipp mailing list
[email-masked]
https://www.pwg.org/mailman/listinfo/ipp