attachment-0002
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><base href="x-msg://667/"><style><!--
/* Font Definitions */
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Andale Mono";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.3in;
text-align:justify;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l0 level1 lfo2;
font-size:16.0pt;
font-family:"Arial","sans-serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:27.0pt;
text-align:justify;
text-indent:-27.0pt;
page-break-after:avoid;
mso-list:l0 level2 lfo2;
font-size:14.0pt;
font-family:"Arial","sans-serif";}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.5in;
text-align:justify;
text-indent:-.5in;
page-break-after:avoid;
mso-list:l0 level3 lfo2;
font-size:12.0pt;
font-family:"Arial","sans-serif";}
h4
{mso-style-priority:9;
mso-style-link:"Heading 4 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.6in;
margin-bottom:.0001pt;
text-align:justify;
text-indent:-.6in;
page-break-after:avoid;
mso-list:l0 level4 lfo2;
font-size:10.0pt;
font-family:"Arial","sans-serif";}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.75in;
text-align:justify;
text-indent:-.7in;
mso-list:l0 level5 lfo2;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
font-style:italic;}
h6
{mso-style-priority:9;
mso-style-link:"Heading 6 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:58.5pt;
text-align:justify;
text-indent:-.8in;
mso-list:l0 level6 lfo2;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
{mso-style-priority:9;
mso-style-link:"Heading 7 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.9in;
text-align:justify;
text-indent:-.9in;
mso-list:l0 level7 lfo2;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
{mso-style-priority:9;
mso-style-link:"Heading 8 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:1.0in;
text-align:justify;
text-indent:-1.0in;
mso-list:l0 level8 lfo2;
font-size:10.0pt;
font-family:"Calibri","sans-serif";
font-style:italic;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
{mso-style-priority:9;
mso-style-link:"Heading 9 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:1.1in;
text-align:justify;
text-indent:-1.1in;
mso-list:l0 level9 lfo2;
font-size:11.0pt;
font-family:"Cambria","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Arial","sans-serif";
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Arial","sans-serif";
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Arial","sans-serif";
font-weight:bold;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-priority:9;
mso-style-link:"Heading 4";
font-family:"Arial","sans-serif";
font-weight:bold;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-family:"Calibri","sans-serif";
font-weight:bold;
font-style:italic;}
span.Heading6Char
{mso-style-name:"Heading 6 Char";
mso-style-priority:9;
mso-style-link:"Heading 6";
font-family:"Calibri","sans-serif";
font-weight:bold;}
span.Heading7Char
{mso-style-name:"Heading 7 Char";
mso-style-priority:9;
mso-style-link:"Heading 7";
font-family:"Calibri","sans-serif";}
span.Heading8Char
{mso-style-name:"Heading 8 Char";
mso-style-priority:9;
mso-style-link:"Heading 8";
font-family:"Calibri","sans-serif";
font-style:italic;}
span.Heading9Char
{mso-style-name:"Heading 9 Char";
mso-style-priority:9;
mso-style-link:"Heading 9";
font-family:"Cambria","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1515802739;
mso-list-template-ids:1382070776;}
@list l0:level1
{mso-level-style-link:"Heading 1";
mso-level-text:%1;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.3in;
text-indent:-.3in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-style-link:"Heading 2";
mso-level-text:"%1\.%2";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:37.8pt;
text-indent:-.4in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-style-link:"Heading 3";
mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:45.0pt;
text-indent:-.5in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level4
{mso-level-style-link:"Heading 4";
mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.6in;
text-indent:-.6in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level5
{mso-level-style-link:"Heading 5";
mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.7in;
text-indent:-.7in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level6
{mso-level-style-link:"Heading 6";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:98.1pt;
text-indent:-.8in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level7
{mso-level-style-link:"Heading 7";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.9in;
text-indent:-.9in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level8
{mso-level-style-link:"Heading 8";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;
mso-bidi-font-family:"Times New Roman";}
@list l0:level9
{mso-level-style-link:"Heading 9";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.1in;
text-indent:-1.1in;
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My proposal was an attempt to have separate sections in the imaging model for each of the services, due to unique requirements, or some sections may require more review.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My thinking was that would allow for the use cases and sequence drawings to reside in the separate sections, so that the drawings and use cases could be discussed and reviewed in an easier fashion.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m ok with you updating sections 1-3 in the Cloud Imaging document, I’ll then update the other sections and make a pass at the other sections. The work should be usable regardless of the document format.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Larry<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> William A Wagner [mailto:wamwagner@comcast.net] <br><b>Sent:</b> Saturday, April 20, 2013 10:23 AM<br><b>To:</b> 'Michael Sweet'; 'larryupthegrove'<br><b>Cc:</b> cloud@pwg.org<br><b>Subject:</b> RE: [Cloud] Cloud Imaging model requirement draft<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Larry and Michael, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I do not see either the rational or advantage in separating the Cloud Imaging Service in the model into separate Service entities. The Semantic Model is constructed on the basis of an MFD, which can support any one or more of the imaging services. I do not understand why this model does not hold equally when the path goes via a Cloud based server.<o:p></o:p></span></p><h4 style='margin-left:0in;text-indent:0in;mso-list:none'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;font-weight:normal'>A Cloud Model that has a Cloud Imaging Server, with which the Client interfaces using the sort of operations defined in the Common Semantics document (e.g., </span><a name="_Toc291529135"></a><a name="_Toc250912744"></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>Create<service>Job</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:normal'> ) and with which a Cloud Imaging Manager interfaces using the “reverse” set of operations (e.g., </span><span style='font-weight:normal'>Fetch<service>Job</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>) </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;font-weight:normal'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>is neither inconsistent with the SM nor an unreasonable model<span style='color:#1F497D'>. <o:p></o:p></span></span></h4><h4 style='margin-left:0in;text-indent:0in;mso-list:none'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;font-weight:normal'>The existing Semantic Model provides a uniform way in which an imaging device or a set of software appears to interfacing entities. Defining separate ‘services’ is a functional rather than physical division. The semantic model did not define separate servers. The reason the service specifications were separate was for the very practical consideration that getting one complete spec written and approved would have been an even longer and difficult task, and there was concern that members and their companies would lose interest. Specifying some services before considering the common model, and documenting the common model before the nature of each of the individual services was considered did, as Mike indicates, result in some inconsistencies that need to be rectified. I do not agree that this resulted in each introducing a slightly different version of the common schema beyond what was inherent in the specific nature of the service. I think it worthwhile for the Semantic Model group to consider a single Common Model update that includes each of the individual services, and I think we should discuss this both for its conceptual preferability and in terms of resources.<o:p></o:p></span></h4><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>An overall Semantic Model document may be divided into common, document input and document output services in the discussion; that should be considered in formatting the document. But I question whether the model itself should be collapsed. With respect to defining a C</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>loud Scan/FaxIn/EmailIn service that provides storage, it is unclear why this is preferable to a Cloud Imaging Service that includes Scan, FaxIn, EmailIn and Resource functional services (as well as the other Imaging Services).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In short, I understand that there may be valid alternate solutions that appear, to some, to have advantages over the current one. But we have an approach that is not broken and into which a lot of effort has been invested. I suggest that we need consider very carefully before we take off on a different route.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Larry, in an effort to continue keep Cloud modeling going, I propose to update sections 1-3 of your wd-cloudimagingmodel10-20130206.docx with the additional changes that have been discussed over the past few months in regard to the Cloud Printing Model. Please let me know if you prefer a different approach.<span style='color:#1F497D'><o:p></o:p></span></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner<o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> [<a href="mailto:cloud-bounces@pwg.org">mailto:cloud-bounces@pwg.org</a>] <b>On Behalf Of </b>Michael Sweet<br><b>Sent:</b> Friday, April 19, 2013 3:59 PM<br><b>To:</b> larryupthegrove<br><b>Cc:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> Re: [Cloud] Cloud Imaging model requirement draft<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Larry,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 2013-02-07, at 2:38 PM, larryupthegrove <<a href="mailto:larryupthegrove@comcast.net">larryupthegrove@comcast.net</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;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.<o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Thanks for this, and apologies that it has taken me this long to review it...<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='color:black'>...</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>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></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I believe there could eventually be a Copy and a Device Administration set of requirement documents as well.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf"><span style='color:purple'>ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf</span></a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx"><span style='color:purple'>ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx</span></a><o:p></o:p></span></p></div></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Device Administration is out of scope. We are not defining an interface for remote device management.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Andale Mono","serif";color:black'>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><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. <o:p></o:p></p></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>