Implement some of the language outlined in the following e-mail in an attempt to limit the divergence between JSON-LD and RDF data models:
PROPOSAL: Specifically, these phrases:
I agree with the intent of 3 and 4, although rather than just sticking these sentences somewhere, it needs to be made sure that the algorithms are updated accordingly; especially re 3.
With 1 and 2, I am unconvinced that having those features (blank edges and unconnected nodes) in the JSON-LD data model is actually useful, and would prefer if the algorithms would either remove them, or translate them into something that can be expressed in the RDF data model.
RESOLVED: Add the following statements to the spec: a) "Authors SHOULD NOT use unconnected nodes (a node definition that does not contain any properties) in JSON-LD documents." b) "Authors SHOULD NOT use blank nodes as edge labels." c) "JSON-LD processors MUST normalize all language tags to lowercase when processing documents via the JSON-LD Algorithms." d) "Blank node labels are scoped to the JSON-LD document."
Update Data Model and Relationship to RDF sections
This is a first attempt to specify JSON-LD's data model in all details and compare it to RDF's data model.
This addresses #157, #181, and #168.
Make sure all language-tags are normalized to lowercase
This addresses #181.
The syntax and API specification have been updated according the resolution. Unless I hear objections I will proceed and close this issue in 24 hours.