- From: Matthew Ström via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Dec 2022 16:47:45 +0000
- To: public-design-tokens-log@w3.org
The genesis of this question came from another question: how should we define the typography composite token (#102) ? It seems like there's general consensus around having an "open" definition, where we have a required set of properties, but accept any number of additional properties. I suggested that the required properties should be the "minimum amount of information necessary to render a given element." My initial suggestion was that font family and font size were all that should be needed to render a piece of text. But, I realized that a lot more is needed, otherwise it's up to the platform to interpret/infer - color, weight, letter spacing, etc. So, I set out to figure out what set of properties is shared across all target platforms ([in progress spreadsheet here](https://docs.google.com/spreadsheets/d/1aC2Q-KH6fuNOjSC02akj7dGb7zS-MoY9qzySmPmlzd0/edit?usp=sharing)) ... and realized we don't have a standard definition of a target platform 😬 To your question: the "open" format does all the above. If the format requires a property, it should be guaranteed to be supported by all platforms and design tools. Beyond that, the spec should allow (but not require) an author to cover any capability that their target platform has, now or in the future. -- GitHub Notification of comment by ilikescience Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/190#issuecomment-1335523569 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 December 2022 16:47:46 UTC