Skip to content

Limit divergence between JSON-LD and RDF data models #181

Closed
msporny opened this Issue Nov 1, 2012 · 7 comments

5 participants

@msporny
JSON-LD Public Repositories member
msporny commented Nov 1, 2012

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:

http://lists.w3.org/Archives/Public/public-rdf-wg/2012Oct/0240.html

PROPOSAL: Specifically, these phrases:

  1. "Unconnected nodes (IRIs, blank nodes or values) are supported." We should add: "Authors SHOULD NOT use unconnected nodes (a node definition that does not contain any properties) in JSON-LD documents."
  2. "Edge labels may be blank nodes." We should add: "Authors SHOULD NOT use blank nodes as edge labels."
  3. "Language tags are not normalized to lower case." We should add: "JSON-LD processors MUST normalize all language tags to lowercase when processing documents via the JSON-LD Algorithms."
  4. "Scope of blank node labels". We should add: "Blank node labels are scoped to the JSON-LD document."

//cc @prototypo

@gkellogg
JSON-LD Public Repositories member
gkellogg commented Nov 1, 2012

+1

@lanthaler
JSON-LD Public Repositories member

+1

@msporny
JSON-LD Public Repositories member
msporny commented Nov 7, 2012

+1

@niklasl
JSON-LD Public Repositories member
niklasl commented Nov 8, 2012

+1

@cygri
cygri commented Nov 13, 2012

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.

@lanthaler
JSON-LD Public Repositories member

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."

@lanthaler lanthaler added a commit that referenced this issue Dec 3, 2012
@lanthaler lanthaler 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.
714c507
@lanthaler lanthaler added a commit that referenced this issue Dec 3, 2012
@lanthaler lanthaler Make sure all language-tags are normalized to lowercase
This addresses #181.
666308a
@lanthaler
JSON-LD Public Repositories member

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.

@lanthaler lanthaler closed this Dec 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.