- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Fri, 19 Oct 2012 13:09:21 -0400
- To: public-rdf-wg@w3.org
- Message-ID: <50818941.1050800@openlinksw.com>
On 10/19/12 10:45 AM, Peter Patel-Schneider wrote: > I have absolutely no problem with other documents about JSON-LD that > don't mention RDF at all. However, if the controlling document on > JSON-LD produced by the RDF WG isn't about RDF in a very strong way, > then there is something very wrong. > > peter As per my last comment, we need to get the definitions of the following straight: 1. EAV/CR -- Entity Attribute Value plus Classes & Relationships (relationship semantics are implicit and thereby susceptible to ambiguity) 2. RDF -- EAV/CR with the addition of explicit entity relationship semantics + URIs as entity denotation mechanism 3. Linked Data -- RDF or EAV/CR + explicit entity relationship semantics + de-referencable URIs as entity denotation mechanism 4. JSON-LD -- a JSON based data representation and serialization format for Linked Data. We have to be brave enough to loosely couple RDF and Linked Data. There's nothing to lose and everything to gain :-) Links: 1. http://lists.w3.org/Archives/Public/public-rdf-wg/2012Sep/0003.html -- apropos my last post and view point reiterated above . -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Friday, 19 October 2012 17:09:49 UTC