Your diagram correlates to the PWG model, although the names are different.
I think one intent with the PWG Cloud printing diagram was to follow the
basic print interfaces already defined. We did back off from defining
interfaces for registration and association, understanding that these are
not print specific. Therefore the Cloud Print Service is (at this point)
just a print service that happens to be in the Cloud, for which (it is
currently believed) the Client interface will follow the general Client to
Print Service interface. The Cloud Print Manager appears to be a new entity,
but it is unclear to me at this point how different this is from just
another print service that happens to interface between a physical printer
and a print service in the cloud.
This approach needs to be worked on of course, and may not be an optimum
model. But it seemed better to start with something based on the existing
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
Sent: Wednesday, August 08, 2012 11:02 AM
To: cloud at pwg.org
Subject: [Cloud] cloud reference diagram
I was looking at our basic functional model of how cloud printing should
work, and there are many similarities between our cloud service,
registration ,etc. and the world of SIP VoIP. In the world of SIP, there
are SIP "proxies" and SIP user agents (or clients).
The SIP proxy is this proxy service "in the sky" (cloud) that proxies access
between user-agents (VoIP phones).
SIP phones don't talk to each other in a peer-to-peer fashion, rather, they
"register" with a SIP proxy, and the SIP proxy "proxies" access to these
devices to the rest of the telephony world. The proxy offers an "address
space" and a way of referencing these VoIP user agents that is globally
addressable, and these proxies also offer other services that can add
"value" but again, they don't represent a phone endpoint themselves -- they
are "proxies" for actual service endpoints. SIP proxies have registration,
feature negotiation, de-registration, and authentication, as well as
management functions (MIBs, REST APIs, SOAP endpoints, etc.)
The real "concrete" print service is actually somewhere else.the cloud just
provides value-added proxy services for print clients to access these
In the spirit of this well-understood terminology, I have created a simple
pic (see attached PDF) of what I think we're really trying to accomplish.
This message has been scanned for viruses and dangerous content by
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.