[community-group] Define how far design tokens are expected to be interoperable. (#215)

romainmenke has just created a new issue for https://github.com/design-tokens/community-group:

== Define how far design tokens are expected to be interoperable. ==
Many feature requests are fairly handwavy towards implementations in translation tools.

I've already voiced my concerns about this numerous times and I think it would be helpful for everyone involved to further define the goal of this specification.

I always interpreted the goal as having interoperability between translation tools even when these are tools for different platforms.

These things must be true :
- my translation tool for CSS is no longer maintained, I can swap it with any compliant tool and the output CSS is exactly the same.
- I have a website implementation, but I now also want an iOS app, I can use any compliant tool and have access to all my tokens and all my tokens work the same
- I don't have to spend time on configuration and glue code to smooth over differences

That means that this specification must define exactly how translation tools must behave and that it must not include features that are impossible to define for translation tools.

Firstly I would like to know the position of the specification editors towards this interpretation.

Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/215 using your GitHub account


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

Received on Monday, 17 April 2023 16:41:31 UTC