Re: [community-group] Should the spec include more semantic types? (#104)

Thanks for raising this issue @mkeftz. I've since noticed that Interplay has implemented something along the `$usedFor` proposal as an extension. Thanks also to @CITguy for sharing how you've done something similar as an extension for TokenCSS.

For what it's worth, I put tried to compare how various tools let you use/specify the usages of design tokens aa while ago. I was exploring what a suitable set of `$usedFor` keywords might be. You can see my findings here: https://docs.google.com/spreadsheets/d/1NIxopYDkYTovkQHAoCl4wMj5ce5jp_hDjVLZqYqgaKo/edit

However, the format editors have discussed this and decided not to add a `$usedFor` property to the spec for now. While we think it - or something like it - could become a useful addition in the future, we want to keep the scope of initial of the initial spec version focussed on the essentials. We feel this is optional metadata for tokens, and therefore not required for tools to be able to store and exchange design token data with each other.

Once the format manages to gain widespread adoption, we can hopefully see whether there is more demand for this kind of functionality and, if so, what the most common usages are that we need to support.

To that end, I'd encourage you both to document your extensions (if you haven't already), so that others could add support for them to their tools. If extensions like yours gain broad support and usage, that would also provide a very clear "cowpath“ for future spec versions to pave.

In the meantime, we'll close this Github issue though since a decision has been reached not to add this to the spec for the time being.

-- 
GitHub Notification of comment by c1rrus
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/104#issuecomment-1419946133 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 6 February 2023 23:38:14 UTC