attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Ira,<div><br><div><div><div>On Oct 16, 2013, at 4:49 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div>Hi Mike,<br><br></div>Agreed - Service(s) --> Printer(s) in IPP.<br><br></div>But this locks us in forever to only output services (like FaxOut), right?<br></div></div></div></div></div></div></div></div></div></div></blockquote><div><br></div>I don't think so - it just means that we start calling scanners and other imaging services "Printers" since the protocol started life to support printing.</div><div><br></div><div>Alternately we go back and define aliases for the original print-centric operation codes to use Service instead of Printer, but then we also would want to rename printer-xxx attributes to service-xxx which would impact the on-the-wire encoding (whereas adding a name that has the same operation code doesn't...)</div><div><br></div><div><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div>The IPP URI scheme (and IPPS URI scheme) allow URIs to reference any<br></div>object (not just IPP Printer), e.g., Subscription.<br></div></div></div></div></div></div></div></div></blockquote><div><br></div>Sure.</div><div><br><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div>So I think we ought to at least briefly discuss this (Service-->Printer)<br>
</div>closing the future off at the F2F, before finalizing.<br></div></div></div></div></div></div></blockquote><div><br></div>Absolutely, and something we should be discuss during our SCS time slot.</div><div><br><blockquote type="cite"><div dir="ltr"><div><div><div><div>I'm thinking about modelling IPP attributes for ConfiguredPrinters and<br></div>ConfiguredResources (in the System object) and some of the other<br>
</div>complex attributes (presumably they'll become collections?).<br></div></div></div></blockquote></div><br></div></div><div>That would be my preference, yes.</div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); 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; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); 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; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></body></html>