Hi Kelly,
To elaborate a bit more on the distinction between the work of the IPP WG
and the Cloud Imaging Model WG:
1. The Cloud WG is working on a "model" of Cloud Printing based on the
PWG Semantic Model. The intent is to later expand this model to address all
"Imaging" services using Cloud-based intermediaries.
2. The concept is that once a general model is agreed to, it will be
up to the IPP WG group to specify an IPP binding and the Semantic Model WG
to develop a Web Services binding.
3. The main contributions of the Cloud Group at this point have been
in identifying areas that the Semantic Model WG has had to work on,
specifically the PWG Job Ticket and the additional "reverse" set of
operations by which an Imaging Service (such as provided by a printer) must
initiate communication with a Cloud-based intermediary to allow the
interchange normally initiated by the Client.
4. The initial idea was to handle Cloud Printing within the IPP WG,
but the membership decided that a model not restricted to a specific binding
was preferable.
5. This Cloud Imaging model is intended to be consistent with the
Semantic model, and I expect will eventually be absorbed into the Semantic
Model effort.
6. The earlier Print Job Ticket Mapping activities, which have now
been transferred to the Semantic Model WG, correlate Semantic Model elements
with the Printer Capabilities and Print Job Ticket structures based on PPDs
or XPS (MSPS), approaches used by existing Cloud Print Services. One intent
of this effort was to encourage some degree of compatibility between
current Cloud Print Services and the PWG Semantic Model.
7. However, creating a model to address interoperability with current
or potential 3rd party Cloud Print Services is not a part of the current
charter of the Cloud WG, although some aspects of compatibility with some
extant implementations are occasionally considered. This is perhaps a
deficiency, but this path was taken because no standard exists for Cloud
Print Services and existing services are considered as offering inadequate
flexibility to Users. However, the Cloud WG would welcome input and
requests from those familiar with and/or planning Cloud Print Services.
Thanks,
Bill Wagner
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
Michael Sweet
Sent: Monday, January 28, 2013 9:36 AM
To: K.D. Lucas
Cc: cloud at pwg.org
Subject: Re: [Cloud] Cloud Imaging and IPP Printer and Print Job States
Kelly,
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 <http://tools.ietf.org/html/rfc2911> . I found these
in section 4.3.7 <http://tools.ietf.org/html/rfc2911#section-4.3.7> , 4.3.8
<http://tools.ietf.org/html/rfc2911#section-4.3.8> , 4.4.11,
<http://tools.ietf.org/html/rfc2911#section-4.4.11> and 4.4.12
<http://tools.ietf.org/html/rfc2911#section-4.4.12> .
I have a few questions:
1. Is this the latest definitions for Printer and Print Job Statuses?
Yes.
2. 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.
3. 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 <http://www.mailscanner.info/> MailScanner, and is
believed to be clean.
--
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...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20130128/c4c116e5/attachment-0002.html>