Thanks Larry,
I think this reflects the last conference call, with a few little
exceptions. The legend is a good idea.
1. My understanding is that all Cloud Print Service/Cloud Print
Manager lines should be arrowed.
2. Capabilities (which may be dynamic) were grouped with status, which
needs to be supported in the Cloud Print Service/Cloud Print Manager
interface. Perhaps they do not need to be included in printer registration.
I suggest that whatever in the Cloud Print Provider handles printer
registration must also communicate with the Cloud Print Service to obtain
the status/configuration information.
Depending on what we settle with, this diagram will need a lot of text
explanation.
Thanks for posting this.
Bill Wagner
From: larryupthegrove [mailto:larryupthegrove at comcast.net]
Sent: Monday, July 23, 2012 11:44 AM
To: cloud at pwg.org
Cc: William Wagner
Subject: Cloud model drawing posted
ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation20120722.vsd
ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation20120722.pdf
I didn't receive any feedback, so I updated per my interpretation of the
minutes.
Larry
--
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/20120723/b017faf9/attachment-0002.html>