W3C home > Mailing lists > Public > public-design-tokens-log@w3.org > March 2020

Re: [community-group] [RFC] Format specification (#1)

From: Kevin Powell via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Mar 2020 01:34:56 +0000
To: public-design-tokens-log@w3.org
Message-ID: <issue_comment.created-593720435-1583199295-sysbot+gh@w3.org>
### On Value Types
@mirisuzanne and @blackfalcon I'm also curious about the various types we'd have. I know there are other aspects of the spec being worked on in different modules: Color, Space, Typography, etc. I would imagine they'll be opinionated about the formats of those different values, but I think it's worth discussing here as well.

In thinking about values is there a "best base" value type that exists in each category? A simple example to get the conversation going:

For color, there's HEX, but there's also RGBa. A color may be more accurately represented in RGBa than with HEX. If the token value was stored as an RGBa, the HEX could be derived from RGBa (with the loss of the alpha value), but the inverse is not true. 

Some consumers may not support the alpha value, but token authors may want to supply it.

I'm also ideating out loud, but in a way it's a bit like progressive enhancement. My example color token has the alpha value for consumers that can use it, but for others a simpler HEX can be derived.

Now zoom out from the specifics of color, but think to space (px, rem, em, in, cm?), and typography (px, rem, em, pt) and any others. Are there specific units of measure or representations that serve as the "best base" for the token value?

GitHub Notification of comment by kevinmpowell
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-593720435 using your GitHub account
Received on Tuesday, 3 March 2020 01:34:58 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 3 March 2020 01:34:58 UTC