[community-group] Define how to handle different versions of the specification (#162)

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

== Define how to handle different versions of the specification ==
This specification should assume that there is a large ecosystem of tools and a large body of static token files.

Tools can be well maintained or not and can be up to date with the latest specification or they might not be.

A single organisation using design tokens might depend on dozens of tools all which will can be in different states.

Users might not always be aware of all the other tools used in an organisation.
Users might not be aware of the exact state of all the tools.
Users **will not** have the ability to influence the tools in use and their state.

**Knowing** what is supported, what will work from A to Z will be non-trivial in a relatively large org once the specification has been through a few updates.

At the moment I could not find anything specific about this in the current specification.

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


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

Received on Friday, 5 August 2022 07:04:03 UTC