attachment-0001
Hi Pete,<br><br>Thanks for your good clarifications. I like combining in the single<br>PWG Print Job Ticket spec the job ticket, capabilities, and default<br>job ticket (DMTF settings).<br><br>Therefore, I've incorporated *both* PWG PrintJobTicket and<br>
PrintServiceCapabilities element groups in the scope of my<br>suggested revision:<br><br><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110818.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110818.pdf</a> / doc<br>
- clean with all changes accepted<br><br>
<a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110818-rev.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110818-rev.pdf</a> / doc<br clear="all">- cumulative redlines<br><br>Cheers,<br><br>PS - I'm not very happy about the changed dates for the various <br>
Cloud Imaging first edition (Print) specs - these should be discussed<br>in detail at the Cloud Imaging WG teleconference next Monday.<br><br>- Ira<br><br>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>
Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SWG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102, 0, 204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Christmas through April:<br> 579 Park Place Saline, MI 48176<br> 734-944-0094<br>May to Christmas:<br> PO Box 221 Grand Marais, MI 49839<br> 906-494-2434<div style="display:inline"></div><div style="display:inline">
</div><div style="display:inline"></div><div></div><br>
<br><br><div class="gmail_quote">On Thu, Aug 18, 2011 at 11:54 AM, Zehler, Peter <span dir="ltr"><<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</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"><span style="font-size:11.0pt;color:#1F497D">Ira,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I view the Printer Capabilities and Print Job Ticket as linked. The Print Job Ticket spec I’m drafting describes the different uses of the Print Job Ticket including<u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;color:#1F497D"><span>1)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;color:#1F497D">It is used in a job submission protocol to carry the User’s request. <u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;color:#1F497D"><span>2)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;color:#1F497D">It is used in a PrintJob object to indicate the accepted request that might have been modified to resolve conflicting or unsupported elements.<u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;color:#1F497D"><span>3)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;color:#1F497D">It is used in the PrintJob is to carry the applied PrintJobTickets elements as a PrintJob is processed by the Printer (i.e., PrintJobReceipt/xxx-applied). <u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;color:#1F497D"><span>4)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;color:#1F497D">It is used by the Printer to indicate the default values for the Printer (i.e., PrintServiceDefaults/xxx-default). <u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;color:#1F497D"><span>5)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;color:#1F497D">It is used by the Printer to indicate the capabilities of the Printer (i.e., PrintServiceCapabilities/xxx-supported). <u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;color:#1F497D"><span>6)<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;color:#1F497D">It is used by the Printer to indicate the capabilities of the Printer available without operator intervention (i.e., PrintServiceCapabilitiesReady/xxx-ready). <br>
<br><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I have not written the capabilities section yet but I see it mainly as a table indicating the element name and associated capabilities syntax along with some verbiage to explain the relationships. The capabilities elements are used to indicate if a Print Job Ticket element is supported by the Printer and the supported values.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">For Cloud printing the Client needs a Print Job Ticket. The Client may to know the capabilities and defaults. It is preferable to have a scalable Client that can adapt the capability of a Cloud Printer. Of course a Client can be written to a limited subset of the model but even then it may be useful to examine the capabilities to determine if simple features such as color printing are supported.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I view the Print Job Ticket, its supported elements and allowed values (i.e., capabilities), and its default values as a single specification. I’d also point out that Google Cloud Print uses PPD and PSF as a Ticket, Default and Capabilities as well.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Pete <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:navy">Peter Zehler</span><span style="font-size:11.0pt;color:#1F497D"><br>
<br></span><span style="font-size:10.0pt;color:navy">Xerox Research Center Webster<br></span><span style="font-size:10.0pt;color:navy">Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a></span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">Voice: <a href="tel:%28585%29%20265-8755" value="+15852658755" target="_blank">(585) 265-8755</a></span><span style="font-size:11.0pt;color:#1F497D"><br></span><span style="font-size:10.0pt;color:navy">FAX: <a href="tel:%28585%29%20265-7441" value="+15852657441" target="_blank">(585) 265-7441</a></span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">US Mail: Peter Zehler</span><span style="font-size:11.0pt;color:#1F497D"><br></span><span style="font-size:10.0pt;color:navy">Xerox Corp.</span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">800 Phillips Rd.</span><span style="font-size:11.0pt;color:#1F497D"><br></span><span style="font-size:10.0pt;color:navy">M/S 128-25E</span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">Webster NY, 14580-9701</span><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:#1F497D"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>] <b>On Behalf Of </b>Ira McDonald</span></p>
<div class="im"><br><b>Sent:</b> Thursday, August 18, 2011 10:38 AM<br><b>To:</b> Michael Sweet; Ira McDonald<br></div><b>Cc:</b> <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><div class="im"><br><b>Subject:</b> Re: [Cloud] Revised charter<u></u><u></u></div>
<p></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Hi,</p><div><div></div><div class="h5"><br><br>I believe both the title and description of the new spec need changes:<br><br>(1) Title should be<br> "Mapping of PWG Job Ticket to/from MSPS, PPD, and JDF (PJTMAP)"<br>
- per last week's minutes and our F2F discussion, JDF in scope<br><br>(2) Document filename should be<br> "wd-cloudpjtmap10-yyyymmdd"<br><br>(3) Description should be strictly limited to PWG Job Ticket (the<br>
only normative reference needed for this mapping spec) and<br> name MSPS, Adobe PPD, and CIP4 JDF<br><br>(4) If our scope is expanded to address PrintServiceCapabilities,<br> then a SECOND mapping spec should be written, not a muddy<br>
scope job ticket mapping spec<br><br>(5) Both directory (charter) and prefix (ch) are wrong in this<br> Interim draft, per PWG Naming Policy<br><br>The term "PWG semantic elements" is far too fuzzy to be source<br>
or target for mapping - also there is no proposal to map the vast<br>majority of PWG SM/2.0 elements or objects.<br><br>The urgent issue is non-PWG *job ticket* usage in Cloud offerings <br>- capabilities are and will continue to be advertised and discovered <br>
by a number of different means in Cloud Print implementations.<br><br>Cheers,<br>- Ira<br><br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>
Chair - TCG Embedded Systems Hardcopy SWG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600CC">http://sites.google.com/site/highnorthinc</span></a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Christmas through April:<br> 579 Park Place Saline, MI 48176<br> <a href="tel:734-944-0094" value="+17349440094" target="_blank">734-944-0094</a><br>May to Christmas:<br> PO Box 221 Grand Marais, MI 49839<br> <a href="tel:906-494-2434" value="+19064942434" target="_blank">906-494-2434</a><u></u><u></u></div>
</div><p></p><div><div></div><div class="h5"><p class="MsoNormal" style="margin-bottom:12.0pt"><br><br><u></u><u></u></p><div><p class="MsoNormal">On Wed, Aug 17, 2011 at 8:05 PM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:<u></u><u></u></p>
<div><p class="MsoNormal">The changes look good to me; aside from the editorial comments about the MS licensing of MSPS, and the filename (should be "wd" until approved :) I think we are good to go...<u></u><u></u></p>
<div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I will fix the minutes tonight...<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p><div><div><div><div><div><p class="MsoNormal">
On Aug 17, 2011, at 3:33 PM, William Wagner wrote:<u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p></div></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><div><div><div><p class="MsoNormal">
<span style="font-size:14.0pt">In accord with the information in the minutes of the face-to-face Cloud Meeting minutes of 2 August (<a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20110802.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20110802.pdf</a>), I have revised the existing, approved Cloud Imaging WG charter and posted an interim draft.</span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt"><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/ch-cloud-charter-20110818-rev.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/ch-cloud-charter-20110818-rev.pdf</a></span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt"><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/ch-cloud-charter-20110818.docx" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/ch-cloud-charter-20110818.docx</a></span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt"> </span><span style="font-size:11.0pt"><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:14.0pt">I sought to make changes in a way consistent with the original. In the interests of using concall time effectively, I request that those who prefer different wording or abbreviations post their preferred version, and that discussion be focused on content. One issue that needs to be resolved is under comment W1. “Considering that Semantic Model V2 is not yet formalized, but represents the preferred model, what do we use as a reference? If the to be issued PJT, do we loose mapping to the SM elements related to printer description?”</span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt"> </span><span style="font-size:11.0pt"><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:14.0pt">Since the charter already separated out the print and multifunction document activity milestones, I made no changes to these other than the dates.</span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt"> </span><span style="font-size:11.0pt"><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:14.0pt">(I should also observe the minutes cited above have an incorrect title and date)</span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt">Thanks,</span><span style="font-size:11.0pt"><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:14.0pt"> </span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:14.0pt">Bill Wagner</span><span style="font-size:11.0pt"><u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:14.0pt"> </span><span style="font-size:11.0pt"><u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:11.0pt"> <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:11.0pt"> <u></u><u></u></span></p></div></div><p class="MsoNormal"><span style="font-size:13.5pt"><br>
-- <br>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is <u></u><u></u></span></p></div></div><p class="MsoNormal">
<span style="font-size:13.5pt">believed to be clean. _______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><u></u><u></u></span></p>
</div></blockquote></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal"><span style="font-size:13.5pt;color:black">________________________________________________________________________<br></span><span style="font-size:13.5pt;color:#888888">Michael Sweet, Senior Printing System Engineer, PWG Chair</span><span style="font-size:13.5pt;color:black"><u></u><u></u></span></p>
</div></div><p class="MsoNormal"><u></u> <u></u></p></div></div><div><p class="MsoNormal"><br>-- <br>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is <br>
believed to be clean. <u></u><u></u></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><u></u><u></u></p></div></div></div><p class="MsoNormal"><br><br>-- <br></p><div class="im">This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is <br>believed to be clean. <u></u><u></u></div><p></p></div></div></blockquote></div><br>
<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.