[IPP] [Cloud] Simplified Cloud Imaging Diagram for a typical MFD

[IPP] [Cloud] Simplified Cloud Imaging Diagram for a typical MFD

[IPP] [Cloud] Simplified Cloud Imaging Diagram for a typical MFD

William A Wagner wamwagner at comcast.net
Wed Dec 11 16:22:45 UTC 2013


Randy,

Although they may change as a result of these interchanges, we have been
talking about sequences for several months now and they are plotted in
ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.pdf. 
Thanks,

Bill Wagner

-----Original Message-----
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
Randy Turner
Sent: Wednesday, December 11, 2013 11:06 AM
To: Michael Sweet
Cc: <cloud at pwg.org>; <ipp at pwg.org>
Subject: Re: [Cloud] Simplified Cloud Imaging Diagram for a typical MFD


Yeah, that label idea will come in handy in future references, and when we
want to talk about sequences.

R.

On Dec 11, 2013, at 10:07 AM, Michael Sweet <msweet at apple.com> wrote:

> Randy,
> 
> 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.
>> 
>> R.
>> 
>> 
>> On Dec 10, 2013, at 9: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
>>> 
>>> _______________________________________________
>>> 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
> 
> 

_______________________________________________
cloud mailing list
cloud at pwg.org
https://www.pwg.org/mailman/listinfo/cloud



More information about the ipp mailing list