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

Re: JSON-LD requirements

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 04 Jul 2011 01:33:43 +0100
Message-ID: <4E110A67.4090001@openlinksw.com>
To: public-linked-json@w3.org
On 7/3/11 7:08 PM, Gregg Kellogg wrote:
> Well, I was really attempting to do that. The term "RDF" doesn't appear anywhere in the document, and I was really trying to stick with (what I believe to be) a standard definition of "Linked Data" from Wikipedia andhttp://linkeddata.org. If we have a basic disagreement about what the term "Linked Data" means, then we can hardly agree what "Linked Data in JSON" should be.
Gregg,

Wikipedia doesn't describe what Linked Data is. It attempts to describe 
TimBL's meme [1].

Linked Data != Best Practice. TimBL's meme was about leveraging AWWW for 
Web Scale Linked Data, a best practice.

Using hyperlinks as mechanism for "whole data representation" via 
EAV/SPO graphs is what Linked Data is about.

I know from your background @ NeXT (and your data representation 
transformation demos) that to you are very familiar with the concept of 
Linked Data structures pre. ubiquitous WWW. Thus, think more in terms of 
what your already know about Linked Data structures and the fact that 
today we can now craft them using EAV/SPO patterns that leverage power 
inherent in the URI abstraction.

JSON-LD could be a spec for using JSON as simple mechanism for "whole 
data representation" via Linked Data graphs.

A Linked Data definition will always be confusing if it doesn't find a 
way to clearly articulate the importance of the following:

1. Data Object Names
2. Data Object Representation
3. Data Object Representation via EAV/SPO triples (3-tuples)
4. Data Object Representation Address
5. Data Object Names resolving to Referent Representation via 
Representation Address.

This just boils down to de-reference (indirection) and address-of 
operations via hyperlinks with regards to graphs that deliver "whole 
data representation".

If all fails, just lookup: http://graph.facebook.com/kidehen, then ask 
the obvious question: what's wrong with what that resolves to re. Linked 
Data? As far as I know, it's simply lacking re. items 1-5 i.e., property 
names are literals and so are their values. The object in question is 
also devoid of introspection since it doesn't have a resolvable name.

JSON-LD can only be a really lightweight spec if it seeks to serve a 
genuine need. Otherwise, I ask the question one more time: what's wrong 
with RDF/JSON from Talis?


Links:

1. http://www.w3.org/DesignIssues/LinkedData.html -- Linked Data meme .

-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
Received on Monday, 4 July 2011 00:34:20 UTC

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