On 2013-01-28, at 1:51 AM, "K.D. Lucas" <kdlucas at gmail.com> wrote:
> I was looking over IPP definitions for Printer and Print Job states, according to RFC 2911. I found these in section 4.3.7, 4.3.8, 4.4.11, and 4.4.12.
>> I have a few questions:
> Is this the latest definitions for Printer and Print Job Statuses?
> Has Cloud Print Imaging adopted/used these definitions?
Yes, as Cloud Imaging is an extension of the Semantic Model which started as an abstract definition of IPP.
> If so, it looks like the "Reasons" why printers and print jobs get into their various states is the most significant piece of information in these definitions. Under reasons, there seems to be some ambiguous definitions. It's not clear to me that many of the reasons are needed.
Can you provide some specific examples?
> I'm also slightly confused about the distinction between the IPP Everywhere Group and the Cloud Imaging Group. Is the Cloud Imaging group focused on the use case where there is a Cloud Print Service in between the printer device and the client? Correspondingly I'm guessing IPP Everywhere does not address interoperability of potential 3rd party Cloud Print Services. Am I interpreting that correctly?
IPP Everywhere addresses basic printing and interoperability through a higher minimum set of required capabilities - protocols, file formats, etc. Basically, how do we make the existing IPP support "driverless" printing from multiple platforms?
The Cloud Imaging Model addresses printing across network boundaries, specifically where the Client is unable to communicate directly with the Printer. This has traditionally been done using output device support in IPP ("print servers") and a lot of hand-waving ("implementation-defined" behavior) but we are now tackling it directly.
The corresponding IPP binding of the Cloud Imaging Model is called IPP Shared Infrastructure Extensions - the naming of the IPP spec is different because the same model applies much more broadly than just "cloud".
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...