On Thursday 12. August 2010 13:35:28 John Erickson wrote:
I realize this is a dangerous question, but...what is the cause of the
change?
Oh, it is good and interesting question, but one that I cannot answer, and
my solution has to be so generic it isn't relevant.
The problem is that I cannot
On Thursday 12. August 2010 13:42:52 Leigh Dodds wrote:
I've been wondering about this too. I've always leaned towards
treating a 301 as an owl:sameAs statement [1].
Interesting!
This could be encoded
in the data directly instead of your ex:permanently_moved_to. But I'd
also argue that
On Thursday 12. August 2010 14:02:45 Bernard Vatant wrote:
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)
Yeah, that's now in production at http://smil.uio.no/ (uhm, down now...
Well, I left that company some
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
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
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
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