From RDF Working Group Wiki
Revision as of 13:55, 23 February 2011 by Mbrunati
JSON RDF Task Force
The JSON RDF Task Force is primarily responsible for creating a JSON serialization of RDF.
- RDF JSON, by Talis.
- JSON-LD, by Manu Sporny.
- JRON by Sandro Hawke.
- JSON serialization in the Linked Data API.
- SPARQL Query Results in JSON by DAWG.
- JSN3 by Nathan.
- JSON Serialization of RDF
Questions to Contemplate
- Are we to create a lightweight JSON based RDF interchange format optimized for machines and speed, or an easy to work with JSON view of RDF optimized for humans (developers)?
- Is it necessary for developers to know RDF in order to use the simplest form of the RDF-in-JSON serialization?
- Should we attempt to support more than just RDF? Key-value pairs as well? Literals as subjects?
- Must RDF-in-JSON be 100% compatible with JSON (aka: JSON-P)? Or must it only be able to be read by JSON and can thus deviate from the standard JSON spec?
- Must all major RDF concepts must be expressible via the RDF-in-JSON syntax?
- Should we go more for human-readability, or terse/compact/machine-friendly formats?
- Should there be a migration story for the JSON that is already used heavily on the Web? For example, in REST-based services?
- Should processing be a single-pass or multi-pass process? Should we support SAX-like streaming?
- Should there be support for disjoint graphs?
- Should we consider how the structure may be digitally signed?
- How should normalization occur?
- Should graph literals be supported?
- Should named graphs be supported?
- Should automatic typing be supported?
- Should type coercion be supported?
- Should there be an API defined in order to easily map RDF-in-JSON to/from language-native formats?