attachment-0002
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 14, 2012, at 9:10 AM, Ira McDonald wrote:</div><blockquote type="cite">Hi Mike,<br><br>I agree with your observations below.<br><br>Except that the Associate Receipt and Register Receipt below<br>should be simply Associate Response and Register Response<br>(consistent w/ other PWG SM operations Request/Response).<br></blockquote><div><br></div>Fair enough.</div><div><br><blockquote type="cite">
They are quite different from a JobReceipt (an ornamented<br>
original User's JobTicket w/ actual chosen and defaulted <br>
values per the Job processing <service>).<br>
<br>And in IPP and PWG SM, we're thinking the Subscription-like<br>paradigm, so the operations are called CreatePrintAssociation <br>and CreatePrintRegistration (at least that's what Pete and I<br>have assumed). <br></blockquote><div><br></div>I would prefer CreateClientAssociation and CreateManagerRegistration (to keep with our current terminology) or just CreateAssociation and CreateRegistration since these are not service-specific. On the Client side I would expect that association will provide access to all services "shared" (registered) through the Cloud via the service endpoint provided in the response.</div><div><br></div><div>On the Cloud Print Manager side I would expect the manager to provide the service (or list of services) it wants to register along with any descriptive information - initially we are just talking about Print, but why have/force separate Create<service>Registration operations for the common MFD use case? Again, following the subscription interface we have in IPP, you can (today) create multiple subscriptions with a single operation and the response contains the corresponding list of subscription IDs - we'd use URIs for the Cloud Print Services.</div><div><br></div><div><blockquote type="cite">We don't use Subscribe as an operation in PWG SM - I don't <br>think the Cloud abstract operations should be called simply <br>Associate and Register. They also both should have input <br>parameters of the lease time for the created object - nothing<br>
is forever...<br></blockquote></div><div><br></div>Unless you ask for "forever" and the service allows it... :) IPP Notifications already support this use case...<div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Geneva; 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; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Geneva; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Geneva; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></div></span></div></span></div></span></span>
</div>
<br></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>