attachment
<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 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-priority:99;
mso-style-link:"Comment Text Char";
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial","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;}
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.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-priority:99;
mso-style-link:"Comment Text";
font-family:"Arial","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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;}
--></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='color:#1F497D'>Thank you Geoff. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Normally corrections are assembled at end of Last Call and made at once so that reviewers do not have a moving target. However, since last call has just started and these corrections are all editorial, I have posted a corrected version.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Unfortunately MS Word flagged a whole bunch of format changes (which I don’t think were made) in the version you sent. But from the red changes, I take your corrections as the following (numbers refer to lines in your copy)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Spelling correction to - <o:p></o:p></span></p><p class=MsoNormal style='text-indent:.5in'><span style='color:#1F497D'>840: queries; <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'>table 2: Communication;<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'> table 4: JobId, </span>corresponding; <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>1282: facsimile; <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>1507: cannot;<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>1633: when the<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>table 6 note 5: associated <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>1793: an<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>figure 11: precedes<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Table 8: elements, impressions, re-registered<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>2236: references<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Table 3: Adding space between </span>JobUuid;<b> JobId, </b>2 places<b><o:p></o:p></b></p><p class=MsoNormal>1708 Adding “and” before CapabilitiesReady (and eliminating the space between Capabilities and Ready, since this is an element name)<span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>On 1421, I meant ‘operationality’ although ‘operation’ might be better<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='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"'> Geoff Soord [mailto:Geoff-Soord@softwareimaging.com] <br><b>Sent:</b> Monday, December 22, 2014 4:01 AM<br><b>To:</b> William A Wagner<br><b>Cc:</b> cloud@pwg.org<br><b>Subject:</b> RE: [Cloud] workgroup last call - updated draft<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>Hi All,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>I have corrected several minor typos and grammatical errors.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>Complements of the season,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>Geoff Soord<o:p></o:p></span></p><p class=MsoNormal><b><i><span lang=EN-GB style='color:#1F497D'>Technology Manger<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span lang=EN-GB style='color:#1F497D'>Software Imaging<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span lang=EN-GB style='color:#1F497D'><a href="http://www.softwareimaging.com">www.softwareimaging.com</a><o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span lang=EN-GB style='color:#1F497D'>+44 1865 989 078<o:p></o:p></span></i></b></p></div><p class=MsoNormal><span lang=EN-GB style='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"'> <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>William A Wagner<br><b>Sent:</b> 22 December 2014 04:44<br><b>To:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> [Cloud] workgroup last call - updated draft<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal>Seasons Greetings!<o:p></o:p></p><p class=MsoNormal>I have posted a new draft of the Cloud Model specfiication at:<o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20141222.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20141222.pdf</a><o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20141222.docx">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20141222.docx</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This draft is for workgroup last call, with comments to be addressed at January 12 Cloud Conference call. After resolution of workgroup comments, updated draft will be put into PWG Last Call to overlap with the February Face-to-face meetings.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This posted draft addresses comments from the December 15 conference call and from a listing of editorial comments from Michael Sweet (many thanks for the detailed review). Several issues are still up for discussion and they are noted as comments in the above cited draft.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Michaels comments were, for the most part accepted. A few that were not are listed below with my reasons. These are open to discussion by the workgroup. (Line numbers refer to December 8 draft.)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Section 2.2: - Cloud Computing: spaces before "a". <WW> This is a direct quote and I believe an ellipsis is the correct way of indicating that there is unrepresented text in the original.<WW><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal>-Section 3.2.3: Is this in-scope? FaxModem in Cloud and scanner in MFD? <WW> This is an example of a possible use case. Indeed, it seems one of the few configurations of Cloud support of FaxOut. I see no reason why it should not be a valid use case. <WW><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Section 3.3.2: Isn't selection of an alternate imaging service (moving the job) out of scope. <WW> This is something that a Cloud Imaging Service could reasonably do when the originally selected local service is unusable, in certain configurations. I see no reason why it should not be a valid use case.<WW><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-Section 3.5.2:- Line 623-624: logging "selected Cloud Imaging Service" (drop Local Imaging Service) <WW> Isn't the Local service operating on a job a significant thing to log?<WW><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Section 4.1.1.1:- Line 847: With respect to the advantages of asynchronous notification, which is alluded to but not specified in this model, do we want to mention long/blocking poll operations? <WW>Some reasonable advantages of asynchronous notification are given. It is unclear to me that the specified polling would necessarily be long or blocking.<WW><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>- Section 4.1.1.2: - Line 856: "synchronization" instead of "synchronism"? <WW> I suggest that synchronism is the state and synchronization is the process by which synchronism is achieved. So I thing that “synchronism” is appropriate here.<WW><o:p></o:p></p><p class=MsoNormal>- Section 4.1.1.2: - Lines 871-873: Jobs can't go from "processing" to "pending", but they might go from processing to processing-stopped <WW> Correct. Furthermore, since loss of communication is determined by the Proxy, Job state change in the Local Service should follow what can be done by an outside client. Table added.<WW><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoCommentText>- Section 4.2.1.2:- Table 3: Add DeregisterService operation?<WW> No, Local Services are not registered. If a service in a Local System is to be removed with respect to a Cloud System, the Local System is re--registered without the subject service.<WW><o:p></o:p></p><p class=MsoNormal>- Section 4.2.2.10.2: - Line 1463-1472: Why the numbers in parenthesis? <WW> These are intended to represent numerical coding value of IdentifyActions element. Perhaps this is too much detail?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Global: settle on consistent term for "document data", "Document Data", "DocumentData", or "Digital Data". <WW> Text is adjusted as follows. DocumentData is used when referring to the Semantic Model Element in a operation. Document Data is used when generally referring to the data stream defining a Document, and defined in the terminology section. "digital data” is used when referring to that form of data, which may or may not be Document Data.<WW><o:p></o:p></p><p class=MsoCommentText><o:p> </o:p></p><p class=MsoNormal>Many thanks to all.<o:p></o:p></p><p class=MsoNormal>Bill Wagner<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><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span lang=EN-GB style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span lang=EN-GB style='font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>Software Imaging: Providing Solutions for the Printer Industry and Mobile Phone Market.<br><br>Software Imaging Limited is a limited company registered in England & Wales.<br>Registered No: 01755090<br>Registered Office: Unipart House, Garsington Road, Oxford, OX4 2PG, UK</span><span lang=EN-GB style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div></body></html>