attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Pete,<div><br></div><div>I like the direction of this draft, some quick comments (we can go into detail at the next concall, Nov 18th):</div><div><br></div><div>- (Editorial) All of the tables seem to be using the IEEE paragraph style; just re-style using Normal to get the proper row spacing…</div><div><br></div><div>- I think we want a new operation code for Get-Next-Scan-Document rather than re-using the Send-Document op code. Op codes are cheap and these operations have completely different semantics (different direction of data flow, etc.) Also, given our renaming of AddHardcopyDocument to AddDocumentImages for SM 3.0 and IPP FaxOut, I suggest the name Get-Document-Images for IPP Scan.</div><div><br></div><div>- For Get-Next-Scan-Document/Get-Document-Images, I think we want the document-format-accepted attribute from IPPSIX in the request - that will allow the Client to specify the formats it is able to consume, and the scanner can (re)package the document images up as appropriate. The document-format should be part of the response as well. The order of document-format-accepted values specifies the Client’s preferred format… Alternately we could add document-format-accepted to the Create-[Scan-]Job request - that might be more consistent and allow a spooling service to pre-fetch the document images in the preferred format. (I’d still put the document-format in the Get response…)</div><div><br></div><div>- Regarding note 1 on page 20, we deprecated Restart-Job, Purge-Jobs, and Reprocess-Job because of the accounting issues; I think the “Resubmit-Job” operation here is a typo (the operation is listed in the table, and 0x002c is “Reprocess-Job” - same bug is in IPP FaxOut...)</div><div><br></div><div>- Create[-Scan]-Job: Should add (optional) destination-uris to the operation attributes group; if omitted, creating a pull job…</div><div><br></div><div>- We should sync up input-attributes from FaxOut with this spec; in particular:</div><div><br></div><div>— None of the input-xxx attributes are defined in RFC 2911…</div><div><br></div><div>— input-color-entry was simplified to input-color-mode in FaxOut. If we want to provide greater control over the representation of colors then I suggest we re-use the pwg-raster-document-type-supported keywords; we certainly can’t use the old SM Scan keywords as-is since IPP keywords are hyphenated-lowercase instead of TitleCase. However, I personally feel that input-quality + input-color-mode are enough to cover 1-bit, 8-bit, and 16-bit grayscale and 24-bit or 48-bit RGB color; I’m not aware of any scanners that can produce an actual CMYK separation image (all of them convert from RGB) so there seems little point in supporting CMYK explicitly.</div><div><br></div><div>— input-compression-quality-factor is very JPEG-specific. While I understand the motivation for such an attribute, I question whether we need/want a JPEG quality control vs. providing guidance on using input-quality to set baseline JPEG quality factor values (or use it to choose between JPEG/JBIG vs. Flate compression) (alternately maybe we could use MIME media type parameters to specify the file format options?)</div><div><br></div><div><br></div><div><br><div><div>On Nov 5, 2013, at 12:51 PM, 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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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: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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1"><p class="MsoNormal">All,<o:p></o:p></p><p class="MsoNormal">I have posted an initial version of “IPP Scan Service” . Please add IPP Scan to the agenda of the next IPP teleconference.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span style=""><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.pdf">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.pdf</a><o:p></o:p></span></p><p class="MsoNormal"><span style=""><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.pdf">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.pdf</a><o:p></o:p></span></p><p class="MsoNormal"><span style=""> </span></p><p class="MsoNormal"><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.docx">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.docx</a> <o:p></o:p></p><p class="MsoNormal"><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.docx">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-201301105.docx</a> <o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span style="font-family:"Impact","sans-serif";color:navy">Peter Zehler</span><span style="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"><span style="color:blue">Peter.Zehler@Xerox.com</span></a></span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Voice: (585) 265-8755</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">FAX: (585) 265-7441</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">US Mail: Peter Zehler</span><span style="color:#1F497D"><br>
</span><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">800 Phillips Rd.</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">M/S 128-25E</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">
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D"><o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/ipp<br></blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">_______________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div>
</div>
<br></div></body></html>