attachment-0001
<br><font size=2 face="sans-serif">> </font><font size=2 face="Courier New">We
finally agreed that the two values</font><font size=3> </font><font size=2 face="Courier New">'save-toner'
and</font><font size=3> </font><font size=2 face="Courier New">'speed'
are implied by the</font><font size=3> </font><font size=2 face="Courier New">"print-quality".</font><font size=3>
</font><font size=2 face="Courier New">Since they were not required,
they were removed.</font>
<br>
<br><font size=2 face="sans-serif">I think this warrants further examination.
I have known toner saving methods that do a very good job of preserving
print quality. </font>
<br><font size=2 face="sans-serif">----------------------------------------------
<br>
Harry Lewis <br>
Chairman - IEEE-ISTO Printer Working Group<br>
http://www.pwg.org<br>
IBM Printing Systems <br>
http://www.ibm.com/printers<br>
303-924-5337<br>
---------------------------------------------- </font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Zehler, Peter"
<PZehler@crt.xerox.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: owner-ipp@pwg.org</font>
<p><font size=1 face="sans-serif">07/10/2003 01:41 PM</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">"IPP Discussion List
(IPP@pwg.org)" <IPP@pwg.org>, printing-jobticket@freestandards.org,
printing-driver@freestandards.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">IPP> Print Quality Issue
resolution</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="Arial">All,</font>
<p><font size=2 face="Courier New">During the PWG/FSG meeting in Portland
we had a discussion about the IPP</font><font size=3> </font><font size=2 face="Courier New">"print-quality"
attribute and FSG's desire to add two new values,</font><font size=3> </font><font size=2 face="Courier New">'economy'
and</font><font size=3> </font><font size=2 face="Courier New">'fine',
where</font><font size=3> </font><font size=2 face="Courier New">'economy'
is lower than</font><font size=3> </font><font size=2 face="Courier New">'draft'
and</font><font size=3> </font><font size=2 face="Courier New">'fine' is
higher than</font><font size=3> </font><font size=2 face="Courier New">'high'.</font><font size=3>
</font><font size=2 face="Courier New">The FSG further proposed the addition
of a new attribute, called</font><font size=3> </font><font size=2 face="Courier New">"print-optimize",
that</font><font size=3> </font><font size=2 face="Courier New">would augment</font><font size=3>
</font><font size=2 face="Courier New">"print-quality" with values
of</font><font size=3> </font><font size=2 face="Courier New">'image',</font><font size=3>
</font><font size=2 face="Courier New">'photo',</font><font size=3> </font><font size=2 face="Courier New">'text',</font><font size=3>
</font><font size=2 face="Courier New">'text-and-image',</font><font size=3>
</font><font size=2 face="Courier New">'save-toner' and</font><font size=3>
</font><font size=2 face="Courier New">'speed'.</font>
<p><font size=2 face="Courier New">With regard to</font><font size=3> </font><font size=2 face="Courier New">'economy'
and</font><font size=3> </font><font size=2 face="Courier New">'fine',
we agreed that</font><font size=3> </font><font size=2 face="Courier New">'economy'
would map to</font><font size=3> </font><font size=2 face="Courier New">"print-quality"='draft'
and</font><font size=3> </font><font size=2 face="Courier New">'fine' to</font><font size=3>
</font><font size=2 face="Courier New">"print-quality"='high'.
There may be end user</font><font size=3> </font><font size=2 face="Courier New">visible
features that map to multiple</font><font size=3> </font><font size=2 face="Courier New">attributes.
We leave it to specific print</font><font size=3> </font><font size=2 face="Courier New">domains
to</font><font size=3> </font><font size=2 face="Courier New">model these
higher level</font><font size=3> </font><font size=2 face="Courier New">aggregate</font><font size=3>
</font><font size=2 face="Courier New">features. When appropriate
we will add needed elements to the Semantic Model.</font>
<p><font size=2 face="Courier New">There was a lot of push back on</font><font size=3>
</font><font size=2 face="Courier New">"print-optimize". The
main concern was that</font><font size=3> </font><font size=2 face="Courier New">"print-optimize"
contained a mixed bag of items. The two main categories were content
metadata and</font><font size=3> </font><font size=2 face="Courier New">rendering
hints. We finally agreed that the two values</font><font size=3>
</font><font size=2 face="Courier New">'save-toner' and</font><font size=3>
</font><font size=2 face="Courier New">'speed' are implied by the</font><font size=3>
</font><font size=2 face="Courier New">"print-quality".</font><font size=3>
</font><font size=2 face="Courier New">Since they were not required,
they were removed. The remaining values are needed to direct the
type of optimization/processing that will be performed on the content.
It does not necessarily mean the</font><font size=3> </font><font size=2 face="Courier New">value
describes the</font><font size=3> </font><font size=2 face="Courier New">content.
</font><font size=3> </font><font size=2 face="Courier New">To clarify
this we changed the attribute name to</font><font size=3> </font><font size=2 face="Courier New">"print-content-optimize".
</font><font size=3> </font><font size=2 face="Courier New">Finally
the value</font><font size=3> </font><font size=2 face="Courier New">'image'
seemed the same as</font><font size=3> </font><font size=2 face="Courier New">'photo'.
The name for this was changed to</font><font size=3> </font><font size=2 face="Courier New">'graphic'.</font>
<p><font size=2 face="Courier New">As a result the following attribute
will be added to the JobX specification in it next revision.</font>
<p><font size=2 face="Courier New"> print-content-optimize
(type2 keyword)</font>
<p><font size=2 face="Courier New"> This attribute
refines the value specified by the print-quality</font>
<p><font size=2 face="Courier New"> attribute.</font>
<p><font size=2 face="Courier New"> The standard keyword
values are:</font>
<p><font size=2 face="Courier New"> 'graphic':
optimize for graphic clarity</font>
<p><font size=2 face="Courier New"> 'photo':
optimize for photo clarity</font>
<p><font size=2 face="Courier New"> 'text':
optimize for text clarity</font>
<p><font size=2 face="Courier New"> 'text-and-graphic':
optimize for both text and graphic clarity</font>
<p><font size=3><br>
</font>
<p><font size=3 face="Impact">Peter Zehler</font>
<p><font size=3 color=red>XEROX</font>
<p><font size=2 face="Tahoma">Xerox Innovation Group</font>
<p><font size=2 face="Arial">Email: PZehler@crt.xerox.com</font>
<p><font size=2 face="Arial">Voice: (585) 265-8755</font>
<p><font size=2 face="Arial">FAX: (585) 422-7961</font>
<p><font size=2 face="Arial">US Mail: Peter Zehler</font>
<p><font size=2 face="Arial"> Xerox Corp.</font>
<p><font size=2 face="Arial"> 800 Phillips Rd.</font>
<p><font size=2 face="Arial"> M/S 128-25E</font>
<p><font size=2 face="Arial"> Webster NY, 14580-9701</font>
<p>