- From: Louis Chenais via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jan 2022 09:21:07 +0000
- To: public-design-tokens-log@w3.org
## Color format Thanks for your feedback @sbaechler. While I understand your points, I tend to agree with @c1rrus regarding interoperability. The DTCG has 2 main objectives: 1. Create a standard format for design tokens so that people can freely define and use design tokens whatever the tool they're using. 2. Engage with the community and promote best practices. Interoperability is therefore something we really strive for. The more adoption this first specification gets, the better it is. Thus, I also think we should keep the number of permitted color formats in our spec to a minimum. The current format is an hex triplet/quartet. I don't have any preference on the format itself. I only want this value to include a potential alpha value so that users and tools can generate other formats from it. ## Color space > Having that data attached to the color token could be very useful for teams that want to ensure proper conversion, since the color space cannot be inferred from the value itself. I think this could easily be done by including the color space in the token `metadata` property. -- GitHub Notification of comment by ChucKN0risK Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/79#issuecomment-1017270723 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 January 2022 09:21:09 UTC