HI Mike,
Thanks for doing this!
I’ve not personally had a chance to stare at it very hard just yet. But my one suggestion for the diagram might be to label each of the vertices with a unique letter, and label each of edges with a unique number, so that one can describe a path or an edge / vertex interface in an unambiguous manner. This could be useful in lieu of our being in one place and all able to “point” at things on a whiteboard or projector screen.
Smith
/**
Smith Kennedy
ATB Wireless Architect - PPS
Hewlett-Packard Co.
*/
On 2013-12-10, at 7:06 PM, Michael Sweet <msweet at apple.com> wrote:
> All,
>> Because we seem to be tripping over differences in terminology and our collective "big picture" of how cloud-based imaging is supposed to work, I put together the attached simplified diagram for a typical MFD that is registering Print, Scan, and FaxOut with a public cloud. Each of the local services is "connected" to a corresponding service in the cloud. I have purposely not included any fan-out in the diagram in order to focus our discussions on this simplified model. We can expand our discussions once there is agreement on the simplified model/diagram.
>> (When comparing this to the model described in IPPSIX, you'd just remove all of the non-print services from the diagram...)
>> Thoughts? Does this roughly match everyone's internal picture of cloud-based imaging?
>>>>>> <PastedGraphic-1.png>
>> _______________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20131211/eaadeff4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3319 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20131211/eaadeff4/attachment.p7s>