- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Sat, 29 Oct 2022 14:38:16 +0000
- To: public-design-tokens-log@w3.org
> But we need to recall the format aims for data transportation and "easy" human editing. That is not true currently :) The spec only mentions that using JSON has the side effect of being somewhat human-readable. But it doesn't even state that this is a goal or a requirement. It however has been mentioned many times in comments. Which is why I asked for clarifications on this conflict between comments and the spec here : https://github.com/design-tokens/community-group/issues/149 Even when a parser for the current spec **can** be implemented, doesn't mean that it will age gracefully. My concern is the long term. Starting out with a specification that has many implicit and vague parts means that it will be much harder to expand later. Starting with a simpler and explicit format is easier. I would like to see a transfer format that can easily be used in older and newer versions of tools and where older and newer files can easily be opened in all tools. I also want new additions and expansions to be simple and I never want them to be breaking changes for any and all users. These properties reduce friction between spec editors, tools and users, in turn these drive adoption. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/139#issuecomment-1295855733 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 29 October 2022 14:38:19 UTC