attachment
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Print Quality Issue resolution</TITLE>
<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2>Peter,</FONT></SPAN></DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2>Seems a reasonable resolution. However, since you
state:</FONT></SPAN></DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial size=2><FONT
face="Courier New">...the value</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>image</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2> seemed the same as</FONT><FONT face="Times New Roman"
size=3> </FONT><FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>photo</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>. The name for this was changed to</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>graphic</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=706514420-10072003><FONT face="Courier New"
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2>I do not understand why the values include both "Graphic" and
"Photo".:</FONT></SPAN></DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial><FONT face="Courier New"
size=2> 'graphic': optimize for
graphic clarity</FONT>
<P align=left><FONT face="Courier New"
size=2> 'photo': optimize for
photo clarity</FONT></P>
<P align=left><FONT face="Courier New"
size=2> 'text': optimize for
text clarity</FONT></P>
<P align=left><FONT face="Courier New"
size=2> 'text-and-graphic':
optimize for both text and graphic clarity</FONT></P>
<P align=left><FONT face="Courier New" size=2></FONT> </P>
<P align=left><SPAN class=706514420-10072003><FONT face="Courier New"
size=2>Bill Wagner</FONT></SPAN></P></FONT></SPAN></DIV>
<DIV><SPAN class=706514420-10072003><FONT face="Courier New"
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=706514420-10072003><FONT face="Courier New"
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=706514420-10072003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Zehler, Peter
[mailto:PZehler@crt.xerox.com]<BR><B>Sent:</B> Thursday, July 10, 2003 3:42
PM<BR><B>To:</B> IPP Discussion List (IPP@pwg.org);
printing-jobticket@freestandards.org;
printing-driver@freestandards.org<BR><B>Subject:</B> [printing-jobticket]
Print Quality Issue resolution<BR><BR></FONT></DIV>
<P align=left><FONT face=Arial size=2>All,</FONT></P>
<P align=left><FONT face="Courier New" size=2>D</FONT><FONT face="Courier New"
size=2>uring the PWG/FSG meeting in Portland we had a discussion about the
IPP</FONT> <FONT face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>print-quality</FONT><FONT face="Courier New" size=2>"</FONT><FONT
face="Courier New" size=2> attribute and FSG's desire to add two new
values,</FONT> <FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>economy</FONT><FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2> and</FONT> <FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>fine</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>, where</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>economy</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2> is lower
than</FONT> <FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>draft</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2> and</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>fine</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2> is higher
than</FONT> <FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>high</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>.</FONT> <FONT face="Courier New" size=2>The FSG
further</FONT><FONT face="Courier New" size=2> propose</FONT><FONT
face="Courier New" size=2>d</FONT><FONT face="Courier New" size=2> the
addition of a new attribute, called</FONT> <FONT face="Courier New"
size=2>"</FONT><FONT face="Courier New" size=2>print-optimize</FONT><FONT
face="Courier New" size=2>"</FONT><FONT face="Courier New" size=2>,
that</FONT> <FONT face="Courier New" size=2>would augment</FONT> <FONT
face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>print-quality</FONT><FONT face="Courier New" size=2>"</FONT><FONT
face="Courier New" size=2> with values of</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>image</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2>,</FONT>
<FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>photo</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>,</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>text</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2>,</FONT>
<FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>text-and-image</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>,</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>save-toner</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2> and</FONT>
<FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>speed</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>.</FONT></P>
<P align=left><FONT face="Courier New" size=2>With regard to</FONT> <FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>economy</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2> and</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>fine</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>,</FONT><FONT face="Courier New" size=2> we agreed that</FONT> <FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>economy</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2> would map to</FONT> <FONT face="Courier New"
size=2>"</FONT><FONT face="Courier New" size=2>print-quality</FONT><FONT
face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>=</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>draft</FONT><FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2> and</FONT> <FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>fine</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2> to</FONT> <FONT face="Courier New"
size=2>"</FONT><FONT face="Courier New" size=2>print-quality</FONT><FONT
face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>=</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>high</FONT><FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>. There may be end
user</FONT> <FONT face="Courier New" size=2>visible</FONT><FONT
face="Courier New" size=2> features that map to multiple</FONT> <FONT
face="Courier New" size=2>attributes. We leave it to specific
print</FONT> <FONT face="Courier New" size=2>domains</FONT><FONT
face="Courier New" size=2> to</FONT> <FONT face="Courier New" size=2>model
these higher level</FONT> <FONT face="Courier New"
size=2>aggregate</FONT><FONT face="Courier New" size=2></FONT> <FONT
face="Courier New" size=2>features. When appropriate we will add needed
elements to the Semantic Model.</FONT></P>
<P align=left><FONT face="Courier New" size=2>There was a lot of push back
on</FONT> <FONT face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>print-optimize</FONT><FONT face="Courier New" size=2>"</FONT><FONT
face="Courier New" size=2>. The main concern was that</FONT> <FONT
face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>print-optimize</FONT><FONT face="Courier New" size=2>"</FONT><FONT
face="Courier New" size=2> contained a mixed bag of items. The two main
categories were content metadata and</FONT> <FONT face="Courier New"
size=2>rendering hints. We finally agreed that the two values</FONT>
<FONT face="Courier New" size=2>'</FONT><FONT face="Courier New"
size=2>save-toner</FONT><FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2> and</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>speed</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2> are implied
by the</FONT> <FONT face="Courier New" size=2>"</FONT><FONT face="Courier New"
size=2>print-quality</FONT><FONT face="Courier New" size=2>"</FONT><FONT
face="Courier New" size=2>.</FONT> <FONT face="Courier New"
size=2></FONT> <FONT face="Courier New" size=2>Since they were</FONT><FONT
face="Courier New" size=2> not required</FONT><FONT face="Courier New"
size=2>, they</FONT><FONT face="Courier New" size=2> were removed.</FONT><FONT
face="Courier New" size=2> The remaining values are needed to direct the
type of optimization</FONT><FONT face="Courier New" size=2>/processing that
will be performed</FONT><FONT face="Courier New" size=2> on the content.
It does not necessarily mean the</FONT> <FONT face="Courier New" size=2>value
describes the</FONT> <FONT face="Courier New" size=2>content</FONT><FONT
face="Courier New" size=2>. </FONT> <FONT face="Courier New" size=2>To
clarify this we changed the attribute name to</FONT> <FONT face="Courier New"
size=2>"</FONT><FONT face="Courier New"
size=2>print-content-optimize</FONT><FONT face="Courier New"
size=2>"</FONT><FONT face="Courier New" size=2>. </FONT> <FONT
face="Courier New" size=2>Finally the value</FONT> <FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>image</FONT><FONT
face="Courier New" size=2>'</FONT><FONT face="Courier New" size=2> seemed the
same as</FONT> <FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>photo</FONT><FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>. The name for this was
changed to</FONT> <FONT face="Courier New" size=2>'</FONT><FONT
face="Courier New" size=2>graphic</FONT><FONT face="Courier New"
size=2>'</FONT><FONT face="Courier New" size=2>.</FONT></P>
<P align=left><FONT face="Courier New" size=2>As a result the following
attribute will be added to the JobX specification in it next
revision.</FONT></P>
<P align=left><FONT face="Courier New" size=2>
print-content-optimize (type2 keyword)</FONT></P>
<P align=left><FONT face="Courier New" size=2>
This attribute refines the value specified by the print-quality</FONT></P>
<P align=left><FONT face="Courier New" size=2>
attribute.</FONT></P>
<P align=left><FONT face="Courier New" size=2>
The standard keyword values are:</FONT></P>
<P align=left><FONT face="Courier New"
size=2> 'graphic': optimize
for graphic clarity</FONT></P>
<P align=left><FONT face="Courier New"
size=2> 'photo': optimize for
photo clarity</FONT></P>
<P align=left><FONT face="Courier New"
size=2> 'text': optimize for
text clarity</FONT></P>
<P align=left><FONT face="Courier New"
size=2> 'text-and-graphic':
optimize for both text and graphic clarity</FONT></P><BR><BR>
<UL>
<UL>
<UL>
<UL>
<P align=left><A name=_MailAutoSig><FONT face=Impact>Peter
Zehler</FONT></A></P>
<P align=left><FONT face=XeroxPeopleNet color=#ff0000>XEROX</FONT></P>
<P align=left><FONT face=Tahoma size=2>Xerox Innovation
Group</FONT></P>
<P align=left><FONT face=Arial size=2>Email:
PZehler@crt.xerox.com</FONT></P>
<P align=left><FONT face=Arial color=#000000
size=2>Voice: (585) 265-8755</FONT></P>
<P align=left><FONT face=Arial color=#000000
size=2>FAX: (585) 422-</FONT><FONT
face=Arial size=2>7961</FONT></P>
<P align=left><FONT face=Arial size=2>US Mail: Peter Zehler</FONT></P>
<UL>
<P align=left><FONT face=Arial
size=2> Xerox
Corp.</FONT></P>
<P align=left><FONT face=Arial
size=2> 800 Phillips
Rd.</FONT></P>
<P align=left><FONT face=Arial
size=2> M/S
128-25E</FONT></P>
<P align=left><FONT face=Arial
size=2> Webster NY,
14580-9701</FONT></P></UL></UL></UL></UL></UL>
<P align=left></P></BLOCKQUOTE></BODY></HTML>