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)"><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:0in;
margin-left:.25in;
margin-bottom:.0001pt;
text-align:justify;
page-break-after:avoid;
font-size:12.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";}
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.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.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{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:1491871544;
mso-list-type:hybrid;
mso-list-template-ids:-2079564104 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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'>There will be a Cloud Imaging Model conference call on Monday at 3PM ET, (Noon PT)<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'>AUDIO:</span> <span style='color:#1F497D'>Phone Bridge<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'> Call-in toll-free number (US/Canada): 1-866-469-3239<br> Call-in toll number (US/Canada): 1-650-429-3300 (Primary)<br> Call-in toll number (US/Canada): 1-408-856-9570 (Backup)<br><br> Attendee Access Code: *******#<br> Attendee ID Code: # (empty)<br><br>If you need the Attendee Access code, please email me a request.<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>VIDEO: </span>PWG WebEx. <o:p></o:p></p><p class=MsoNormal>Topic: IPP/Cloud WG <o:p></o:p></p><p class=MsoNormal>Date: Every Monday<o:p></o:p></p><p class=MsoNormal>Time: 3:00 pm, Eastern Daylight Time (New York, GMT-04:00) <o:p></o:p></p><p class=MsoNormal>Meeting Number: 682 763 393 <o:p></o:p></p><p class=MsoNormal>Meeting Password: Printing123 <o:p></o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>To join the online meeting (Now from mobile devices!) <o:p></o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>1. Go to <a href="https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&RT=MiMxMQ%3D%3D">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&RT=MiMxMQ%3D%3D</a> <o:p></o:p></p><p class=MsoNormal>2. If requested, enter your name and email address. <o:p></o:p></p><p class=MsoNormal>3. If a password is required, enter the meeting password: Printing123 <o:p></o:p></p><p class=MsoNormal>4. Click "Join". <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:12.0pt;color:#1F497D'>NOTE that conference uses phone bridge as indicated above, not audio with PWG Webex <o:p></o:p></span></b></p><p class=MsoNormal>To view in other time zones or languages, please click the link: <o:p></o:p></p><p class=MsoNormal><a href="https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&ORT=MiMxMQ%3D%3D">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&ORT=MiMxMQ%3D%3D</a> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>For assistance <o:p></o:p></p><p class=MsoNormal>------------------------------------------------------- <o:p></o:p></p><p class=MsoNormal>1. Go to <a href="https://ieee-isto.webex.com/ieee-isto/mc">https://ieee-isto.webex.com/ieee-isto/mc</a> <o:p></o:p></p><p class=MsoNormal>2. On the left navigation bar, click "Support". <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To add this meeting to your calendar program (for example Microsoft Outlook), click this link: <o:p></o:p></p><p class=MsoNormal><a href="https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAgN0HgWlP05sWLy7lRjCXMtc9FsW9s-XNPklCRd8QoYu&RT=MiMxMQ%3D%3D">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAgN0HgWlP05sWLy7lRjCXMtc9FsW9s-XNPklCRd8QoYu&RT=MiMxMQ%3D%3D</a> <o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;color:#993366'><br></span><span style='font-size:10.0pt'><br></span>Agenda:<br>(1) PWG IP Policy and Minute Taker <br>(2) <span style='color:#1F497D'>Approve</span> <span style='color:#1F497D'>Cloud minutes from February concall (<a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20140204.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/<span style='color:windowtext;text-decoration:none'><u><span style='color:blue'>cloud-concall-minutes-20140224.pdf</span></u></span></a>) <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(3) Consider IPP SIX Cloud Model comparison (</span><span style='font-size:12.0pt'><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud-IPPSIX_Compare_20140321.docx">ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud-IPPSIX_Compare_20140321.docx</a>)</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(4) Review updated Dra</span><span style='color:#1F497D'>ft </span><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20140305.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20140305.pdf</a>, addressing the following<span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Although (we hope) that this document is nearing prototype status, there are several question that have arisen, or that I have, that should be addressed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>There is a requirement that the Cloud Imaging System maintain a log in the format of the PWG Common Log Format.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Does the Cloud System retain the log or do the individual Cloud Services?<o:p></o:p></p><p class=MsoCommentText style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Are the job events and parameters in the PWG Common Log Format Spec sufficient for a Cloud Service/System?<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>It was requested that DocumentFormatAccepted and CompressionAccepted be added as optional elements to the FetchDocument operation. The terms are derived from IPP and do not appear in the Semantic Model. It is understood that these are “preferred” values, not supported values.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Should “preferred” values be added to the Semantic Model?<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The model requires that the Proxy communicate the significant elements and values of a local service (Accessible Element Set) to the corresponding Cloud Service and update them as necessary. Therefore preferred as well as supported values would be known to the Cloud Service. Why should they be included in specific FetchDocument requests? <o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>c.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Or do we have a misunderstanding or disagreement with respect to communicating the Accessible Element Set of Local Service capabilities and description elements to the Cloud Service?<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The Model description should refer to elements in the Semantic Model, not IPP.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Should the Cloud Model explicitly identify Semantic Model elements to be included in Operations Requests and Responses? This may require defining new elements for inclusion in SM3.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Is it necessary/desirable to ensure inclusion of elements corresponding to all IPP SIX attributes in IPP versions of the operations? (not include a mapping in the document, but certainly generating one in a worksheet)<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>It was requested that the GetJobElements operation be added to the Proxy/Cloud interface, presumably to allow the Proxy to maintain a Job Log. Although the intent of this operation is that same as for the GetJobElements operation in the Client-Cloud interface, the access policy restrictions are different. Specifically, for the Proxy interface, the Cloud Service must deny access if the requested job is not one that that Cloud Service has provided to the identified Local Service.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Are there other potential access restrictions as well for the Proxy version?<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Should the Proxy interface version of this operation have a different name, so that defining the access and potential error response information, which is different for the proxy version, does not overly complicate the description of the operation?<o:p></o:p></p><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>Thank You,<o:p></o:p></p><p class=MsoListParagraph style='margin-left:0in'>Bill Wagner<o:p></o:p></p></div></body></html>