Re: Requirements update

Here are updates based on feedback. Note that I also modified the definition of "linked data graph" in the LD section to indicate that it is unordered.


 1.  A JSON-LD document must be able to express a linked data graph<http://json-ld.org/requirements/latest/#dfn-linked_data_graph>.
 2.  A JSON-LD document must be a valid JSON document.
 3.  All JSON constructs must have semantic meaning in a JSON-LD document: JSON object<http://json-ld.org/requirements/latest/#dfn-json_object>s, arrays, numbers, strings and the literal names false, and true.
 4.  A subject<http://json-ld.org/requirements/latest/#dfn-subject> is defined using a designated name/value pair of a JSON object<http://json-ld.org/requirements/latest/#dfn-json_object>.
 5.  There must be a way label a JSON object<http://json-ld.org/requirements/latest/#dfn-json_object> with an IRI.
 6.  There may be a way to reference an un-labeled JSON object that does not have a direct child relationship.
 7.  JSON object<http://json-ld.org/requirements/latest/#dfn-json_object> name/value should be used to describe property<http://json-ld.org/requirements/latest/#dfn-property>-object<http://json-ld.org/requirements/latest/#dfn-object> relationships.
 8.  A property<http://json-ld.org/requirements/latest/#dfn-property> should resolve to an absolute IRI.
 9.  Un-coerced strings represent literal object<http://json-ld.org/requirements/latest/#dfn-object>s.
 10. Coerced strings may represent IRIs.
 11. There should be a way to associate a datatype IRI with a literal JSON value.
 12. JSON boolean and numbers values represent specific datatyped literals.
 13. The literal value of JSON null is undefined.
 14. A JSON array may be used to associate multiple object<http://json-ld.org/requirements/latest/#dfn-object>s with a subject<http://json-ld.org/requirements/latest/#dfn-subject> through a common property<http://json-ld.org/requirements/latest/#dfn-property>.
 15. Without explicit syntactic support, JSON arrays must not be interpreted as defining an object ordering.
 16. A JSON-LD document should be able to express and ordered list objects.

Gregg

On Aug 9, 2011, at 9:24 AM, Gregg Kellogg wrote:

We discussed the requirements [1] on the call today. I made a couple of small changes, but I mainly wanted to get feedback from the list on the specific JSON-LD markup requirements:


 1.  A JSON-LD document must be able to express a linked data graph.
 2.  A JSON-LD document must be a valid JSON document.
 3.  All JSON constructs must have semantic meaning in a JSON-LD document: associative arrays, arrays, numbers, strings and other literal names to express semantic information.
 4.  A subject is defined using a designated name/value pair of a JSON object.
 5.  There must be a way label a JSON object with an IRI.
 6.  There may be a way to reference an un-labeled JSON object that does not have a direct child relationship.
 7.  JSON name/value should be used to describe property-object relationships.
 8.  A property should resolve to an absolute IRI.
 9.  An object is represented using JSON objects, arrays, numbers, strings and literal names resolve to nodes in a linked data graph.
 10. Un-coerced JSON strings represent literal objects.
 11. Coerced JSON strings may represent IRIs.
 12. There should be a way to associate a datatype IRI with a literal JSON value.
 13. JSON booleans, numbers and other literal values must represent specific datatyped literals.  What does null map to? There may be value in specifically saying that the meaning is undefined.
 14. A JSON array may be used to associate multiple objects with a subject through a common property.
 15. A JSON array must not be used to imply an order to the component entities.
 16. A JSON-LD document should be able to express and ordered list objects.


Gregg

[1] http://json-ld.org/requirements/latest/