- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Wed, 17 Dec 2025 20:21:30 +0000
- To: public-design-tokens-log@w3.org
Crissov has just created a new issue for https://github.com/design-tokens/community-group: == Color: use 'color model' instead of 'color space' == ### Problem area Specification ### Problem The [Design Tokens Color Module 2025.10](https://www.w3.org/community/reports/design-tokens/CG-FINAL-color-20251028/#supported-color-spaces) correctly specifies the terms _color space_ and _color model_ in it terminology section (3), but then goes on to refer to "color spaces" where "color models" would be more appropriate, especially in the heading of sub-section 4.2. It does not make sense (anymore) to also change the `colorSpace` property of the `$value` property. ### Suggested fix The heading of section 4.2 (and references to it) should read: "Supported color models". I do *not* propose to regroup its subsections hierarchically by space first and model second. The prose could point out that some color spaces are almost always used with the same single color model and that the terms are mostly synonymous then, whereas other spaces – sRGB in particular – have many models representing their colors. ### Required - [x] I have searched [existing issues](https://github.com/design-tokens/community-group/issues) and there is not already an open issue on the subject. - [x] I have read and agree to abide by the [CODE_OF_CONDUCT](https://github.com/design-tokens/community-group/blob/CODE_OF_CONDUCT.md) Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/370 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 December 2025 20:21:31 UTC