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 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoTitle, li.MsoTitle, div.MsoTitle
{mso-style-link:"Title Char";
margin-top:0in;
margin-right:0in;
margin-bottom:4.0pt;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial","sans-serif";
color:#1F497D;}
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.TitleChar
{mso-style-name:"Title Char";
mso-style-link:Title;
font-family:"Arial","sans-serif";
color:#1F497D;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Table1Char
{mso-style-name:"Table1 Char";
mso-style-link:Table1;
font-family:"Arial","sans-serif";}
p.Table1, li.Table1, div.Table1
{mso-style-name:Table1;
mso-style-link:"Table1 Char";
margin-top:2.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Arial","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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=MsoTitle><span style='color:windowtext'>Although the introduction in the PWG Print Job Ticket and Associated Capabilities is very informative, it brings to the fore an area of confusion that may not be mine alone and may affect the adoption of the PWG Print Job Ticket as a mechanism for printer characteristics (not just capabilities) communication and job intent communication in a cloud environment.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>What the document describes appears to be an abstract structure rather than a specific entity. Thus the statement “PrintJobTickets are used in a number of ways associated with the PrintJob” . Specifically identified uses are “</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>representation of the defaults” (DefaultJobTicket?) and “in the submission of a PrintJob”. Also identified as using the PrintJobTicket structure (although perhaps with different datatypes) are </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>the </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>PrintJobReceipt and </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>PrintJobTicketCapabilities. All these may be assumed to be specific entities, associated with either a specific submitted print job request/print job or a specific print service. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The entity “used in a job submission protocol to carry the User’s request.” is presumably what is referred to as the “</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>submitted PrintJobTicket”</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>. Is this the same as the “</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>accepted PrintJobTicket”? Or is the </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>“</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>accepted PrintJobTicket” the same as the “</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>PrintJob’s PrintJobTicket” ? And them there is the Job Template which presumably is a Job Ticket not bound to a job (or service). (And since, some have maintained that a Print Job does not exist until a Print Job Request is accepted by a Print Service, is what is submitted with a print job request a Print Job Template?)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Looking for clarification on what is meant by Job Ticket in approved MFD documents, the Scan Service Specification has this definition:<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify;text-autospace:none'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>“Scan Job Ticket - </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>A Scan Job Ticket is a data object that contains an End User’s Scan Intent for document processing, job processing and descriptive job properties of a Scan Job. The job elements apply to the entire Scan Job. The document processing elements will be used for all the Documents within the Scan Job unless overridden at the Document level (See ScanDocumentTicket). The content of a ScanJobTicket is configured by End User through a Scan Client.”<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The Resource Service Specification has this definition:<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:6.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>“Job Ticket - A data object that contains the user’s intent for job-level document processing, job processing and descriptive properties of a job of a Service. …”<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:6.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>(should that have been “Job <u>or </u>a Service?)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>And the Model Specification has this definition<o:p></o:p></span></p><p class=Table1><span style='font-size:10.0pt'>“Job Ticket - A data object that contains a User’s Job-level Intent for Document processing, Job processing and descriptive Job properties of a Job, sent to an MFD Service. Job Elements apply to the entire Job. Document processing Elements apply to all Documents within the Job unless overridden at the Document level (See Document Ticket). The content of a Job Ticket is configured by a User through a Client. “<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From the model viewpoint, it may be reasonable to say that a PrintJobTicket is data object with defined format and contents, and that instances of a PrintJobTicket can be used in several places including Job Request, Job tracking within a Print Service , PrintJobDefaults, definition of PrintJobTicketCapabilities, PrintJobReceipts etc., and wherever else it may be used. (or some more correct statement). Indeed. Such a description showing how the various applications of the PrintJobTicket are related and perhaps derived from each other would be useful. As far as I know, we have not defined a JobTicket that way elsewhere; we have said that the JobTicket is used to communicate the user’s intent in submitting a job request.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>However, with all respect for those who have defined the semantic Model, I think that for Cloud use, it is particularly important that we define the contents of an object with a specific name that is used to define user intent in a job request; and that we define the contents of a similar object with a different name that is used to specify the available capabilities along with necessary additional information about the Print Service. The current document, with perhaps some more information clarifying the uses of the <service>JobTicket, would be a very useful addition to the revised Model specification. But I suggest that the specification of a PWG PrintTicket for Job Request Submission and a PWG Printer characteristics object be a simpler and more explicit presentation of these specific applications of the general PrintJobTicket data object.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></b></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>