Re: [community-group] [RFC] Format specification (#1)

I believe it was related to the version of the file itself, not of the token spec. 

However, you bring a very important point that we need to discuss with tooling vendors at large: should the format be shaped in a way that allows for token-level versioning, or any mechanism that potentially helps with cross-tool conflict resolution between versions of a token set? 

My hunch is that we'll see some tools acting as "design token brokers" in the middle, which are tools that would aggregate tokens and manage them in a way that works for an entire team's ecosystem. Another outcome I foresee will be that a team points all of their tools to a single "token source", which itself handles access management, versioning, and shipping. 

With that in mind, I'd love to hear more about your use-case and perhaps you could even share what you think might solve what you brought up?

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


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

Received on Wednesday, 3 March 2021 03:54:32 UTC