- From: Pierre Dubois via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 16:20:11 +0000
- To: public-design-tokens-log@w3.org
@delisma a JSON-LD document is a [conforming JSON document](https://www.w3.org/TR/json-ld/#abstract). > The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. The difference is an JSON-LD document are a contextualized JSON document and become more flexible because of the relation established between the JSON property name and a vocabulary term. (Linked Data) There is several existing developer libraries that already support JSON-LD - https://json-ld.org/#developers > And I'm not expecting designers to know JSON The JSON format defined/used by this design token specification is intended for being implemented by developer that know JSON as mentioned in the first bullet in [Section 4](https://design-tokens.github.io/community-group/format/#file-format): "for **developers writing software** that supports design token files" The discussion of using or not JSON-LD for design-token belong to another thread/discussion. My point was only to mention that the multilingual feature is already supported for JSON-LD documents and it is possible to upgrade JSON document into JSON-LD document. -- GitHub Notification of comment by duboisp Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/62#issuecomment-957910426 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 16:20:13 UTC