A summary of named color proposals spurred by the debate over the CSS 3 color module inclusion if X11 Named Colors. Please post feedback and comments to the email@example.com
Proposal: extensible color name profiles
Originally suggested to CSS Working group mailing list at http://lists.w3.org/Archives/Public/www-style/2002May/0203.html by Dylan Schiemann and influenced by http://lists.w3.org/Archives/Public/www-style/2002May/0144.html
CSS2 has the following:
color: keyword; (inherit, transparent, systemColors, etc.)
CSS3 proposes adding:
If css 3 is adding color-profiles, why not consider adding color-name-profiles, such as:
with the profileURL optional, containing a translation table to sRGB, or a set of functions (one for each of several commonly used programming languages).
Thus, all could be expressed as:
color: profile(cns,orange,very dark,vivid,url());
color: profile(crayola,electric lime,url());
color: profile(com.dylanschiemann.www.customColorNames,Lincoln Log,url());
Some of these are of course ridiculously longer than using the shorter syntax.
Browsers could be required to be able to convert colors using a lookup table for named colors, or read the method for that browsers language of choice to do rgb conversions.
I would think this should be optional, but would be very useful for using a standard css syntax for authoring programs. For example, a Dreamweaver like program could offer custom color palettes from a company such as Crayola, create a color picker which would store the colors in this new css syntax, and then offer an rgb export conversion if most browsers did not support this optional color name profile.
Proposal: CNS Colors
Refer to CSS Working group thread at http://lists.w3.org/Archives/Public/www-style/1996Feb/0006.html for Proposal by Chris Lilley.
Proposal: HSL Adjectives
Refer to CSS Working group thread at http://lists.w3.org/Archives/Public/www-style/2001Mar/0098.html for Proposal by Dylan Schiemann.