Hi Kjetil, I've been wondering about this too. I've always leaned towards treating a 301 as an owl:sameAs statement [1]. This could be encoded in the data directly instead of your ex:permanently_moved_to. But I'd also argue that based on the semantics of HTTP a client could reasonably infer that too, others disagree [2] (see cygri's comment). Personally I think the semantics are clear and there's nothing broken in a client assuming that.
Regardless, I think I'd advocate using owl:sameAs to indicate the change. This still provides a hook to merge data using the older URIs. Cheers, L. [1]. http://www.ldodds.com/blog/2007/03/the-semantics-of-301-moved-permanently/ [2]. http://www.semanticoverflow.com/questions/1270/do-semantic-web-agents-handle-additional-redirects-on-uris-for-non-information-re On 12 August 2010 10:12, Kjetil Kjernsmo <[email protected]> wrote: > Hi all! > > Cool URIs don't change, but cool content does, so the problem surfaces that I > need to permanently redirect now and then. I discussed this problem in a > meetup yesterday, and it turns out that people have found dbpedia problematic > to use because it is too much of a moving target, when a URI changes because > the underlying concepts change, there's a need for more 301s. > > The problem is then that I need to record the relation between the old and the > new URI somehow. As of now, it seems that the easiest way to do this would be > to do something like: > > <http://example.org/old> ex:permanently_moved_to <http://example.org/new> > > and if the former is dereferenced, the server will 301 redirect to the latter. > Has anyone done something like that, or have other useful experiences relevant > to this problem? > > Cheers, > > Kjetil > > > Please consider the environment before printing this email. > > Find out more about Talis at http://www.talis.com/ > shared innovation™ > > Any views or personal opinions expressed within this email may not be those > of Talis Information Ltd or its employees. The content of this email message > and any files that may be attached are confidential, and for the usage of the > intended recipient only. If you are not the intended recipient, then please > return this message to the sender and delete it. Any use of this e-mail by an > unauthorised recipient is prohibited. > > Talis Information Ltd is a member of the Talis Group of companies and is > registered in England No 3638278 with its registered office at Knights Court, > Solihull Parkway, Birmingham Business Park, B37 7YB. > -- Leigh Dodds Programme Manager, Talis Platform Talis [email protected] http://www.talis.com
