Hi Mike,
My two cents.
No - let's keep the name "print-color-mode" to cohere with the
zillion other print-xxx or printer-xxx attributes.
In the new IPP Scanner and Fax objects lets just globally apply
most/many existing IPP Printer attributes in big table(s) with
a rationale for why some attributes are not applicable to the
other multifunction objects.
Unless almost all Printer attributes *are* applicable, which I begin
to suspect is the case (and have a short table of the exceptions).
I think we should reserve use of he "imaging-" prefix for only new
attributes defined first for Scanner, Fax, etc. objects for IPP
Everywhere Second Edition.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Christmas through April:
579 Park Place Saline, MI 48176
734-944-0094
May to Christmas:
PO Box 221 Grand Marais, MI 49839
906-494-2434
On Mon, Apr 18, 2011 at 4:52 PM, Michael Sweet <msweet at apple.com> wrote:
> All,
>> 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?
>> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20110418/ef9747ed/attachment-0001.html>