attachment-0002
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">So that also means we should model a Cloud Association and Registration Service (CARS :) that just supports the Associate and Register operations and is the endpoint of the Cloud Print Provider. This service can be standalone (frontend) or part of the Cloud Print System Service.<div><br></div><div><div><br><div><div>On May 14, 2012, at 8:22 AM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://53/"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I think Pete is right that we need to show that registration and association go to the Cloud Print Provider (CPP), with registration creating the Cloud Print Service (CPS) that is associated with the Cloud Print Manager (CPM) for the "long term".</div><div><br></div><div>I'm also now thinking we should show the Cloud Print System Service (CPSS) that the client talks to, since that is how we've been talking about the CPP in recent meetings. The CPSS may not be the same service that the Client sends its Associate request to - Cloud services are much more dynamic and a particular user/organization may have specific resources assigned/dedicated to them. The common association/registration front-end interface directs Clients and CPMs to the appropriate Cloud services assigned for their use.</div><div><br></div><div>In the diagram we should show a receipt being returned by the CPP for Associate and Register requests. An Associate Receipt would return something like an OAuth2 token with the URI representing the CPSS (probably the same as the one used for the Associate request, but possibly a different service endpoint specific to the user/resources/geographic region), while the Register Receipt is the OAuth2 token along with the URI representing the endpoint for the CPS that is the Cloud's queue for the CPM.</div><div><br></div><div>Thoughts?</div><div><br></div><div><br></div><div><div><div>On May 14, 2012, at 5:20 AM, "Zehler, Peter" <<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: 'Andale Mono'; font-size: medium; 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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); ">All,<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); ">The main problem I have with the diagram is that it shows a Cloud Print Manager registering with the Cloud Print Service instead of the Cloud Print Provider. In my (protocol centric) view a upon the receipt of a registration request from a Cloud Print Service, or its agent, the Cloud Print Provider instantiates a cloud environment specific implementation of a Cloud Print Service. The requirements for that implementation are that it implements the PWG Print Service interface, exposes the appropriate objects and attributes, and externally conforms to the state models codified in the PWG model. At a later time the Cloud Print Manager will bind to the Cloud Print Service to provide updated status and capability information and to process Print Jobs destined for the physical printer(s) associated with the Cloud Print Manager. <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); ">I expect the normal cardinality would be one physical device per Cloud Print Manager and One Cloud Print Manager per Cloud Print Service. The PWG model accommodates both Fan-Out and Fan-In of Printers. This allows a Cloud Print Manager to “front end” a number of physical printers. Those printers can be collocated (i.e., printer farm) or distributed (e.g., FedEx printer in Google Cloud Print). Alternatively a single physical device could be associated with a Cloud Print Manager that registers multiple Cloud Print Services. The purpose of such a configuration could be to present different capabilities and/or different defaults for each of the Cloud Print Services.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); ">The [Print] Client is shown sending an Association request to the Cloud Print Provider. Once the association is established and based on the policies in place for the associated user, a set of Cloud Print Services will be visible to the [Print] Client. The [Print] Client can then interact (e.g., query status, query capabilities, submit print jobs) with the Cloud Print Service.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); ">Pete<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="font-family: Impact, sans-serif; color: navy; ">Peter Zehler</span><span style="color: rgb(31, 73, 125); "><br><br></span><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: navy; ">Xerox Research Center Webster<br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">Email:<span class="Apple-converted-space"> </span><a href="mailto:Peter.Zehler@Xerox.com" style="color: purple; text-decoration: underline; ">Peter.Zehler@Xerox.com</a></span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">Voice: (585) 265-8755</span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">FAX: (585) 265-7441</span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">US Mail: Peter Zehler</span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">Xerox Corp.</span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">800 Phillips Rd.</span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">M/S 128-25E</span><span style="color: rgb(31, 73, 125); "><br></span><span style="font-size: 10pt; font-family: Arial, sans-serif; color: navy; ">Webster NY, 14580-9701</span><span style="color: rgb(31, 73, 125); "></span><span style="font-size: 12pt; font-family: 'Times New Roman', serif; color: rgb(31, 73, 125); "><o:p></o:p></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="color: rgb(31, 73, 125); "> </span></div><div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in; "><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><span class="Apple-converted-space"> </span><a href="mailto:cloud-bounces@pwg.org" style="color: purple; text-decoration: underline; ">cloud-bounces@pwg.org</a><span class="Apple-converted-space"> </span>[mailto:cloud-<a href="mailto:bounces@pwg.org" style="color: purple; text-decoration: underline; ">bounces@pwg.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>larryupthegrove<br><b>Sent:</b><span class="Apple-converted-space"> </span>Friday, May 11, 2012 7:05 PM<br><b>To:</b><span class="Apple-converted-space"> </span><a href="mailto:cloud@pwg.org" style="color: purple; text-decoration: underline; ">cloud@pwg.org</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>[Cloud] Cloud white board diagram from meeting - converted tovisio/pdf<o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20model%20representation.vsd" style="color: purple; text-decoration: underline; ">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.vsd</a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20model%20representation.pdf" style="color: purple; text-decoration: underline; ">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.pdf</a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Please review and I’ll update drawing before inserting into the cloudmodel draft.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Larry<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span style="font-size: 12pt; font-family: 'Times New Roman', serif; "><br>--<span class="Apple-converted-space"> </span><br>This message has been scanned for viruses and<span class="Apple-converted-space"> </span><br>dangerous content by<span class="Apple-converted-space"> </span><a href="http://www.mailscanner.info/" style="color: purple; text-decoration: underline; "><b>MailScanner</b></a>, and is<span class="Apple-converted-space"> </span><br>believed to be clean.<o:p></o:p></span></div></div><br>--<span class="Apple-converted-space"> </span><br>This message has been scanned for viruses and<span class="Apple-converted-space"> </span><br>dangerous content by<span class="Apple-converted-space"> </span><a href="http://www.mailscanner.info/" style="color: purple; text-decoration: underline; "><b>MailScanner</b></a>, and is<span class="Apple-converted-space"> </span><br>believed to be clean. _______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org" style="color: purple; text-decoration: underline; ">cloud@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/cloud" style="color: purple; text-decoration: underline; ">https://www.pwg.org/mailman/listinfo/cloud</a><br></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; border-spacing: 0px; "><div>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></div></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; 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; "><div>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></div></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>