attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Pete,<div><br></div><div>Thanks for the update.</div><div><br></div><div>WRT process, yes we continue the Formal Vote, using the original stable draft you posted. The discussion during the concall will be recorded as editorial comments for one or more of the votes cast by members, and we can review the outcome of the vote and your changes in response to our comments at the F2F.</div><div><br></div><div><br></div><div><div><div>On Sep 30, 2014, at 8:45 AM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
@font-face
{font-family:Menlo-Regular;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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: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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
p.IEEEStdsParagraph, li.IEEEStdsParagraph, div.IEEEStdsParagraph
{mso-style-name:"IEEEStds Paragraph";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:4.5pt;
margin-bottom:.0001pt;
text-align:justify;
font-size:12.0pt;
font-family:"Menlo-Regular","serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:445584723;
mso-list-type:hybrid;
mso-list-template-ids:-508132360 67698713 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1"><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">Below are my responses to the “Discussion of IPP Scan” posted in the IPP teleconference meeting minutes.<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">a.
<a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140917.pdf">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140917.pdf</a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ>I now have an updated specification
</span><span style="font-size:12.0pt;font-family:"Cambria","serif""><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20141001.pdf">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20141001.pdf</a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Cambria","serif"">Please let me know what I should do with the updated specification.</PZ><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">b. PWG Formal Vote until October 17, 2014<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ>I assume the formal vote continues.</PZ><o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">c. Editorial comments:<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> Add description of multiple document (object) support/creation - artifact of document-format.<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ>Added a section in 4.1<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">“4.1.1 Documents within a Scan Job<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">From a client’s point of view the number of documents created in a Job is a function of the Scan Service’s capability and the document
format of the Output Image. For example a document format such as JPEG only allows a single image per file. If a stack of documents are being scanned and the Scan Service supports multi-document jobs, then each JPEG file generated will be associated with
a Document within the Scan Job. If the Scan Service did not support multi-document jobs, then only a single sheet from the stack would be scanned resulting in a single document job. If that same stack of documents is scanned using a PDF document format,
the all the Output Images, regardless of multi-document support, will be in a single PDF file associated with a single Document within the Scan Job.”<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""></PZ><o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> Drop compression-accepted and document-format-accepted from Get-Next-Document-Images;
just use the values in the Create-Job request (same for both push and pull scan)<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ>deleted</PZ><o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> Clarify that output to archives is undefined/out-of-scope<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> SM and JDF can do it
<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ /><o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> Add "scan to archive formats" is out of scope
<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ>Added the following to the list of out of scope in section 3.4<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:1.0in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">“Scan to archive formats (i.e., a single document object referencing a container of multiple files)”<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""></PZ><o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> Be silent about what happens if document-format is an archive format<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ /><o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"MS Mincho"">⁃</span><span style="font-size:12.0pt;font-family:"Cambria","serif""> Update Get-Next-Document-Images description to mention each call returns a new document
object containing one or more complete document images (e.g. a JPEG at a time or a PDF at a time, etc.)<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""><PZ><o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">In section 6.1 I changed the description of Get-Next-Document-Images from<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">“The REQUIRED Get-Next-Document-Images operation allows a Scan Client to retrieve a scanned document from an existing job object.
This operation enables pull scanning. The Scan Client specifies the target Scan Job. The Scan Job MUST be in the ‘processing’ or ‘completed’ state. As the scan data becomes available the document content is delivered in the response. To support streaming the
Scan Client MUST support the "chunked" Transfer-Encoding in the response”<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">To<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">“</span><span style="font-size:12.0pt;font-family:"Cambria","serif"">The REQUIRED Get-Next-Document-Images operation allows a Scan
Client to retrieve the scan data from an existing job object. This operation enables pull scanning. The Scan Client specifies the target Scan Job. The Scan Job MUST be in the ‘processing’ or ‘completed’ state. As the scan data becomes available the Scan Job
content is delivered in the response. The response’s operational attribute “document-format” indicates the file type of the data. The document description attribute “document-number” indicates to which document within the job the scan data belongs. If the
document number changes, the previous document is complete. If the operational attribute “last-document” is true the transfer of all documents within the job is complete. To support streaming the Scan Client MUST support the "chunked" Transfer-Encoding in
the response.</span><span style="font-size:12.0pt;font-family:"Cambria","serif"">”<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""> </span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">And in section 6.1.2 in the description of “Group 3: Document content” I changed<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">“The document content is sent in the response as specified in [RFC2910] section 3.1. Note that the Scan Client MUST be ready to
accept a response using the "chunked" Transfer-Encoding.”<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">To<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif"">“</span><span style="font-size:12.0pt;font-family:"Cambria","serif"">The document content, or a portion thereof, is sent in the response
as specified in [RFC2910] section 3.1. Note that the Scan Client MUST be ready to accept a response using the "chunked" Transfer-Encoding.</span><span style="font-size:12.0pt;font-family:"Cambria","serif"">”<o:p></o:p></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:12.0pt;font-family:"Cambria","serif""></PZ><o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span style="font-family:"Impact","sans-serif";color:navy">Peter Zehler<o:p></o:p></span></p><p class="MsoNormal"><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">PARC, A Xerox Company</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">800 Phillips Rd, 128-27E</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><a href="mailto:Peter.Zehler@Xerox.com"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue">Peter.Zehler@Xerox.com</span></a><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Office: +1 (585) 265-8755<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Mobile: +1 (585) 329-9508</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">FAX: +1 (585) 265-7441</span><o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>