attachment-0002
<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)"><!--[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;
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";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l2 level1 lfo2;
font-size:14.0pt;
font-family:"Cambria","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l1 level2 lfo4;
font-size:14.0pt;
font-family:"Cambria","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
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.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";
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.styleheading1notboldblack, li.styleheading1notboldblack, div.styleheading1notboldblack
{mso-style-name:styleheading1notboldblack;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l2 level2 lfo5;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleheading1notboldblack0, li.styleheading1notboldblack0, div.styleheading1notboldblack0
{mso-style-name:styleheading1notboldblack0;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l2 level2 lfo6;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
p.styleheading1notboldblack00, li.styleheading1notboldblack00, div.styleheading1notboldblack00
{mso-style-name:styleheading1notboldblack00;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l2 level2 lfo2;
font-size:14.0pt;
font-family:"Cambria","serif";
color:black;
font-weight:bold;}
span.heading1char0
{mso-style-name:heading1char;
mso-style-priority:9;
font-family:"Cambria","serif";
font-weight:bold;}
span.heading2char0
{mso-style-name:heading2char;
mso-style-priority:9;
font-family:"Cambria","serif";
font-weight:bold;}
span.bodytextchar0
{mso-style-name:bodytextchar;
mso-style-priority:99;
font-family:"Calibri","sans-serif";}
span.heading1char00
{mso-style-name:heading1char0;
mso-style-priority:9;
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.heading2char00
{mso-style-name:heading2char0;
mso-style-priority:9;
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.bodytextchar00
{mso-style-name:bodytextchar0;
mso-style-priority:99;
font-family:"Calibri","sans-serif";}
span.balloontextchar0
{mso-style-name:balloontextchar;
mso-style-priority:99;
font-family:"Tahoma","sans-serif";}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Cambria","serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle38
{mso-style-type:personal;
font-family:"Cambria","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle39
{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.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:148526618;
mso-list-type:simple;
mso-list-template-ids:-146499756;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:.25in;
mso-level-legacy-space:0in;
margin-left:0in;
text-indent:0in;
font-family:"Arial","sans-serif";}
@list l1
{mso-list-id:232006760;
mso-list-template-ids:9729752;}
@list l1:level1
{mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level2
{mso-level-style-link:"Heading 2";
mso-level-suffix:space;
mso-level-text:"%1\.%2\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.55in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level3
{mso-level-reset-level:level1;
mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level4
{mso-level-text:"%1\.%2\.%3\.%4\.";
mso-level-tab-stop:1.25in;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
mso-level-tab-stop:1.75in;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2
{mso-list-id:675117133;
mso-list-template-ids:-319017128;}
@list l2:level1
{mso-level-style-link:"Heading 1";
mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level2
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.55in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level3
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level4
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level5
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level6
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level7
{mso-level-suffix:space;
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:"Cambria","serif";
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level1 lfo9
{mso-level-numbering:continue;
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:.25in;
mso-level-legacy-space:0in;
margin-left:0in;
text-indent:0in;
font-family:"Arial","sans-serif";}
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='font-family:"Cambria","serif"'>Glen,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>I was planning on using diagrams from</span><span style='font-family:"Calibri","sans-serif"'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><</span><a href="http://www.linuxfoundation.org/sites/main/files/JTAPI.GSOC_.201104.06.pdf">http://www.linuxfoundation.org/sites/main/files/JTAPI.GSOC_.201104.06.pdf</a>> <span style='font-family:"Cambria","serif"'>and XMLSPY for the PWG model as well as simple drawings using a tool such as Visio created real time. (If you know of other pictures lying around we can use those as well.) Isn’t it possible to throw something together that we can talk to this afternoon? My work time for the remainder of the year is quite limited and beginning the new calendar year I’ll be loaded down with work in a new research area. I would think a discussion might help you in your CPDC work as well as helping me with the PWG Job Ticket spec.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Can we discuss it today…or at least begin a discussion?<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Pete</span><span style='font-size:11.0pt;font-family:"Cambria","serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","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"'> Petrie, Glen [mailto:glen.petrie@eitc.epson.com] <br><b>Sent:</b> Thursday, December 01, 2011 9:19 AM<br><b>To:</b> Zehler, Peter; cloud@pwg.org<br><b>Subject:</b> RE: [Cloud] RE: About PWG Print Job Ticket<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>Peter,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>JTAPI aside, I believe we have a different overall print model; which reduce the situation to a matter of mapping and bindings. I am working on the Common Mobile Print Dialog (Client) (CPDC) for OpenPrinting and would like to use the PWG:PJT. I realize the PWG activities are not specifically concerned with specifying is part of the print chain but I am trying to make the two mesh together. I am doing a write up for OpenPrinting now and will copy you if you are interested. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>Since this type of discussion really take diagrams along with discussion; let me do the write up before we talk.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:[mailto:cloud-bounces@pwg.org]">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>Zehler, Peter<br><b>Sent:</b> Thursday, December 01, 2011 4:07 AM<br><b>To:</b> William Wagner; <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] RE: About PWG Print Job Ticket</span><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Glen, Bill and any interested parties,<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'>I just don’t type well enough to discuss a matter like this in enough detail. It is also a discussion that would work better in real time. I propose we use today’s SM Teleconference slot (phone and LiveMeeting info below) to discuss this productively.<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'>The short answer Glen is that the JTAPI Job maps to a PWG PrintJob operation in a single document job. It maps to a CreateJob, 1*AddDocument/Uri, CloseJob operations in a multiple document Job. The Job in your model closely aligns with a JobTicket in the PWG with the exception that documents(Run Lists in JDF) are not contained in a JobTicket. It should also be noted that the PWG model does not explicitly model a JobDocumentPage though we do have PageOverrides.<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'>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'> <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 style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'>Agenda: Thursday December 1, 3pm EST<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'>1. Identify Minute Taker<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'>2. Job Ticket mapping of PWG/JTAPI/JDF <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:"Courier New"'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><br><b>Audio Information </b><br>Call-in toll-free number (US/Canada): 1-866-469-3239 <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'>Call-in toll number (US/Canada): 1-650-429-3300 <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'>Call-in toll number (US/Canada): 1-408-856-9570 <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'>Attendee access code: (by request only, please contact me if you do not have it).<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><br><b>LiveMeeting URL:</b><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><u><span style='font-family:"Arial","sans-serif"'><<span style='color:blue'><a href="https://www.livemeeting.com/cc/xerox/join?id=PwgSemanticModel&role=attend&pw=LetMeIn">https://www.livemeeting.com/cc/xerox/join?id=PwgSemanticModel&role=attend&pw=LetMeIn</a></span>><span style='color:blue'> </span></span></u></b><b><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:"Arial","sans-serif"'> </span></b><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt;text-autospace:none'><b><span style='font-family:"Arial","sans-serif"'>LiveMeeting First Time Users: </span></b><span style='font-family:"Arial","sans-serif"'><br>To save time before the meeting, <a href="http://go.microsoft.com/fwlink/?LinkId=90703">check your system </a>to make sure it is ready to use Microsoft Office Live Meeting. <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-family:"Arial","sans-serif"'>LiveMeeting Troubleshooting</span></b><span style='font-family:"Arial","sans-serif"'><br>Unable to join the meeting? Follow these steps: <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo8;text-autospace:none'><![if !supportLists]><span style='font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-family:"Arial","sans-serif"'>Copy this address and paste it into your web browser: <br><a href="https://www.livemeeting.com/cc/xerox/join">https://www.livemeeting.com/cc/xerox/join</a> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 lfo9;text-autospace:none'><![if !supportLists]><span style='font-family:"Arial","sans-serif"'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-family:"Arial","sans-serif"'>Copy and paste the required information: <br>Meeting ID: PwgSemanticModel <br>Entry Code: LetMeIn <br>Location: <a href="https://www.livemeeting.com/cc/xerox">https://www.livemeeting.com/cc/xerox</a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><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='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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:[mailto:cloud-bounces@pwg.org]">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>William Wagner<br><b>Sent:</b> Wednesday, November 30, 2011 8:15 PM<br><b>To:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: [Cloud] RE: About PWG Print Job Ticket<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I suggest that the discussion remain on the list in that it is useful for many, particularly those who have not participated in the MFD group. Some of us have been indoctrinated into Pete’s model to various degrees, but I sometimes get the impression that people are agreeing with things that are proposed while having a somewhat different concept, particularly of what a job is and when it is created. Hopefully the job ticket specification can be made sufficiently complete to avoid confusion between the PWG model and others. For example, I was confused about the contention that there were multiple print job tickets associated with a given print job, although this was clarified to mean (I think) that there were multiple data objects of the data type printjobticket associated with a given print job although only one printjobticket data object (thus the stress in the text that what was being discussed was the datatype, something that Glen stated was unnecessary)<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'>Bill Wagner<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 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"'> <a href="mailto:cloud-bounces@pwg.org">cloud-bounces@pwg.org</a> <a href="mailto:%5bmailto:cloud-bounces@pwg.org%5d">[mailto:cloud-bounces@pwg.org]</a> <b>On Behalf Of </b>Petrie, Glen<br><b>Sent:</b> Wednesday, November 30, 2011 4:34 PM<br><b>To:</b> Zehler, Peter; <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> [Cloud] RE: About PWG Print Job Ticket<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>Peter,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>Thanks for providing your model. While I understand it; from your description, I now have an even more fundamental difference than just the Print Job Ticket.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>I would like to continue our dialog as it really helps in understand the model that you and others are using; but, if you want to take it off the mail list; that would be ok with me.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>My fundamental difference is the role and responsibilities you discuss.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>I equate your “Client” with an Application and your “Print Service” with a “Print Client”! That is, the Application invokes a Print Client (think of the old Print Dialog). The Print Client, along with the Print Service capabilities (how that is obtained is another mail thread), provides the user (or maybe the application) with a set of settable print (service, printing) options for each document the user (or maybe the application) wants to print as part of the Print Job. It is the Print Client that creates the Print Job (object). The Print Client submits the Print Job to the selected Print Service. The Print Service can then reject or acceptance the Print Job Request. If accepted the Print Service put the Print Job in the Print Service’s print queue. I believe this what you refer to a “job creation”. In my model, only the Print Client can create Print Jobs and only the Print Service can execute Print Jobs; it is a simple and distinct separation of roles and responsibilities. In both the Cloud and mobile environments, this separate enables a simpler API implementation.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>While I did not discuss Print Status initially, it may or may not be desirable to record job, print-service, printing status in the actual Print Job Ticket; to me, that is just recording keeping and the print status could be recorded in a number of places. To me, the questions are: Does the Application care about print status – no. Does the Print Client care about print status – no. Only the user care about print status. If the Print Job fails, the User will have to invoke a new print request once the failure has been resolved. This makes it possible (maybe desirable) for the Print Service to send status data to a completely separate and independent Print Status Service!! This atomic approach works well in Cloud and mobile where the location of the individual entities can be anywhere and in different security domains. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>Back to the question of how to use your model in/with my model. For any Print Service I create would have a binding to what I call the Print Client or I create a Print Manager that acts as your Print Service.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'>glen<u><o:p></o:p></u></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif";color:blue'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><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"'> Zehler, Peter <a href="mailto:%5bmailto:Peter.Zehler@xerox.com%5d">[mailto:Peter.Zehler@xerox.com]</a> <br><b>Sent:</b> Wednesday, November 30, 2011 11:00 AM<br><b>To:</b> Petrie, Glen; <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Subject:</b> RE: About PWG Print Job Ticket</span><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Glen,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>I believe some of the confusion comes from the differences in various environments on what constitutes a print job. There are many environments that model only single document jobs. For example this is what is used in Windows and Google Cloud Print. Other environment support multi-document Jobs. IPP and WS-Print support multiple document jobs.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Another source of confusion seems to be where a Print Job exists. It is my understanding that the Print Job does not exist until a job creation request (e.g. CreateJob, PrintJob, PrintUri) is accepted by a Printer and a Job is created based on the information in the job creation request. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>I would modify your single document job model slightly<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | Print Job Status <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Print Job => | Print Job Content (by value or reference) <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | Print Job Ticket => | Print Job Description<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | Print Job Processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> |Print Document Processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job is the job object created by the Print Service and contains the job attributes and state <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Status is the set of attributes maintained by automata for the job (e.g., JobState, ImpressionsCompleted)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Content is the Document data <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where Print Job Ticket is the container element for the accepted descriptive and processing intent<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Description is the Job level descriptive elements (e.g., JobName, DocumentFormatSupplied). (your Print Job Info and Job Content)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Processing is the set of Job level processing intents (e.g., JobPriority). (your Print Job Info)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document Processing is the set of attributes applied the Print Job Content (e.g., Sides, Copies) (your Print Job Ticket). <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>In a single document job submission the Client supplies the Print Job Content and optionally a Print Job Ticket in the job creation request. The Printer copies, ignores or substitutes as appropriate when creating the Print Job.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>The multiple document job model looks like<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Print Job => | Print Job Status<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | Print Job Ticket => | Print Job Description<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | | Print Job Processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | |Print Document Processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> |Print Documents=> |Print Document=> | Print Document Status<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | Print Document Content (by value or reference)<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-family:"Cambria","serif"'> | Print Document Ticket => | Print Document Description<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'> |Print Document Processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job is the job object created by the Print Service and contains the job attributes and state <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Status is the set of attributes maintained by automata for the job (e.g., JobState, ImpressionsCompleted)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where Print Job Ticket is the container element for the accepted descriptive and processing intent<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Description is the Job level descriptive elements (e.g., JobName, DocumentFormatSupplied). (your Print Job Info and Job Content)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Processing is the set of Job level processing intents (e.g., JobPriority). (your Print Job Info)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document Processing is the set of attributes applied the Print Document Content (e.g., Sides, Copies) (your Print Job Ticket). (Note: These values are used unless overridden at the document level)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Documents is the container object created by the Print Service for the contained Document(s) <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document is the document object created by the Print Service and contains the document attributes and state <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document Status is the set of attributes maintained by automata for the Document (e.g., DocumentState, ImpressionsCompleted)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document Content is the Document data <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document Description is the Job level descriptive elements (e.g., JobName, DocumentFormatSupplied). (your Job Content)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Document Processing is the set of attributes applied the Print Document Content (e.g., Sides, Copies) (your Print Job Ticket). <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>In a multiple document job submission the Client optionally supplies a Print Job Ticket on the job creation request. The Print Document Content and optionally the Print Document Ticket are supplied in the add document/uri request. The Printer copies, ignores or substitutes as appropriate when creating the Print Job or Print Document.<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:"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"'> Petrie, Glen <a href="mailto:%5bmailto:glen.petrie@eitc.epson.com%5d">[mailto:glen.petrie@eitc.epson.com]</a> <br><b>Sent:</b> Wednesday, November 30, 2011 12:30 PM<br><b>To:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a>; Zehler, Peter<br><b>Subject:</b> About PWG Print Job Ticket<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Peter,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>After reviewing of the later content of the Print Job Ticket specification, I realize what is called a Print Job Ticket in the specification is what I have always understood to mean the Print Job. And, what is called the Document Ticket is what I have always understood to mean the Print Job Ticket. For example, in JTAPI, the attribute in the specification that are associated with the Document Ticket are those associated in JTAPI with a Print Job Ticket.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Perhaps you can provide me a reference for a Print Job.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>My understanding is that a Client submits a Print Job to a Print Service. A Print Job consists of a Print Job Ticket and Print Job Content (Document) and Print Job Info (parts of what you call PrintJobDescription and PrintJobProcessing).<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>My model <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='font-family:"Cambria","serif"'>| Print Job Info<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Print Job => | Print Job Ticket<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='font-family:"Cambria","serif"'>| Print Job Content<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Info is the set of attributes you have that start with ‘Job’.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Ticket is the set of attributes applied the Print Job Content; what you call DocumentTicket/Processing.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Where the Print Job Content is the set of “documents” and attributes that you generally have that start with ‘Document’<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>In the specification the model is sort of like mine but the ‘labels’ are different and some elements/attributes moved around. The closet analog is<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='font-family:"Cambria","serif"'>| Print Job Processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Print Job Ticket => | Print Document Processing (could be Print Document Ticket)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='font-family:"Cambria","serif"'>| Print Job Description <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Since the PWG:PJT models, object and attributes are, I assume, based on IPP-isms and naming conventions; I believe the best solution is mapping of the PWG:PJT in binding code for support of the PWG:PJT.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>So, I retracted my comments made yesterday and I will focus on bindings and/or mappings of the PWG:PJT.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'>Glen<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p><p class=MsoNormal><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. <o:p></o:p></p><p class=MsoNormal><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. <o:p></o:p></p><p class=MsoNormal><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. <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>