- From: carlosame via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Jun 2021 15:05:37 +0000
- To: public-houdini-archive@w3.org
> For `device-cmyk` you are quite correct; this is really a color model and, although we try to provide a colorimetric interpretation this is not always possible. `device-cmyk` could have a `colorModel` of `CMYK` and a `colorSpace` of `device-cmyk`. > It is not a general Color object model for the Web platform. Therefore, the terminology has to be understood within the specific, largely historical, confines of CSS syntactic forms If one writes a script today, and then another predefined color space is added to the `color()` function and is used, that script would no longer know which color model is being used. Same thing for custom-profiled colors: I do not know the color model because the Typed OM does not give me that information. Knowing the color model is essential for basic use cases. To be more specific, my suggestion would be to use the values in the "Signature" column of Table 19 in the ICCv4 specification as the possible values for `colorModel`, plus `HSL` and `HWB`. And `colorSpace` could be left as it is now (so the current mapping to syntactic forms is respected). -- GitHub Notification of comment by carlosame Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1044#issuecomment-871485037 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 June 2021 15:05:41 UTC