attachment-0001
<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 14 (filtered medium)"><base href="x-msg://44/"><!--[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;}
@font-face
        {font-family:Impact;
        panose-1:2 11 8 6 3 9 2 5 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","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.apple-style-span
        {mso-style-name:apple-style-span;}
span.apple-tab-span
        {mso-style-name:apple-tab-span;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.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='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mike,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My responses are in line below. I should have the updated specification and schema posted sometime tomorrow.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Pete<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Impact","sans-serif";color:navy'>Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br><br></span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy'>Xerox Research Center Webster<br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Voice: (585) 265-8755</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>FAX: (585) 265-7441</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>US Mail: Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Xerox Corp.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>800 Phillips Rd.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>M/S 128-25E</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Webster NY, 14580-9701</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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"'> Michael Sweet [mailto:msweet@apple.com] <br><b>Sent:</b> Monday, August 22, 2011 11:50 AM<br><b>To:</b> Zehler, Peter<br><b>Cc:</b> mfd@pwg.org; IPP@pwg.org; cloud@pwg.org<br><b>Subject:</b> Re: [MFD] Initial PWG Print Job Specification Posted<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Aug 19, 2011, at 2:01 PM, Zehler, Peter wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>All,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>An initial draft of the PWG Semantic Model Print Job Ticket (PJT) has been posted. It is available at<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><<a href="ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-PwgPrintJobTicket-20110818.pdf">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-PwgPrintJobTicket-20110818.pdf</a>><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The specification is based on v1.140 of the PWG Semantic Model Schema. See the Semantic Model page for links to the files and to browse an online html version. The Semantic Model web page is available at: <<a href="http://www.pwg.org/mfd">http://www.pwg.org/mfd</a>> (Note: if version 1.140 is not show try refreshing the page.)<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The first review of this specification will occur at the Semantic Model Working Groups 9/1/11 teleconference at 3 pm EDT. I’ll send out a meeting notice closer to the date with all the necessary information.<o:p></o:p></span></p></div></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Not sure if I'll be able to call in, but here are some initial comments from a first read:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- General: Looks like the footer has a lot of extra whitespace in it?<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>Fixed</PZ><o:p></o:p></span></p></div><div><p class=MsoNormal>- Section 1, Introduction<o:p></o:p></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- You jump right in to PrintJobTicket, but never introduce the semantic model (aside from the abstract) - I think it would be useful and appropriate to provide a paragraph or two (and maybe a diagram?) providing the scope of the SM and where PrintJobTicket fits.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ> couple of paragraphs added</PZ><o:p></o:p></span></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- Some mixed usage of PrintJob, Print Job, PrintJobTicket, Print Job Ticket, etc.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>Fixed</PZ><o:p></o:p></span></p></div><div><p class=MsoNormal>- Sections 5.x, 6.x, and 7.x: Datatypes<o:p></o:p></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- I think we do want text here<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>Added</PZ><o:p></o:p></span></p></div><div><p class=MsoNormal>- Section 8: Print Job Ticket Elements’ Semantic information<o:p></o:p></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- Wouldn't Table 1 be better broken up into Description and Processing elements, and put near the fugures? For example, right now if I look at Figure 15 (job processing) I need to search for OutputBin within the document to find out what it means and what the accepted values are.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>We can discuss this at the next teleconference. I prefer a single table that acts as a dictionary of all the semantic elements. There are elements shared between groups and I’d prefer only a single entry. The information is organized a set of summary diagrams, a table with an overview of the semantics, and finally the referenced specification and section that gives the precise semantics.</PZ><o:p></o:p></span></p></div><div><p class=MsoNormal>- Section 9: PrintServiceCapabilities<o:p></o:p></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- Table 2: There is at least one place where the capabilities element has a different name than the job ticket element (e.g. Resolutions vs. Resolution). I don't think we need to add a column, but perhaps we could add the job ticket element in parenthesis when the names don't match?<o:p></o:p></p></div><div><p class=MsoNormal>- Section 10: Simple PrintJobTicket<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>Fixed the capabilities element representation. Also added additional information for MediaCol.</PZ><o:p></o:p></span></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- According to the semantic definition, MediaType is part of MediaCol and not a top-level element in PrintDocumentProcessing.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>MediaType can be used anywhere where Media is used. I added the reference to WS-Print. It would seem cleaner to extend IPP to allow media-type to be a top level attribute. If that does not happen the IPP encoding will require media-col whenever media-type is used.</PZ> <o:p></o:p></span></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- However, the current schema shows MediaType as an optional top-level element in a sequence with Media/MediaSource, which are under a choice???<o:p></o:p></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span>- That doesn't match the IPP definition of media, media-type, or media-source, either... Both media-type and media-source need to be in media-col for IPP, with media/media-col being mutually-exclusive (a choice in XML schema)<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><PZ>I have corrected the media definition in Document Processing. Note that WS-Print requires Media and MediaType as DocumentProcessing elements.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><img border=0 width=455 height=156 id="Picture_x0020_1" src="cid:image001.png@01CC632F.8D292B40"></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I corrected the media definition in MediaCol. MediaType at the same level as the XML choice and can be specified with any of the three media choices.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><img border=0 width=282 height=119 id="Picture_x0020_2" src="cid:image002.png@01CC6330.D896E710"></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'></PZ><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>________________________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p></div><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.
</body></html>