Found 1 record.
Status: Reported (1)
RFC 7986, "New Properties for iCalendar", October 2016Source of RFC: calext (art)
Errata ID: 5449
Publication Format(s) : TEXT
Reported By: Дилян Палаузов
Date Reported: 2018-08-03
Section 5.9 COLOR Pr says:
Description: ...The value is a case-insensitive color name taken from the CSS3 set of names, defined in Section 4.3 of [W3C.REC-css3-color- 20110607]. Example: The following is an example of this property: COLOR:turquoise
It should say:
Description: ...The value is either a case-insensitive color name taken from the CSS3 set of names, defined in Section 4.3 of [W3C.REC- css3-color-20110607], or a lower-cased rgb() functional notation with absolute values specified in Section 4.2.1 of the same document. Examples: The following are examples of this property: COLOR:turquoise COLOR:rgb(61\,211\,68)
draft-daboo-icalendar-extensions-07 removed the possibily to have RGB colours for COLOR.
CSS3 included color names, that browsers at that time suppored, originating from X11's rgb.txt. The color names and values were randomly chosen. The minimal distance between the colors isn't consistent. One motivation for creating a color name were hardware capabilities - an argument which isn't valid for 20 years now. There is no reason to limit the number of possible values for COLOR. A user interface for choosing a named color has either to offer the user the possibility to choose from a pre-filled list of colors, which could clutter the interface, or let the user choose any RGB color and narrow it later to the closest color with CSS3 name. This narrowing isn't trivial and performing it seems like having an RFC running in itself.