attachment
<div dir="ltr"><div class="gmail_extra"><div>[changed subject to show correct date]<br></div>
<br><br><div class="gmail_quote">On Sat, Dec 7, 2013 at 11:09 AM, William A Wagner <span dir="ltr"><<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal">There will be a Cloud conference call on Monday, <span style="color:#1f497d">9 December </span>at 3PM E<span style="color:#1f497d">S</span>T (Noon PDT). <span style="color:#1f497d">This will probably be the last Cloud conference call of the year.</span><u></u><u></u></p>
<div class="im"><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal" style="margin-bottom:12.0pt"> Call-in toll-free number (US/Canada): <a href="tel:1-866-469-3239" value="+18664693239" target="_blank">1-866-469-3239</a><br>
Call-in toll number (US/Canada): <a href="tel:1-650-429-3300" value="+16504293300" target="_blank">1-650-429-3300</a> (Primary)<br> Call-in toll number (US/Canada): <a href="tel:1-408-856-9570" value="+14088569570" target="_blank">1-408-856-9570</a> (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.<u></u><u></u></p></div><p class="MsoNormal">PWG WebEx. <u></u><u></u></p><div class="im">
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Topic: IPP/Cloud WG <u></u><u></u></p><p class="MsoNormal">Date: Every Monday, from Monday, September 23, 2013 to no end date <u></u><u></u></p><p class="MsoNormal">
Time: 3:00 pm, Eastern Daylight Time (New York, GMT-04:00) <u></u><u></u></p><p class="MsoNormal">Meeting Number: 682 763 393 <u></u><u></u></p><p class="MsoNormal">Meeting Password: Printing123 <u></u><u></u></p><p class="MsoNormal">
<u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">------------------------------------------------------- <u></u><u></u></p><p class="MsoNormal">To join the online meeting (Now from mobile devices!) <u></u><u></u></p>
<p class="MsoNormal">------------------------------------------------------- <u></u><u></u></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" target="_blank">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&RT=MiMxMQ%3D%3D</a> <u></u><u></u></p>
<p class="MsoNormal">2. If requested, enter your name and email address. <u></u><u></u></p><p class="MsoNormal">3. If a password is required, enter the meeting password: Printing123 <u></u><u></u></p><p class="MsoNormal">
4. Click "Join". <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">To view in other time zones or languages, please click the link: <u></u><u></u></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" target="_blank">https://ieee-isto.webex.com/ieee-isto/j.php?ED=152699422&UID=1183762542&PW=NYTM5NTNhNjUy&ORT=MiMxMQ%3D%3D</a> <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">------------------------------------------------------- <u></u><u></u></p><p class="MsoNormal">For assistance <u></u><u></u></p>
<p class="MsoNormal">------------------------------------------------------- <u></u><u></u></p><p class="MsoNormal">1. Go to <a href="https://ieee-isto.webex.com/ieee-isto/mc" target="_blank">https://ieee-isto.webex.com/ieee-isto/mc</a> <u></u><u></u></p>
<p class="MsoNormal">2. On the left navigation bar, click "Support". <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">To add this meeting to your calendar program (for example Microsoft Outlook), click this link: <u></u><u></u></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" target="_blank">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> <u></u><u></u></p>
<p class="MsoNormal"></p><div class="im"><span style="font-size:10.0pt;color:#993366"><br></span><span style="font-size:10.0pt"><br></span>Agenda:<br><br>(1) PWG IP Policy and Minute Taker <br></div>(2) <span style="color:#1f497d">Approve</span> <span style="color:#1f497d">Cloud minutes from </span><span style="color:#1f497d">November 18 (<a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20131118.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20131118.pdf</a>)</span><u></u><u></u><p>
</p><p class="MsoNormal">(3) Review <span style="color:#1f497d">update to the Cloud Requirements and Model document at </span><u></u><u></u></p><p class="MsoNormal"><span style="color:#1f497d"> <a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.pdf</a></span> <u></u><u></u></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" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131125.docx</a><u></u><u></u></span></p>
<p class="MsoNormal" style="text-indent:.5in"><span style="color:#1f497d">(also accessible at <a href="http://xxx" target="_blank">http://xxx</a>)<u></u><u></u></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="color:#1f497d"><u></u> <u></u></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 <a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131115-rl.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudimagingmodel10-20131115-rl.pdf</a>.<u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Extracting from the minutes of that call, actions/comments are in red.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></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<u></u><u></u></span></p>
<p class="MsoNormal">c. <a href="http://4.2.1.2" target="_blank">4.2.1.2</a>: must -> MUST for items 3 and 4 –<span style="color:red"> Reworded to avoid use of conformance terms.</span><u></u><u></u></p><p class="MsoNormal">
d. 4.2.1.2 IdentifyDevice<u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">Q: Do we want the Cloud Imaging Service to be able to cancel <u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">identify operations?<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">A: Maybe<u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">How to do it with IPP?<u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">‘cancel’ keyword for identify-actions? <span style="color:red">OK</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">IIG2: provide guidance on recommended durations, each <u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">identify-printer operation replaces the previous actions (if not <u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">expired), what to do for display (replace, alternate, ??? <u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">discuss in IPP WG)<u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">
Action: Mike to post adding identify-actions = ‘cancel’ and <u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">‘identifying-printer’ printer-state-reasons to IPP list<u></u><u></u></p><p class="MsoNormal">e. Global: fix lowercase musts <span style="color:red">OK</span><u></u><u></u></p>
<p class="MsoNormal">f. Global: check spelling <span style="color:red">OK</span><u></u><u></u></p><p class="MsoNormal">g. <a href="http://4.2.2.1" target="_blank">4.2.2.1</a>:<u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">
Lines 894-897 should be numbered list <span style="color:red">OK</span><u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">Expand a bit on the kinds of notifications that are supplied: jobs are <u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">fetchable, identify device is pending, jobs were canceled, etc. <span style="color:red">OK</span><u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in"><a name="142cdd28268ad37a_2"></a>Line 950: end -> cancel, capitalize identify actions <span style="color:red">OK</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Item 4: Include job elements instead of separate UpdateJobState <u></u><u></u></p><p class="MsoNormal" style="margin-left:.5in">operation <span style="color:red">Job State should be adequate</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Item 5: IdentifyActions instead of DeviceIdentifyRequest<span style="color:red"> OK</span><u></u><u></u></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?<u></u><u></u></span></p>
<p style="margin-left:1.0in"><u></u><span style="font-family:"Courier New""><span>o<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><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><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">identify actions include new set of actions <span style="color:#c00000">OK</span><u></u><u></u></p><p class="MsoNormal">h. Table 2: <u></u><u></u></p><p class="MsoNormal"><span style="font-family:"MS Mincho"">⁃</span><u></u><u></u></p>
<p class="MsoNormal">Add GetJobElements, GetDocumentElements (standard SM <u></u><u></u></p><p class="MsoNormal">operations) <span style="color:#c00000">Question need for these if job status changes are now reported in GetSystemNotitications<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">Thanks,<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1f497d">Bill Wagner<u></u><u></u></span></p>
</div></div></blockquote></div><br></div></div>