attachment-0002
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><base href="x-msg://667/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Larry,<div><br><div><div>On 2013-02-07, at 2:38 PM, larryupthegrove <<a href="mailto:larryupthegrove@comcast.net">larryupthegrove@comcast.net</a>> wrote:</div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: 'Andale Mono'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">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.</div></div></div></blockquote><div><br></div>Thanks for this, and apologies that it has taken me this long to review it...</div><div><br></div><div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; "><o:p><font color="#000000">...</font><font face="Calibri, sans-serif"><span style="font-size: 11pt;"> </span></font></o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; ">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.<o:p></o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; ">I believe there could eventually be a Copy and a Device Administration set of requirement documents as well.<o:p></o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><o:p></o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><o:p> </o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf" style="color: purple; text-decoration: underline; ">ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf</a><o:p></o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><o:p> </o:p></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx" style="color: purple; text-decoration: underline; ">ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx</a><o:p></o:p></div></div></div></blockquote><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Device Administration is out of scope. We are not defining an interface for remote device management.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>