- From: Nate Baldwin via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Nov 2022 14:46:13 +0000
- To: public-design-tokens-log@w3.org
@Shrinks99 recommendation here is spot on: 1. Per channel integer floats 2. Color space as another field I would go a step further to suggest some consideration around whether the channels should or should NOT be labeled. In other words, channel values as an array. The reason for that is colors are defined as tuples in all color spaces, and the association of what those values represent is done via color space. So an sRGB color may be represented like this: ``` value: [0, 0.5, 1], colorspace: 'sRGB' ``` Regarding floats, you may not need any defined bit depth, or really any "support" for depth— just capture precise decimal values and consuming applications can match closest supported depths on their end. Finally, regarding the color space field, it is worth starting with ICC profiles— these are common in the industry for standardizing how colors are interpreted and converted between spaces. It doesn't account for all spaces that designers may use, but will ensure standards for common ones like sRGB, cmyk, etc. -- GitHub Notification of comment by NateBaldwinDesign Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/79#issuecomment-1327588883 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 November 2022 14:46:15 UTC