Difference between revisions of "TF-JSON"

From RDF Working Group Wiki
Jump to: navigation, search
m (Clarified confusing questions and added links)
Line 12: Line 12:
* ''[http://webr3.org/apps/specs/jsn3/ JSN3]'' by Nathan.
* ''[http://webr3.org/apps/specs/jsn3/ JSN3]'' by Nathan.
* ''[http://www.w3.org/2009/12/rdf-ws/papers/ws02 Flat triples approach to RDF graphs in JSON]'' by Dominik Tomaszuk
* ''[http://www.w3.org/2009/12/rdf-ws/papers/ws02 Flat triples approach to RDF graphs in JSON]'' by Dominik Tomaszuk
* ''[http://www.w3.org/2001/sw/wiki/index.php?title=RDF_Core_Work_Items&oldid=1990#JSON Ideas and issues from the community ]'' from RDF Core Work Items build on RDF/NextStepWorkshop
== Deliverables ==
== Deliverables ==

Revision as of 13:17, 2 March 2011

JSON RDF Task Force

The JSON RDF Task Force is primarily responsible for creating a JSON serialization of RDF.



  • JSON Serialization of RDF

Questions to Contemplate

  1. 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)?
  2. Is it necessary for developers to know RDF in order to use the simplest form of the RDF-in-JSON serialization?
  3. Should we attempt to support more than just RDF? Key-value pairs as well? Literals as subjects?
  4. Must RDF in JSON be 100% compatible with the JSON spec? Or must it only be able to be read by a JavaScript library and thus be JSON-like-but-not-compatible (and can thus deviate from the standard JSON spec)?
  5. Must all major RDF concepts be expressible via the RDF in JSON syntax?
  6. Should we go more for human-readability, or terse/compact/machine-friendly formats? What is the correct balance?
  7. Should there be a migration story for the JSON that is already used heavily on the Web? For example, in REST-based services?
  8. Should processing be a single-pass or multi-pass process? Should we support SAX-like streaming?
  9. Should there be support for disjoint graphs?
  10. Should we consider how the structure may be digitally signed?
  11. How should normalization occur?
  12. Should graph literals be supported?
  13. Should named graphs be supported?
  14. Should automatic typing be supported?
  15. Should type coercion be supported?
  16. Should there be an API defined in order to easily map RDF-in-JSON to/from language-native formats?