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=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
{font-family:"Arial MT";}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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;}
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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Arial MT";
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{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:306477316;
mso-list-type:hybrid;
mso-list-template-ids:-418318368 1613549208 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:74.25pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
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='color:#1F497D'>I have posted an update to the Cloud Requirements and Model document at</span><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> <a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.pdf</a></span> <o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'><span style='color:#1F497D'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.docx">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.docx</a><o:p></o:p></span></p><p class=MsoNormal style='text-indent:.5in'><span style='color:#1F497D'>(also accessible at <a href="http://xxx">http://xxx</a>)<o:p></o:p></span></p><p class=MsoNormal style='text-indent:.5in'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This update reflects comments from the November 18 conference call reviewing </span> Cloud Imaging Requirements and Model ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131115-rl.pdf.<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Extracting from the minutes of that call, actions/comments are in red.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.5pt;font-family:"Arial","sans-serif"'>b. </span>Page 28: Still have signal duration listed for Identify Printer - <span style='color:red'>Replaced with IdentifyActions<o:p></o:p></span></p><p class=MsoNormal>c. 4.2.1.2: must -> MUST for items 3 and 4 –<span style='color:red'> Reworded to avoid use of conformance terms.</span><o:p></o:p></p><p class=MsoNormal>d. 4.2.1.2 IdentifyDevice<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Q: Do we want the Cloud Imaging Service to be able to cancel <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>identify operations?<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>A: Maybe<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>How to do it with IPP?<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>‘cancel’ keyword for identify-actions? <span style='color:red'>OK</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>IIG2: provide guidance on recommended durations, each <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>identify-printer operation replaces the previous actions (if not <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>expired), what to do for display (replace, alternate, ??? <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>discuss in IPP WG)<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Action: Mike to post adding identify-actions = ‘cancel’ and <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>‘identifying-printer’ printer-state-reasons to IPP list<o:p></o:p></p><p class=MsoNormal>e. Global: fix lowercase musts <span style='color:red'>OK</span><o:p></o:p></p><p class=MsoNormal>f. Global: check spelling <span style='color:red'>OK</span><o:p></o:p></p><p class=MsoNormal>g. 4.2.2.1:<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Lines 894-897 should be numbered list <span style='color:red'>OK</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Expand a bit on the kinds of notifications that are supplied: jobs are <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>fetchable, identify device is pending, jobs were canceled, etc. <span style='color:red'>OK</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><a name=2></a>Line 950: end -> cancel, capitalize identify actions <span style='color:red'>OK</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Item 4: Include job elements instead of separate UpdateJobState <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>operation <span style='color:red'>Job State should be adequate</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Item 5: IdentifyActions instead of DeviceIdentifyRequest<span style='color:red'> OK</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>GetSystemNotifications should return basic event information, like IPP Get-Notifications: job state changes include new job state, job UUID, service URI <span style='color:#C00000'>Only include job state changes as indicated. Isn't Job UUID sufficiently unique so that service URI is unnecessary?<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#C00000'>I remain uncomfortable with this change. GetSystemNotify was not intended to parallel IPP Get-Notification. Indeed, I am not overjoyed at the GetSystemNotifications name because it is as much a send system notifications as it is a get system notifications operation. It is directed to System Control Service, not individual imaging services and was intended only to flag to Proxy that Job status should be checked for identified Imaging Services. Communicating Job specific status at the System Control Service level seems inappropriate to me. The need to add this job specific information to the GetSystemNotifify comes from the objection to a Cloud Imaging Service responding with its Job State in response to an Update Job State operation. I am inclined to think that this response is still necessary, although adding GetJobState would be a (cumbersome) alternative. </span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>identify actions include new set of actions <span style='color:#C00000'>OK</span><o:p></o:p></p><p class=MsoNormal>h. Table 2: <o:p></o:p></p><p class=MsoNormal><span style='font-family:"MS Mincho"'>⁃</span><o:p></o:p></p><p class=MsoNormal>Add GetJobElements, GetDocumentElements (standard SM <o:p></o:p></p><p class=MsoNormal>operations) <span style='color:#C00000'>Question need for these if job status changes are now reported in GetSystemNotitications<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><p class=MsoNormal><span style='color:#1F497D'>On another point, </span> <span style='color:#1F497D'>considering that the who PJT mapping effort was started as a response to Google Cloud Print using PPDs and MSPS for printer capability and job tickets, I was surprised that there was virtually no interest in considering the current Google Cloud Print documentation as a Cloud WG project. I wonder of this reflects the opinion of just the few work group members who attended the conference call or whether it is consensus among all members.<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'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bill Wagner<o:p></o:p></span></p></div></div></body></html>