- From: Ryan Johnson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Nov 2022 23:18:22 +0000
- To: public-design-tokens-log@w3.org
The whole point of using JSON as the chosen format is to ensure cross-platform interoperability using a well-defined data structure. By adding this type of syntax to the spec, we're adding implied behavior _in addition to_ the data structure. Doing so ventures into the realm of defining a domain-specific language (DSL), which reduces downstream interoperability, because translation tools would need to add an extra layer of complexity in order to parse the DSL into the data structure before they can even begin translating the data. Conversely, if you know you can perform the "extends" behavior using another language, why not use that language to generate your fully-defined `tokens.json`? If the `tokens.json` is already in a fully-defined state, there's no need for translation tools to parse a DSL to begin translating the data. -- GitHub Notification of comment by CITguy Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/116#issuecomment-1319335407 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 November 2022 23:18:23 UTC