- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Dec 2022 10:04:25 +0000
- To: public-design-tokens-log@w3.org
> we should lean more toward the CSS model than the SVG model. Why was JSON picked in that case? It isn't well known for it's easy reading and writing by hand. Was this purely because other formats for design tokens use JSON? For me personally it feels weird to start a new format and immediately have these compromises when the benefits only exist in the short term. --------- > When Jina, Garth, Danny and I started this group, we discussed what our principles should be from a technical and community perspective. At the time we were convinced that we should lean more toward the CSS model than the SVG model. I think it's still relevant today to meet people where they are, but I expect things might evolve once we have much better tooling available to everyone. > We also understand the specification has to lead to token files that are parsable and portable. If part of the specification is vague, it can introduce errors in portability, and we will take steps to update the spec when those areas are identified. Unfortunately there’s not a decision tree or a concrete mechanism we can use to apply this principle to each decision, since context informs us on a case-by-case basis. To help illustrate this principle in practice here’s an example where we feel this principle has informed our decision making process: Not only ambiguity in the specification as it exists today. More importantly are all the future extensions to the format. A format that is explicit about everything and uses structured data without requiring any additional parsing of micro syntax will be easier to extend. Inversely it needs to explored which extension points become impossible by the choices made in favor of easy editing by hand. Relevant to this : https://github.com/design-tokens/community-group/issues/162 -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/149#issuecomment-1345205916 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 10 December 2022 10:04:26 UTC