Hi Mike,
Thank you for your response. The issue is summed up as follows:
The device itself does not allow the selection of the Folder Tray or the Booklet Tray. If a job is programmed for a Trifold C/Z or a Bifold/Booklet (Bifold with center stitch), it WILL be delivered to the Folder Tray or the Booklet Tray, depending on which. To put it differently, the jobs are automatically delivered to those trays when the appropriate folding is selected. You do NOT get the folding by selecting the output tray.
If a constraint(s) need(s) to address this, I cannot see how to specify the folder tray is not selectable with all but one job attribute within a constraint. In other words, a constraint "lists collections of Job Template attributes and values that are incompatible with one another", yet theoretically the constraint should specify the converse, that output-bin = folder (name(MAX)) can only be used with finishings = fold. Otherwise there needs to be a multitude of constraints for all other job attributes that are combined with output-bin = folder. That seems like a lot of constraints.
Or I am missing something, which wouldn't surprise me d:o)
Chris
Christopher Rizzo
Engineer II, Software Engineering
Design & Development Engineering
[signature_3928563565]<http://www.xerox.com/>
Xerox Corporation
Virtual Office Employee
26600 SW Parkway Ave
Wilsonville, OR 97070
[signature_4291808722]<https://www.linkedin.com/company/xerox/> [signature_1018608027] <https://www.youtube.com/user/XeroxCorp> [signature_267370097] <https://twitter.com/Xerox> [signature_2877453276] <https://www.instagram.com/xerox/> [signature_804638117] <https://www.facebook.com/XeroxCorp>
From: ipp <ipp-bounces at pwg.org> on behalf of PWG Workgroup <ipp at pwg.org>
Reply-To: PWG Workgroup <ipp at pwg.org>
Date: Saturday, August 23, 2025 at 10:15 AM
To: PWG Workgroup <ipp at pwg.org>
Cc: Michael Sweet <msweet at msweet.org>
Subject: Re: [IPP] printer-output-tray and output-bin-supported cardinality issue (PWG 5100.13)
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Chris,
On Aug 22, 2025, at 4:59 PM, Christopher Rizzo via ipp <ipp at pwg.org<mailto:ipp at pwg.org>> wrote:
The following requirement in PWG 5100.13-2023 Section 6.6.10 printer-output-tray:
"A Printer MUST support this attribute if it supports the "output-bin" attribute [PWG5100.2]. If supported, this attribute MUST have the same cardinality (contain the same number of values) as the "output-bin-supported" Printer Description attribute [PWG5100.2]. The ith value in this attribute corresponds to the ith value in the "output-bin-supported" attribute."
Presents a conflict in that it's possible some output-bin values cannot be specifically selected in a print-job or create-job request. Output to some bins are controlled only by other job programming attributes.
Can you provide a concrete example of this?
Ideally any output tray/roll should be selectable via the "output-bin" Job Template attribute. If there are constraints requiring the use of other Job Template attributes to "enable" a particular paper path, those should be enforced when accepting a print Job, either by returning the 'successful-ok-ignored-or-substituted-attributes' or 'client-error-conflicting-attributes' status codes with the corresponding attributes/values in the unsupported attributes group of the Create-Job/Print-Job/Print-URI response.
Similarly, the "job-constraints-supported", "job-resolvers-supported", and "job-triggers-supported" Printer attributes can be used to tell a Client what those constraints are and/or to trigger selection of the necessary companion attributes and values so that the Client UI can manage things prior to Job submission...
________________________
Michael Sweet
_______________________________________________
ipp mailing list
ipp at pwg.org<mailto:ipp at pwg.org>
https://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9065 bytes
Desc: image001.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1409 bytes
Desc: image002.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1427 bytes
Desc: image003.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1528 bytes
Desc: image004.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1648 bytes
Desc: image005.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1456 bytes
Desc: image006.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20250825/a3bc52be/attachment-0005.png>
