attachment
<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">All,<div class=""><br class=""></div><div class="">I think we have consensus to relax the IPP Everywhere Printer Self-Certification test suite WRT requiring the value 'document-numbers' in the "overrides-supported" attribute, at least for printers that do not support multiple document jobs (the majority of IPP printers by far). We can discuss whether to add a test for overrides on PDF printers...</div><div class=""><br class=""></div><div class="">We also have consensus to NOT update PWG 5100.6 since doing so will introduce interoperability issues.</div><div class=""><br class=""></div><div class="">As for errata updates to PWG 5100.14, we have consensus to:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">1. List the specific "overrides" member attributes that are required ("overrides.document-numbers", "overrides.page-numbers", plus each of the required/conditionally required Job Template attributes), which is consistent with how "media-col" is handled in the currently published specification; and</div><div class=""><br class=""></div><div class="">2. Update the "overrides" and "overrides-supported" member attributes to "Note 5" since the intent was not to require overrides support for all printers, but just for PDF printers since PWG Raster offers per-page media and duplex overrides as part of the format.</div></blockquote><div class=""><br class=""></div><div class="">Based on your feedback below and what is required for conformance with PWG 5100.6, I feel that any further clarification in 5100.14 should be limited to adding a note explaining that Printers that do not support multiple document jobs MUST still accept a "document-numbers" member attribute with the value '1', and the Clients SHOULD NOT send the "document-numbers" member attribute unless submitting a multiple-document job.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class="">On May 16, 2016, at 8:08 AM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@xerox.com</a>> wrote:<br class=""><br class="">Smith,<br class=""><br class="">I don't understand your response. Especially your comment " rather simply adopting attributes defined therein". A feature, such as overrides, can't be taken in bits and pieces. A feature like this stands on its own and is either supported or not. I'd also point out that the overrides feature is the second version and has significant implementation experience behind it. It has been greatly simplified. <br class=""><br class="">If your intention is to modify the test suite to permit to permit certain implementations to pass, I have no objection. The test suite was never intended to be comprehensive and rigorous. But you must not change the mandatory semantics of 5100.6 in a subsequent specification such as 5100.14. There is no association between overrides and "multiple-document-jobs-supported". I believe that was discussed and rejected. The "overrides-supported" attribute has two mandatory values if overrides is supported. Most important is that a printer MUST accept, and honor, "document-numbers" in a request. Of course the job level attributes (e.g., “multiple-document-handling”) are ignored. But the “ipp-attribute-fidelity” attribute MUST be honored. If it is true, a single document printer that supports overrides MUST NOT reject a job with an override that includes '1' in its "document-numbers" attribute.<br class=""><br class="">I can probably make myself available for a PWG IPP meeting if this subject is on the agenda. Typing is not the most efficient way carry on a discussion. As you may of guessed, I strongly believe it would be a mistake to change a mandatory attribute/value to conditional.<br class=""><br class="">Pete<br class=""><br class=""><br class="">Peter Zehler<br class="">Xerox Corp.<br class="">Global Development Group<br class="">800 Phillips Rd, 111-04A<br class="">Webster NY, 14580-9701<br class="">Email: <a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@Xerox.com</a><br class="">Office: +1 (585) 265-8755<br class="">Fax: +1 (585) 422-0238<br class="">Mobile: +1 (585) 329-9508<br class=""><br class="">-----Original Message-----<br class="">From: Kennedy, Smith (Wireless Architect) [<a href="mailto:smith.kennedy@hp.com" class="">mailto:smith.kennedy@hp.com</a>] <br class="">Sent: Thursday, May 12, 2016 4:24 PM<br class="">To: Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@xerox.com</a>><br class="">Cc: <a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">Subject: Re: [IPP] [PWG5100.6] Issue #30: "overrides-supported": 'document-numbers' should be conditionally required depending on "multiple-document-jobs-supported" = 'true'<br class=""><br class="">Hi Pete,<br class=""><br class="">I wanted to provide you with an update. We discussed this on Monday in the IPP WG meeting, and we all agreed with you that we should not be changing 5100.6. It will remain as it is.<br class=""><br class="">However, since 5100.14 isn't requiring normative compliance with 5100.6 but is rather simply adopting attributes defined therein, we agreed that within the context of IPP Everywhere making "overrides-supported"/"document-copies" it was reasonable to conditionally require depending on "multiple-document-jobs-supported".<br class=""><br class="">Please let me know if you see problems with this direction.<br class=""><br class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> Wireless Architect - Client Software - IPG-PPS<br class=""> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF<br class=""> PWG Chair<br class=""> HP Inc.<br class="">*/<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On 2016-05-09, at 5:03 AM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@xerox.com</a>> wrote:<br class=""><br class="">Smith,<br class="">My concern is that clients that implement page overrides will break. The long standing specification explicitly states the printer must accept document number in a request. I know there are some clients that do not ask the printer first to see if the page number or document number are permitted in the request. The specification does not say that the printer must support the document object, and therefore "document-number" , in order to support page overrides. It only says that the printer must support the document number in the request. I would prefer to keep the requirements as specified not only to prevent client interoperability problems but also to keep the implementations simplified and not have to accommodate special case processing. The simplified implementation would be true not only on the client side but the printer side as well. I have no problem with the client checking to see if the "document-copies" is supported since the use of it is a corner condition. I would also argue that by definition even a printer implementation that supports only single document jobs does implement a document object and its associated number. It is just not exposed through the IPP protocol. <br class="">Pete<br class=""><br class="">Peter Zehler<br class="">Xerox Corp.<br class="">Global Development Group<br class="">800 Phillips Rd, 111-04A<br class="">Webster NY, 14580-9701<br class="">Email: <a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@Xerox.com</a><br class="">Office: +1 (585) 265-8755<br class="">Fax: +1 (585) 422-0238<br class="">Mobile: +1 (585) 329-9508<br class=""><br class="">-----Original Message-----<br class="">From: Kennedy, Smith (Wireless Architect) [<a href="mailto:smith.kennedy@hp.com" class="">mailto:smith.kennedy@hp.com</a>] <br class="">Sent: Friday, May 06, 2016 6:56 PM<br class="">To: Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@xerox.com</a>><br class="">Cc: <a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">Subject: Re: [IPP] [PWG5100.6] Issue #30: "overrides-supported": 'document-numbers' should be conditionally required depending on "multiple-document-jobs-supported" = 'true'<br class=""><br class="">Hi Pete,<br class=""><br class="">Thanks for providing the background on this. But it still seems a bit odd to me to require support for an attribute when the feature itself isn't supported. As you say, if "document-numbers" is omitted, that is semantically equivalent to "all my documents" and on these products that is equivalent to "my first document" since it only supports one document per job.<br class=""><br class="">Is your concern that there could be clients out there that would have their jobs rejected because they expect the printer to always support "document-numbers" and they don't? There are certainly a lot of printers out there that do not support it.<br class=""><br class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> Wireless Architect - Client Software - IPG-PPS<br class=""> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF<br class=""> PWG Chair<br class=""> HP Inc.<br class="">*/<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On 2016-05-05, at 9:11 AM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@xerox.com</a>> wrote:<br class=""><br class="">All,<br class=""><br class="">If I remember correctly, the printer must accept the “document-numbers” in a client request even if the printer only supports single document jobs. For a single document job, and a printer that supports either single or multiple document jobs, the following attribute values in request containing an "overrides" attribute would all be equivalent:<br class="">"document-numbers": '1: 2147483647', (i.e., all my documents)<br class="">"document-numbers": '1: 1', (i.e., my first document)<br class="">"document-numbers" omitted (i.e. all my documents)<br class=""><br class="">The client may specify a subset of documents to which the override is applied. The implication of not specifying is that the overrides applies to all. The printer must accept and understand all of these. A client specifying a document number that does not exist is ignored since the override applies only to the pages/documents/document-copies specified for the override.<br class=""><br class="">I think it is simpler and cleaner to keep the primary specification of the override target (i.e., pages and document) mandatory for the printer to support in a request while the edge case (i.e., document-copies) remains optional.<br class=""><br class="">Peter Zehler<br class="">Xerox Corp.<br class="">Global Development Group<br class="">800 Phillips Rd, 111-04A<br class="">Webster NY, 14580-9701<br class="">Email: <a href="mailto:Peter.Zehler@xerox.com" class="">Peter.Zehler@Xerox.com</a><br class="">Office: +1 (585) 265-8755<br class="">Fax: +1 (585) 422-0238<br class="">Mobile: +1 (585) 329-9508<br class=""><br class="">-----Original Message-----<br class="">From: ipp [<a href="mailto:ipp-bounces@pwg.org" class="">mailto:ipp-bounces@pwg.org</a>] On Behalf Of <a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a><br class="">Sent: Wednesday, May 04, 2016 4:27 PM<br class="">To: <a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">Subject: [IPP] [PWG5100.6] Issue #30: "overrides-supported": 'document-numbers' should be conditionally required depending on "multiple-document-jobs-supported" = 'true'<br class=""><br class="">[Issue Unconfirmed]<br class=""><br class="">PWG 5100.6-2004 section 4.1.7 says:<br class=""><br class="">This attribute MUST contain the keywords “pages” and “document-numbers” because<br class="">a Printer MUST support these attributes.<br class=""><br class="">But the 'document-numbers' attribute should not be required unconditionally; it should be conditionally required depending on whether the Printer reports "multiple-document-jobs-supported" = 'true'. If it doesn't support "multiple-document-jobs-supported" or reports "multiple-document-jobs-supported" = 'false' then 'document-numbers' should not be required.<br class=""><br class="">Link: <a href="http://www.pwg.org/issues/30" class="">http://www.pwg.org/issues/30</a><br class=""><br class="">_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">https://www.pwg.org/mailman/listinfo/ipp<br class=""></blockquote><br class=""></blockquote><br class="">_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">https://www.pwg.org/mailman/listinfo/ipp<br class=""></blockquote><br class=""><div class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer<br class=""></div><br class=""></div></body></html>