Best practice for permantently moved resources?

2010-08-12 Thread Kjetil Kjernsmo
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

Re: Best practice for permantently moved resources?

2010-08-12 Thread Kingsley Idehen
Kjetil Kjernsmo 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

Re: Best practice for permantently moved resources?

2010-08-12 Thread John Erickson
I realize this is a dangerous question, but...what is the cause of the change? * Has the content actually changed (revision), or simply moved (URI change)? * Must the content at the old URI go away, or can it be represented as a previous version? All of this is useful knowledge --- a form of

Re: Best practice for permantently moved resources?

2010-08-12 Thread Bernard Vatant
Hi Kjetil You might be interested by what has been done for lingvoj.org language URIs (which you have used in a project if I remember well) redirected now to lexvo.org. See http://www.lingvoj.org/ There are not many explanations of the rationale and method, but your message reminds me it's on my

Participate in the DC-Provenance task group

2010-08-12 Thread Kai Eckert
Apologies for cross-posting. Hi all, the Dublin Core Metadata Initiative (DCMI) has recently started a task group to address the issue of “metadata provenance”. The group aims at creating a shared model of the data elements required (a so-called “application profile”) to satisfactorily describe