W3C home > Mailing lists > Public > public-lod@w3.org > February 2010

Re: Recommendations for serving backlinks when having hash URIs?

From: Christoph LANGE <ch.lange@jacobs-university.de>
Date: Wed, 10 Feb 2010 14:17:08 +0100
To: Richard Cyganiak <richard@cyganiak.de>
Cc: "public-lod@w3.org" <public-lod@w3.org>
Message-Id: <201002101417.09862.ch.lange@jacobs-university.de>
2010-02-10 12:20 Richard Cyganiak <richard@cyganiak.de>:
> I'd recommend:
> 
> <foo27#bar1> rdfs:seeAlso <slashland/foo27/bar1> .
> 
> and then perform standard (non-redirect) content negotiation at
> <slashland/foo27/bar1>, with variants at <bar1.rdf>, <bar1.html> etc.

OK, thanks, that makes sense.

> …
> 
> at the end of the day it's always up to the clients wether they follow your
> links or not, no matter what you call your property (owl:sameAs,
> rdfs:seeAlso, my:mustFollowThisOrDie). The rdfs:seeAlso property at least is
> standard, and thus has a decent probability of being understood by a client.
> 
> In practice, some clients will understand it and some won't. Hence it might
> be prudent to include some *very* basic information directly in your
> original file at <foo27>, let's say at least an rdfs:label and maybe an
> rdf:type for the <foo27#barNNN> URIs.

Indeed – that should be feasible.

Cheers,

Christoph

-- 
Christoph Lange, Jacobs Univ. Bremen, http://kwarc.info/clange, Skype duke4701
Received on Wednesday, 10 February 2010 13:17:50 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:25 UTC