[Cloud] Cloud Imaging model requirement draft

[Cloud] Cloud Imaging model requirement draft

[Cloud] Cloud Imaging model requirement draft

Michael Sweet msweet at apple.com
Fri Apr 19 19:58:33 UTC 2013


On 2013-02-07, at 2:38 PM, larryupthegrove <larryupthegrove at comcast.net> wrote:
> I posted a draft of the Cloud Imaging document to the white folder of the FTP site.  Please review the document and determine if you think this is a reasonable way forward, or suggest alternatives.

Thanks for this, and apologies that it has taken me this long to review it...

> ... 
> I would as a next step create the framework for the Fax and Scan model documents by using the Cloud Print Model Requirements as a master.
> I believe there could eventually be a Copy and a Device Administration set of requirement documents as well.
> ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf
> ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx

One problem I see with this approach is that the Semantic Model WG did this and now has a bunch of specs to update to synchronize with a 2.0 common model document.  Each new service has introduced its own slightly-different version of the common schema.  I would rather we not go down the same road.

Generally speaking, we need to address document output (Print, FaxOut, EmailOut) and document input (Scan, FaxIn, EmailIn) services that are accessed via a set of Cloud/infrastructure services.  All of the current work has been focused on output, and I think we are in a good place there.  For input, we need to extend the Semantic Model slightly to have the Cloud Scan/FaxIn/EmailIn service provide a storage location (FTP or HTTP/WebDAV) so that the Manager has a place to store the incoming documents and the Client has a place to retrieve the incoming documents.

Transform is the classic "in the cloud" service, and I don't see a need to define a separate Cloud interface to support a situation where a Client submits a Transform job to a Cloud Transform Service, to have that transform be performed on an imaging device - doesn't make a whole lot of sense.

Copy can be modeled as Print with an AddPrintHardcopyDocument operation.  If we *did* keep a separate Copy service, it is just an output service that does not fetch or acknowledge documents.

Device Administration is out of scope.  We are not defining an interface for remote device management.

Michael Sweet, Senior Printing System Engineer, PWG Chair

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/20130419/f0f82051/attachment-0002.html>

More information about the cloud mailing list