On 2013-04-01, at 10:53 AM, William A Wagner <wamwagner at comcast.net> wrote:
> 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.
So WRT the list of CPM operations, I *did* tweak some things relative to the current Cloud Print Requirements and Model:
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.
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)
3. Added new Get/Set-Output-Device-Attributes IPP operation to query and provide capabilities and descriptive attributes of the Output Device.
4. Added a new Acknowledge-Identify-Printer IPP operation to relay Identify-Printer requests from the Client to the Manager.
5. UpdateFetchableJobs is currently called Reset-Fetchable-Jobs in IPP, although I am fine with either name.
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.
Michael Sweet, Senior Printing System Engineer, PWG Chair
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...