attachment-0001
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Given that we have another attribute for scan (ColorEntry) that has slightly different semantics than print-color-mode, I'm thinking we should keep the print attribute named "print-color-mode".<div><br><div><div>On Apr 19, 2011, at 11:45 AM, Tom Hastings wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--#AVG\_LS\_INLINE\_POPUP
{word-wrap: break-word;
overflow:hidden;
z-index:9999;}
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<div lang="EN-US" link="blue" vlink="blue">
<div class="Section1"><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">I agree with Ira. On the other hand,
one other alternative for the name would just to drop the "print-"
prefix and call it "color-mode".<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">Tom<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">
<hr size="2" width="100%" align="center" tabindex="-1">
</span></font></div><p class="MsoNormal"><b><font size="2" face="Tahoma"><span style="font-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size="2" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma">
<a href="mailto:ipp-bounces@pwg.org">ipp-bounces@pwg.org</a> [mailto:ipp-bounces@pwg.org] <b><span style="font-weight:
bold">On Behalf Of </span></b>Ira McDonald<br>
<b><span style="font-weight:bold">Sent:</span></b> Monday, April 18, 2011 15:35<br>
<b><span style="font-weight:bold">To:</span></b> <st1:personname w:st="on">Michael
Sweet</st1:personname>; Ira McDonald<br>
<b><span style="font-weight:bold">Cc:</span></b> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [IPP]
"print-color-mode" or "imaging-color-mode"?</span></font><o:p></o:p></p>
</div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">Hi Mike,<br>
<br>
My two cents.<br>
<br>
No - let's keep the name "print-color-mode" to cohere with the<br>
zillion other print-xxx or printer-xxx attributes.<br>
<br>
In the new IPP Scanner and Fax objects lets just globally apply<br>
most/many existing IPP Printer attributes in big table(s) with<br>
a rationale for why some attributes are not applicable to the<br>
other multifunction objects.<br>
<br>
Unless almost all Printer attributes *are* applicable, which I begin <br>
to suspect is the case (and have a short table of the exceptions).<br>
<br>
I think we should reserve use of he "imaging-" prefix for only new<br>
attributes defined first for Scanner, Fax, etc. objects for IPP <br>
Everywhere Second Edition.<br>
<br>
Cheers,<br>
- Ira<br>
<br>
<br clear="all">
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Co-Chair - IEEE-ISTO PWG IPP WG<br>
Co-Chair - TCG Hardcopy WG<br>
IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br>
<a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><font color="#6600cc"><span style="color:#6600CC">http://sites.google.com/site/highnorthinc</span></font></a><br>
mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Christmas through April:<br>
<st1:address w:st="on"><st1:street w:st="on">579 Park Place</st1:street> <st1:city w:st="on">Saline</st1:city>, <st1:state w:st="on">MI</st1:state> <st1:postalcode w:st="on">48176</st1:postalcode></st1:address><br>
734-944-0094<br>
May to Christmas:<br>
<st1:address w:st="on"><st1:street w:st="on">PO Box</st1:street> 221</st1:address>
Grand <st1:place w:st="on"><st1:city w:st="on">Marais</st1:city>, <st1:state w:st="on">MI</st1:state> <st1:postalcode w:st="on">49839</st1:postalcode></st1:place><br>
906-494-2434<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
<br>
<o:p></o:p></span></font></p>
<div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">On Mon, Apr 18, 2011 at 4:52 PM, <st1:personname w:st="on">Michael
Sweet</st1:personname> <<a href="mailto:msweet@apple.com">msweet@apple.com</a>>
wrote:<o:p></o:p></span></font></p><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">All,<br>
<br>
If we consider scanning and printing of forms, the "bi-level"
(threshold) mode makes sense for both. Do we want to rename
"print-color-mode" to "imaging-color-mode" in anticipation
of using is for other MFD services in IPP?<br>
<br>
________________________________________________________________________<br>
<st1:personname w:st="on">Michael Sweet</st1:personname>, Senior Printing
System Engineer, PWG Chair<br>
<br>
<br>
--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><o:p></o:p></span></font></p>
</div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/"><b><span style="font-weight:bold">MailScanner</span></b></a>, and is <br>
believed to be clean. <o:p></o:p></span></font></p>
</div>
</div>
</o:smarttagtype></o:smarttagtype></o:smarttagtype></o:smarttagtype></o:smarttagtype></o:smarttagtype></o:smarttagtype></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: 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; font-size: medium; "><div>________________________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></div><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>