attachment-0001
<html><body>
<p>Comments against the non-red-lined PDF version of the document.<br>
<br>
<br>
Page 2 line 58: Title here doesn't match the front.<br>
<br>
Page 2 Footer: Change all footers to 2009-2011.<br>
<br>
Page 12 line 539: This sentence is restating the same sentence from the previous page<br>
scope section....(remove)<br>
<br>
Page 19 line 617: broken reference (there are 15 total broken references from a search<br>
on the word Error! in the PDF)<br>
<br>
Page 22 line 669: the word Hardcopy doesn't need up-casing.<br>
<br>
Page 25 line 707: the words " more appropriately" are not necessary<br>
<br>
Page 28 line 767: Content Regions should be Content Region.<br>
<br>
Page 29 line 805: the acronym SDSF is used before it's defined, need to spell it out here<br>
or move the definitions before.<br>
<br>
Page 30 line 825: "1 ton Documents"????<br>
<br>
Page 31 line 868: No figure reference after the word Figure.<br>
<br>
Page 33 line 901: double periods in sentence<br>
<br>
Page 35 line 944: PDF file shows two RED commas in the sentence.<br>
<br>
Page 38 line 989: Need a period, not a comma at the end of the line.<br>
<br>
Page 40 line 1025: Missing (REF) which is in RED.<br>
<br>
page 41 line 1044: Table 4 has forward references listed in the description.<br>
<br>
General comment on description tables (many of the tables have either blank description<br>
columns or blank reference columns....or both....unless the Elements are defined in this<br>
document a reference needs to be included in ALL Element listings in tables.<br>
<br>
Page 77 line 1328 second to last table row: The description for Any is Extension point for status...<br>
should be Extension point for OutputChannelStatus.<br>
<br>
General comment on the Description of the extension point Any....There is a very inconsistent<br>
style of how these are described in the tables (some are blank, some just say Extension point, some<br>
say Extension point for something and some say "extension point for vendor differentiation and <br>
implementation-specific extensions while maintaing interoperability) Suggest simply changing<br>
all to Extension point for "exactly what they extend". Also the word "Any" is inconsistently <br>
upcased or not, sometimes all lower case sometimes upcased throughout the tables.<br>
<br>
Page 77 line 1338: need a period at the end of the sentence.<br>
<br>
Page 82 line 1365 last row in table: Example of the General comment on the Any extension point,<br>
and Processor is spelled wrong.<br>
<br>
Page 86 line 1387 row 12 of table: unnecessary period in third column, and odd character in forth.<br>
<br>
Page 87 line 1401: period spacing mid-line.<br>
<br>
Page 91 line 1428: double semi-colons<br>
<br>
Page 91 line 1450: What's the star for??<br>
<br>
Page 93 line 1486: spacing of comma mid-line.<br>
<br>
Page 93 line 1492: Section 0 reference (broken)<br>
<br>
Page 94 line 1506: Sentence is split by the figure.<br>
<br>
Page 100 line 1565 Resolution row: What's the star for??<br>
<br>
Page 107 line 1605: comma,period in mid-line<br>
<br>
Page 113 line 1647: Why's the word (Copy) in the figure name?? (multiple instances)<br>
<br>
Page 122 line 1704: Section 0 broken reference<br>
<br>
Page 122 line 1706: Internal reference without the word section.<br>
<br>
Page 122 line 1715: need period at the end of the line<br>
<br>
Page 126 line 1735,1736: comma and period spacing issues (3 instances)<br>
<br>
Page 128 line 1744 StateReasons row: odd symbols in third column.<br>
<br>
Page 128 line 1746: Name of Counter Spec. is not complete.<br>
<br>
Page 130 line 1768-1804: Text is BLUE in the PDF.<br>
<br>
Page 134: Table has odd symbols in column 4 and Counter spec name/REF are incorrect.<br>
Symbols occur in many tables in the References column.<br>
<br>
Page 145 line 1923: period spacing issue<br>
<br>
Page 145 line 1924: the word Vendors is upcased...and why is ONLY a vendor extension point?<br>
In theory it could be extended later by the PWG as well.<br>
<br>
Page 149 line 1947: word spacing issues on the line. All text should be Left justified not<br>
simply justified.<br>
<br>
page 161 line 2008: Specific example of table with no description and no references.<br>
<br>
Page 167 line 2153: word spacing issues.<br>
<br>
Page 170: Blank page needs to be removed, and previously mentioned duplicate figure.<br>
<br>
Page 172 line 2190: missing period<br>
<br>
Page 176 line 2262: merged un-ordered list items (Processing - ) is the start of a new<br>
list item<br>
<br>
Page 178 line 2311: Text in figure overlaps the figure content (CancelJob)<br>
<br>
Page 180 line 2354: Double periods mid-line.<br>
<br>
Page 186 line 2564: NEED NOT is NOT a compliance term....<br>
<br>
Page 195 line 2920: NEED NOT is NOT a compliance term... (also occurs on line 2944,3013)<br>
<br>
Page 199 line 3048: need reference for Counter spec.<br>
<br>
Page 200 line 3110 and 3122: need periods at the end of the sentences<br>
<br>
Page 203 line 3131 second and third to last rows of table: missing references and the "H"<br>
should not be up-cased in MadiaUsedSheets. (also no reference column for this table)<br>
<br>
Page 204 line 3142: Confusing reference to the Counter Spec. Is it 5106.1 or 5106.10??<br>
<br>
Page 205 line 3152: Same Counter Spec. reference issue as previous comment.<br>
<br>
Page 206 line 3182 and 3185: Need a TM after 2600 in both citations of IEEE Std. 2600TM-2008.<br>
<br>
<br>
<i>(See attached file: Lexmark_Overall_Spec_Comments.txt)</i><br>
<font size="4" face="Times New Roman">_____________________________________</font>
<p><img src="cid:20__=0ABBF2ACDFF933CD8f9e8a93df93@lexmark.com" width="164" height="46" alt="LEXMARK"><font color="#666666"> </font><b><font color="#666666"><br>
Jerry Thrasher</font></b><font color="#666666"><br>
Senior Engineer, WW Corporate Standards<br>
C14/082-1, 740 New Circle Rd, Lexington Ky 40550<br>
Office: +1 859 825 4056 Fax: +1 859 232 7628<br>
thrasher(at)lexmark(dot)com</font><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>