attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Agreed - I share your concern about breaking backward compatibility. And thanks for adding it to the agenda.<div class=""><br class=""><div class="">
Smith<br class=""><br class=""><br class="">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 2016-02-01, at 4:43 PM, Michael Sweet <<a href="mailto:msweet@apple.com" class="">msweet@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Smith,<div class=""><br class=""></div><div class="">I've added this to the list of issues in Finishings 2.0.</div><div class=""><br class=""></div><div class="">I'd have my concerns about having this be a MUST NOT since it might break existing Clients, but perhaps we could do something like:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">Printers SHOULD NOT return the "finishings-col-database" attribute in response to a Get-Printer-Attributes request unless the Client supplies the "requested-attributes" operation attribute with the value 'finishings-col-database'. Clients SHOULD supply the "requested-attributes" operation attribute whenever they require the current "finishings-col-database" value.</div></blockquote><div class=""><br class=""></div><div class="">But we need to do a little research on this and make sure we don't break anything... :/</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 1, 2016, at 4:25 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi there,<div class=""><br class=""></div><div class="">At HP Inc. we have observed a phenomenon with the "finishings-col-database" similar to the "media-col-database": it can be quite large, and including it in with the rest of the job template attributes for each Get-Printer-Attributes response can have a negative impact on response times. Would it be reasonable or acceptable to make it so that "finishings-col-database" was withheld from Get-Printer-Attributes responses unless it was explicitly named in the "requested-attributes" attribute included in the IPP request? The "finishings-col-ready" could be included by default, but no the full database.</div><div class=""><br class=""></div><div class="">We can discuss this in person next week but I wanted to front load the topic. I wasn't prepared to mention it in today's slide review and didn't want it to belabor the slide review process.</div><div class=""><br class=""></div><div class="">Thanks for your thoughts,</div><div class=""><div class=""><br class="webkit-block-placeholder"></div><div class="">
<div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span style="orphans: 2; widows: 2;" class="">Smith</span><br style="orphans: 2; widows: 2;" class=""><br style="orphans: 2; widows: 2;" class=""><span style="orphans: 2; widows: 2;" class="">/**</span><br style="orphans: 2; widows: 2;" class=""><div class=""><span style="font-family: ArialMT; background-color: rgba(255, 255, 255, 0);" class=""> Smith Kennedy<br class=""> Wireless Architect - Client Software - IPG-PPS</span><span style="font-family: ArialMT;" class=""></span><div style="font-family: ArialMT;" class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF</span></div><div style="font-family: ArialMT;" class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""> PWG Chair<br class=""> HP Inc.</span></div></div><div style="font-family: ArialMT;" class=""><span style="font-family: Arial; orphans: 2; widows: 2;" class="">*/</span><br style="font-family: Arial; orphans: 2; widows: 2;" class=""></div><div style="font-family: ArialMT;" class=""><span style="font-family: Arial; orphans: 2; widows: 2;" class=""><br class=""></span></div></div></div></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></div></div>_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class=""><a href="https://www.pwg.org/mailman/listinfo/ipp" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class=""></div></blockquote></div><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div></div></div></blockquote></div><br class=""></div></body></html>