W3C home > Mailing lists > Public > public-apa@w3.org > September 2019

JSON-LD horizontal review request

From: Benjamin Young <byoung@bigbluehat.com>
Date: Thu, 5 Sep 2019 20:27:24 +0000
To: "public-apa@w3.org" <public-apa@w3.org>
Message-ID: <DM5PR06MB34013240EE28AED4183FAAACB2BB0@DM5PR06MB3401.namprd06.prod.outlook.com>
Hi all,

The JSON-LD WG is nearing publication of three specifications:

JSON-LD syntax is a data encoding format based on JSON. The API provides a means to convert JSON-LD documents into other forms of valid JSON-LD for further processing. Framing is used to reshape existing JSON-LD into a specific JSON tree structure.

JSON-LD does not itself dictate what is encoded in any JSON-LD document, nor how that content is used, displayed, or consumed. The API simply enables usage of the encoded data. Consequently, most of the FAST checklist questions didn't seem to apply directly to usage of the JSON-LD syntax, API, or framing specifications.

However, we did want to provide answers to the two API specific questions--which match the above summary:

If technology defines an API...
Q: If the API can be used for structured content, it provides features to represent all aspects of the content including hidden accessibility features.

A: The API is used for structuring data, but the encoded data itself is where the responsibility for accessibility features lies.

Q: If the API relies on user agents to generate a user interface, the specification provides guidance about accessibility requirements needed to enable full interaction with the API.

A: The API is not intended to generate a user interface directly.

Please let me know if you have other questions around JSON-LD and this summary from the checklist.

Benjamin Young
Co-Chair, JSON-LD WG



Received on Thursday, 5 September 2019 20:27:50 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:05 UTC