- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Jul 2022 10:04:13 +0000
- To: public-design-tokens-log@w3.org
> This doesn't have to be super complicated, but one thing is certain, tagging colour data with a colour space is an absolute must - especially if the goal is making universal interchange format. Otherwise, colour data will be meaningless and subject to open interpretation. Here's my recommendation with respects to colour: Absolutely. That is a bare minimum requirement. > Support for limited subset of colour spaces should be enough, i propose support for [sRGB](https://en.wikipedia.org/wiki/SRGB), [DisplayP3](https://developer.apple.com/documentation/coregraphics/kcgcolorspacedisplayp3?language=objc), and [ACEScg](https://en.wikipedia.org/wiki/Academy_Color_Encoding_System#ACEScg). If colour space info is missing, then sRGB is implied, always. We don't have to embed an entire ICC colour profiles, supplying the colour space as a simple enumeration value is enough. Agree too that a simple enumeration is sufficient, and more interoperable. Suggesting ACEScg fr interchange is interesting, care to say a bit more about it? (I know what it is, and implemented it in color.js; I mean why that particular space if you are going for a very small enumeration of allowed spaces). -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/157#issuecomment-1178799683 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 July 2022 10:04:15 UTC