- From: Mattia Astorino via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 08:30:57 +0000
- To: public-design-tokens-log@w3.org
> I want to acknowledge that while the principles of design tokens you shared are good principles, they aren't in the current definition of this specification, so it's hard to be precise about whether they are or are not correctly applied.
Isn't something useful and foundamental for the spec that you may consider to add?
> Like @PavelLaptev says, we take advantage of the features of JSON to prevent tokens from having ambiguous values.
yeah, i see now that what technically comes after, like tokens transformation, is up to consumers and it's just a matter of best practices. I still find hard to consider everything as design token cause in this example:
```
{
"link-color": {
"$value": "{color.500}"
},
// later in the file ...
"link-color": {
"$value": "{color.200}"
}
}
```
`link-color` violates the first principle if considered as token, but it doesn't if is considered as theme-key.
--
GitHub Notification of comment by equinusocio
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/187#issuecomment-1333395366 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 08:30:59 UTC