- From: Marc Edwards via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Jul 2022 00:03:53 +0000
- To: public-design-tokens-log@w3.org
> If we _require_ specification of color spaces and array notation to specify color, we'll be placing an additional burden on many token spec adopters to not only learn the design token format, but possibly a whole new means of specifying colors they already have documented elsewhere in HEX. My concern is that this requirement would be so off-putting that it will limit the adoption of the specification as a whole. As mentioned previously, sRGB can and should be the default when the color space is omitted, which lets people use a simpler format, if they’d like. It will cause massive issues if color spaces aren’t considered as part of the original spec. It’s just not a viable option to ignore color spaces in 2022. -- GitHub Notification of comment by marcedwards Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/137#issuecomment-1194795471 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 July 2022 00:03:55 UTC