attachment-0002
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://31/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Bill,<div><br><div><div>On 2013-04-01, at 10:53 AM, William A Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:</div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Consolas; 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; ">I have posted a discussion draft of the new operations for the Cloud Print Manager to Cloud Print Service interface. These are based on Pete’s original suggestions as modified in our December face-to-face, and I suggest that the minutes to the meeting be referred to in considering this draft. I see some differences relative to the IPP SIX draft Mike posted last week…so these should be resolved. Mike may have developed the ideas further since the December meeting.<o:p></o:p></div></div></div></blockquote><br></div><div>So WRT the list of CPM operations, I *did* tweak some things relative to the current Cloud Print Requirements and Model:</div><div><br></div><div>1. GetFetchablePrintJobs in SM is just Get-Jobs+which-jobs="fetchable" in IPP; this is consistent with how Get<foo><service>Jobs is mapped in MFD Common.</div><div><br></div><div>2. UpdatePrintServiceState in SM became Update-Output-Device-State in IPP; this is because the Manager is updating the state of the Output Device, not of the Print Service (the Print Service provides a roll-up/combined state)</div><div><br></div><div>3. Added new Get/Set-Output-Device-Attributes IPP operation to query and provide capabilities and descriptive attributes of the Output Device.</div><div><br></div><div>4. Added a new Acknowledge-Identify-Printer IPP operation to relay Identify-Printer requests from the Client to the Manager.</div><div><br></div><div>5. UpdateFetchableJobs is currently called Reset-Fetchable-Jobs in IPP, although I am fine with either name.</div><div><br></div><div>One of the key differences I see between the abstract model in Cloud Print Requirements and Model and the binding model in IPP Shared Infrastructure Extensions is that the relationship between the Cloud Print Service/Infrastructure Printer, Cloud Print Manager/Manager, and Output Device is explicit and follows the existing SM/IPP model for output device fanout. IPPSIX allows multiple output devices to be associated with a single instance of the Cloud Print Service/Infrastructure Printer and uses an identifier (output-device-uuid) from the Cloud Print Manager/Manager to identify which output device is being "addressed" or provided.</div><div><br></div><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; font-size: medium; "><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; font-size: medium; "><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></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>