W3C home > Mailing lists > Public > public-lod@w3.org > December 2012

Re: Linked Data Book in Early Access Release

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Thu, 06 Dec 2012 13:39:19 -0500
Message-ID: <50C0E657.8010302@openlinksw.com>
To: public-lod@w3.org
On 12/6/12 11:51 AM, ☮ elf Pavlik ☮ wrote:
> still it looks like havinghttp://manning.com/dwood  i can't discoverhttp://manning.com/dwood/LinkedData.ttl  following a common convention? what options we could have for that?
> * content type negotiation and redirect -  303?
> * link relation in head of document?

That's because there is some ambiguity in the data, at this time. 
Basically, one than one entity has been denoted using the same URI. 
Possible solution:

<http://manning.com/dwood#this> denotes 'David Wood'.
<http://manning.com/dwood> denotes an HTML document.
<http://manning.com/dwood/LinkedData.ttl> denotes a Turtle based RDF 
document.

This Link shows the problem: 
http://idi.fundacionctic.org/vapour?uri=http%3A%2F%2Fmanning.com%2Fdwood&defaultResponse=dontmind&userAgent=vapour.sourceforge.net

The issue of 303 is a secondary mechanical detail. The important thing 
is to denote all the entities -- in an entity relationship graph (RDF or 
otherwise) -- unambiguously. The mechanics of 303 only comes into play 
when an entity that's not of type 'Web or Internet Document' ends up 
being denoted using a hashless HTTP URI.

-- 

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 Thursday, 6 December 2012 18:39:44 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:30:02 UTC