Re: printer-output-tray and output-bin-supported cardinality issue (PWG 5100.13)
Michael Sweet via ipp <[email protected]> Sat, 23 Aug 2025 13:15:16 -0400
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Chris, > On Aug 22, 2025, at 4:59 PM, Christopher Rizzo via ipp <[email protected]> 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 [email protected] https://www.pwg.org/mailman/listinfo/ipp