- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Sat, 08 Jan 2022 23:51:41 +0000
- To: public-design-tokens-log@w3.org
> Therefore, if we allow both YAML and JSON that would mean that every tool that supports our spec would need to be able to read both formats. I can respect that. And I can also see how focusing on a single, unified format for now is the best way forward. As for OpenAPI supporting both, I’m actually not sure when it happened, but it is interesting that it has developed alongside [JSON Schema](https://json-schema.org/) and for the most part does tend to be JSON-focused. I can respect not adding distractions now to the current priority of figuring out the general schema and token types, so again, JSON seems like a solid choice! Perhaps in the far future YAML could be considered if, as you said, the tooling has already stabilized and the community at large agrees. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/92#issuecomment-1008185697 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 23:51:43 UTC