W3C home > Mailing lists > Public > public-ldp@w3.org > March 2013

Re: Section 4: LDPR/non-LDPR formal definitions

From: Richard Cyganiak <richard@cyganiak.de>
Date: Tue, 26 Mar 2013 14:04:31 +0000
Cc: Henry Story <henry.story@bblfish.net>, public-ldp@w3.org
Message-Id: <1B7A62AE-A7C9-4FC2-AAFE-CB5D98DA1BFA@cyganiak.de>
To: Kingsley Idehen <kidehen@openlinksw.com>
On 26 Mar 2013, at 13:45, Kingsley Idehen <kidehen@openlinksw.com> wrote:
> There is nothing about "text/turtle" that implies adherence or interpretation of the rules outlined in TimBL's Linked Data meme. Not a single thing

text/turtle references the Turtle spec. The Turtle spec says that Turtle serializes an RDF graph. The spec defining RDF graphs says, when explaining what the IRIs in an RDF graph mean [1]:

[[
Perhaps the most important characterisitic of IRIs in web architecture is that they can be dereferenced, and hence serve as starting points for interactions with a remote server. This specification, however, is not concerned with such interactions. It does not define an interaction model.
]]

The solution that you seek is a reference to the LDP spec in that section: “The Linked Data Platform specification [[LDP]] defines a W3C-recommended interaction model for RDF-based resources.”

This will not be possible in *this* iteration of RDF Concepts due to the way the various WG charters are staggered. It takes time to weave new specifications such as LDP into the existing fabric of specifications. The fact that it may take a few years for this sentence to appear is no excuse for harming compatibility now, in my eyes.

Best,
Richard


[1] http://www.w3.org/TR/rdf11-concepts/#referents



> , and that's the crux of the matter. TimBL outlined how to use a specific media type to produce Linked Data based on the RDF model. What he didn't do is take the additional step of triggering registration of a new media type or making an update to existing media types associated with RDF.
> 
> Why should a Web browser render HTML content delivered from a server as content-type: text/plain ?
> Why should a Linked Data browser render (produce a follow-your-nose friendly graph presentation) Turtle content delivered from a server as content-type: text/turtle ? We do it because we adopt an RDF based Linked Data community best practice, not because of any semantics in the media type specification for text/turtle or any other media type associated with RDF.
> 
> Also note, many of us have products that already cater for "text/turtle" and "application/x-turtle" in response to the original Turtle submission [1]. We are all still alive, the Semantic Web vision intact, and general Linked Data publication and consumption hasn't missed a beat :-)
> 
> Links:
> 
> 1. http://www.w3.org/TeamSubmission/turtle/#sec-mime -- Turtle media types .
> 
> 
> Kingsley
>> 
>>> Links:
>>> 
>>> 1. http://lists.w3.org/Archives/Public/public-ldp-wg/2012Oct/0132.html -- sample post from relative URIs and RDF graphs thread .
>>> 2. http://lists.w3.org/Archives/Public/public-ldp-wg/2013Mar/0095.html -- ditto  .
>>> 
>>> -- 
>>> 
>>> 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
>>> 
>>> 
>>> 
>>> 
>>> 
>> Social Web Architect
>> http://bblfish.net/
>> 
> 
> 
> -- 
> 
> 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
> 
> 
> 
> 
> 
Received on Tuesday, 26 March 2013 14:04:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:03:10 UTC