attachment
<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 15 (filtered medium)">
<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: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:11.0pt;
        font-family:"Calibri",sans-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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle19
        {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.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="color:#1F497D">The specification “PWG 5100.5-2003 Standard for IPP Document Object” covers the Document and associated semantics. Additional comments below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0in;margin-bottom:6.0pt;margin-left:0in">
<span style="font-family:"Impact",sans-serif;color:navy">Peter Zehler</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:navy"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Xerox Corp.</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Global Development Group</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">800 Phillips Rd, 111-04A</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Webster NY, 14580-9701</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Email:
</span><span style="color:#1F497D"><a href="mailto:Peter.Zehler@Xerox.com" target="_blank"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter.Zehler@Xerox.com</span></a><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Office:
<a href="tel:%2B1%20%28585%29%20265-8755" target="_blank">+1 (585) 265-8755</a><br>
Fax: <a href="tel:%2B1%20%28585%29%20265-8755" target="_blank">+1 (585) 422-0238</a></span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Mobile:
<a href="tel:%2B1%20%28585%29%20329-9508" target="_blank">+1 (585) 329-9508</a></span><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org]
<b>On Behalf Of </b>Manchala, Daniel<br>
<b>Sent:</b> Wednesday, April 22, 2015 3:32 PM<br>
<b>To:</b> 'ipp@pwg.org'<br>
<b>Subject:</b> [IPP] Multi-document job questions...<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">RFC 2911 describes a multi-document job:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in"><span style="color:#1F497D">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D">
</span><span style="color:#1F497D">The <b>Send-Document Request </b>operation used for multi-document jobs has a laundry list of Operation Attributes (requesting-user-name, document-name, compression, document-format, etc). Does the IPP submission application
ever query the printer to view these <u>document</u> attributes? Or is the IPP submission application restricted to querying the
<u>job</u> attributes (of the job that contains the said documents)?<br>
<PZ>The “Get-Document-Attributes” is available to the submission application.</PZ><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in"><span style="color:#1F497D">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D">
</span><span style="color:#1F497D">Is there any status related to Documents? (Other than the
<b>Send-Document Response</b> associated with the <b>Send-Document Request</b>?)<br>
<PZ>Similar to a Job the Document object has state. The Document object contains “document-state” and “document-state-reasons” elements to represent the object’s state. See “PWG 5108.01-2011 MFD Model and Common Semantics” section 7.2.3 for the detail on
Document States and State Transitions.</PZ> <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-bottom:12.0pt;text-indent:-.25in"><span style="color:#1F497D">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D">
</span><span style="color:#1F497D">Is there any state related to Documents?<br>
<PZ>Document states are simpler than the Job states. The two non-terminating states are ‘Pending’ and ‘Processing’. The terminating states are ‘Aborted’, ‘Canceled’ and ‘Completed’.</PZ><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D">4.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D">
</span><span style="color:#1F497D">Would a human operator expect to see Documents contained within multi-document jobs as individual entities at the printer? Or is that left as a detail of the printer implementation?<br>
<PZ>UI design is the purview of the implementer. However it should be noted that a Document is a passive object whereas a Job is an active object. In the IPP model it is Jobs that are scheduled and run. Documents only exist within the Job and can only be
processed within a processing Job. Documents can be managed (e.g., cancelled, modified) individually.</PZ><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>