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)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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><o:p> </o:p></p><p class=MsoNormal>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></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cloud Imaging Requirements and Model<o:p></o:p></p><p class=MsoNormal>Overview section with definitions for each service:<o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'>Cloud Fax<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Cloud Print<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Cloud Scan<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal>Single function devices only supports one service, multifunction is support for two or more services.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I followed the latest Cloud Printing Model and Requirements as a guide. My thinking was to use the Cloud Imaging document as an overview, with all the specific use cases, sequence drawings, and other specific service details being contained in referenced documents. This would hopefully allow each specific service requirements document to be updated or changed without impacting the imaging document. The drawings and verbiage is in a draft mode, I did a lot of cut/paste/replace.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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></p><p class=MsoNormal>I believe there could eventually be a Copy and a Device Administration set of requirement documents as well.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.pdf</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx">ftp://ftp.pwg.org/pub/pwg/cloud/white/wd-cloudimagingmodel10-20130206.docx</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Larry<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><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>