- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Sat, 08 Jan 2022 00:36:36 +0000
- To: public-design-tokens-log@w3.org
No need to apologise! We're keen for folks to question and challenge things in the spec draft. We considered things like YAML and also extensions to JSON like JSON5 but eventually settled on plain JSON as we felt that was the most widely and consistently supported across different programming languages. As for supporting YAML _and_ JSON, my main concern would be interoperability. The goal of our spec is define a file format that allows people to easily and reliably exchange design token data between various tools. Any tool that supports the spec should be able to read or write files that any other tool that also supports the spec can handle. Therefore, if we allow both YAML and JSON that would mean that _every_ tools that supports our spec would need to be able to read both formats. My gut feel is that the extra work and testing that each tool vendor would have is likely to be a bigger barrier to adoption than JSON (arguably) being a bit less friendly to write than YAML. -- GitHub Notification of comment by c1rrus Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/92#issuecomment-1007842511 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 8 January 2022 00:36:37 UTC