All,
After today's meeting, I thought I would try to draw a slightly
different representation of the functional model diagram than what is in
the current model document. In the current model it is very unclear
what and where the "Cloud Print Manager" is (is in its own cloud or is
it proxy (so not really a cloud service) or in the printer (so not
really a cloud service)). Why does the (Print) Client "register" with
the Cloud Provider instead of just using the Cloud Print Provider.
In the functional model attached, I propose the more cloud centric model
which places service, security and other functionality in the Cloud. The
model is not specifically concerned with interfaces such as using IPP;
it is meant to be more a very top level view. In the attached model the
Client uses or accesses the Cloud Provider for printing services. The
User interacts with the Cloud Print Provider to select a Print Service
associated with the User. The Cloud Print Provider then sends
Capability information (which likely has no secure information) to the
Client. The Print Client creates Print Job Ticket (with a Print Content
reference) which is sent to the Print Service (or Print Service Manager)
for printing. The Print Service accepts (or rejects the Print Job).
The Print Service prints the Print Job and sends status info to the
Print Status Service. Federated printing also work quit well with this
model.
Glen
--
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/ipp/attachments/20120402/725fb73c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: A model-small.jpg
Type: image/jpeg
Size: 42238 bytes
Desc: A model-small.jpg
URL: <http://www.pwg.org/pipermail/ipp/attachments/20120402/725fb73c/attachment.jpg>
