Let us place the following items in the pipe line for discussion (if time permits we could discuss them).
1. Paul Tykodi to discuss the minutes of the meeting with AFP Consortium - the reach out project to Cloud Printing vendors.
2. The Print Service 2.0 roadmap
3. Mapping document - review the requested changes from the last meeting to see whether the attendees agree with the changes in the updated version posted to the FTP site at the beginning of Monday.
Daniel.
________________________________________
From: mfd-bounces at pwg.org [mfd-bounces at pwg.org] on behalf of mfd-request at pwg.org [mfd-request at pwg.org]
Sent: Saturday, April 20, 2013 9:00 AM
To: mfd at pwg.org
Subject: mfd Digest, Vol 3, Issue 58
Send mfd mailing list submissions to
mfd at pwg.org
To subscribe or unsubscribe via the World Wide Web, visit
https://www.pwg.org/mailman/listinfo/mfd
or, via email, send a message with subject or body 'help' to
mfd-request at pwg.org
You can reach the person managing the list at
mfd-owner at pwg.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of mfd digest..."
Today's Topics:
1. SM 2.0, the Copy service, and Add<service>HardcopyDocument
(Michael Sweet)
----------------------------------------------------------------------
Message: 1
Date: Fri, 19 Apr 2013 14:56:57 -0400
From: Michael Sweet <msweet at apple.com>
Subject: [MFD] SM 2.0, the Copy service, and
Add<service>HardcopyDocument
To: "mfd at pwg.org" <mfd at pwg.org>
Message-ID: <26624BA5-335D-4516-BF46-3DF47025BDE4 at apple.com>
Content-Type: text/plain; charset="us-ascii"
All,
I had a random thought today while thinking about what needs to be done to support multifunction services through a cloud intermediary. Functionally each of the services can be put in one of three buckets: document output (Print, FaxOut, EmailOut, Transform), document input (Scan, FaxIn, EmailIn), document input and output (Resource), and non-document (Copy, System Control).
While we currently are not addressing a cloud-based System Control service at this time (or for that matter any remote Output Device/Service control/management), we *do* probably want to address Copy, and that is the *only* other service that is not document-based.
However, conceptually Copy *is* document based, it is just that the document is hardcopy from a scanning source. For FaxOut this is modeled using a separate operation (AddFaxOutHardcopyDocument) that pulls the document data from the specified scan source. A Print service that provided a similar operation (AddPrintHardcopyDocument) could provide the equivalent of the Copy service, and doing so would greatly simplify support for "cloud copy" in the Cloud Imaging Model.
Conceptually the EmailOut service could also implement an AddEmailOutHardcopyDocument operation to email scans, however Scan already supports a Destination URI which could allow for email "storage" of the scanned images, too.
....
Anyways, like I said this is just a random thought, but when we *do* get around to a SM 2.0 specification, perhaps we should also take a fresh look at things and retire the Copy service.
Thoughts?
_________________________________________________________
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/archives/mfd/attachments/20130419/8fcf3dac/attachment-0001.html
------------------------------
_______________________________________________
mfd mailing list
mfd at pwg.orghttps://www.pwg.org/mailman/listinfo/mfd
End of mfd Digest, Vol 3, Issue 58
**********************************
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.