The arrows are mainly there to show which box initiates the communications. And based on Smith's comments I think I'll just label each of the lines for later references so it truly is just a high-level view without any of the specific details.
On Dec 10, 2013, at 10:31 PM, Randy Turner <rturner at amalfisystems.com> wrote:
>> Hi Mike,
>> I think it’s a great idea to put together an unambiguous reference diagram like this — It looks like the arrows in the diagram suggest elements of procedure, but I’m assuming that each type of cloud functional procedure description would reference this diagram in order to completely specify “how things work”. The arrows just emphasize what’s defined in the functional spec.
>>> On Dec 10, 2013, at 9:06 PM, Michael Sweet <msweet at apple.com> wrote:
>>>> 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?
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>> cloud mailing list
>>cloud at pwg.org>>https://www.pwg.org/mailman/listinfo/cloud>> _______________________________________________
> cloud mailing list
>cloud at pwg.org>https://www.pwg.org/mailman/listinfo/cloud
Michael Sweet, Senior Printing System Engineer, PWG Chair