W3C home > Mailing lists > Public > public-linked-json@w3.org > July 2011

Re: JSON-LD Telecon Minutes for 2011-07-04

From: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Date: Tue, 19 Jul 2011 11:00:42 -0400
Cc: public-linked-json@w3.org
Message-Id: <5FB7AC60-C933-4C9E-98AF-767FFC75133F@openlinksw.com>
To: Manu Sporny <msporny@digitalbazaar.com>

On Jul 18, 2011, at 09:00 PM, Manu Sporny wrote:

> I think we're skirting very close to letting theoretical purity
> get in the way of getting real work done. If we don't allow
> unlabeled nodes (or whatever you want to call them), then this
> is illegal in JSON-LD:
> {
>   "name": "Kingsley Idehen"
> }
> If that is an illegal statement in JSON-LD, then JSON-LD is
> certainly not a sub-set of JSON, but a newer, more limited form
> of JSON - and that is when just about every JSON developer will
> look away from JSON-LD and keep looking for something that will
> work for them in the real-world.

Manu --

It seems that your definition of "sub-set" may differ from mine.

To my mind --

- JSON is less restrictive than JSON-LD.

- JSON is more permissive than JSON-LD.

- All JSON-LD is JSON.

- Some JSON is not JSON-LD; is JSON-NLD ("Non-Linked Data").

If this were a Venn Diagram, you'd see two circles, one (JSON-LD) 
entirely contained within the other (JSON).

Further --

- JSON allows for IRI-less nodes.

- JSON-LD *SHOULD NOT* allow for IRI-less nodes.

An IRI-less node cannot be usefully referred to over time, 
nor across graphs (or JSON or other documents).  Such a node's
description cannot be re-retrieved later.

An IRI-bearing node can be usefully referred to over time and 
across graphs, and its description can be retrieved time and 
time again, potentially growing and/or being refined at each
retrieval (dereference).

Such reference (and dereferenceability) is the most important
aspect of Linked Data (LD) that sets it apart from Non-Linked 
Data (NLD)-- i.e., the LINK.

Given all that, I think this follows --

- A JSON-LD document MUST NOT include JSON-NLD.

- A JSON document MAY include JSON-NLD and JSON-LD -- i.e., 
  it MAY intermingle Linked Data and Non-Linked Data.  

- Intermingled JSON-LD and JSON-NLD is preferred over pure 
  JSON-NLD.  Pure JSON-LD is preferred over such intermingling.

Be seeing you,


A: Yes.                      http://www.guckes.net/faq/attribution.html
| Q: Are you sure?
| | A: Because it reverses the logical flow of conversation.
| | | Q: Why is top posting frowned upon?

Ted Thibodeau, Jr.           //               voice +1-781-273-0900 x32
Evangelism & Support         //        mailto:tthibodeau@openlinksw.com
                             //              http://twitter.com/TallTed
OpenLink Software, Inc.      //              http://www.openlinksw.com/
        10 Burlington Mall Road, Suite 265, Burlington MA 01803
OpenLink Blogs              http://www.openlinksw.com/weblogs/virtuoso/
    Universal Data Access and Virtual Database Technology Providers
Received on Tuesday, 19 July 2011 15:01:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:53:17 UTC