- From: David Elisma via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 15:48:49 +0000
- To: public-design-tokens-log@w3.org
@duboisp [Section 4](https://design-tokens.github.io/community-group/format/#file-format) of the draft explain why the community group is choosing JSON as the standard file format" > - Broad support in many programming languages’ standard libraries. This is expected to lower barriers to entry for developers writing software that supports design token files. > - Current popularity and widespread use. This is expected to lower the learning curve as many people will already be familiar with JSON. > - Being text-based (rather than binary) allows hand-editing design token files without needing specialized software other than a basic text editor. It also means the files are somewhat human-readable. Do you think that JSON-LD has a broad support with current tools and librairies? And I'm not expecting designers to know JSON, yet again JSON-LD, but the learning curve is much lower for the non-developer audience. -- GitHub Notification of comment by delisma Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/62#issuecomment-957867422 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 November 2021 15:48:51 UTC