- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Fri, 17 Feb 2012 16:08:45 -0500
- To: public-lod@w3.org
- Message-ID: <4F3EC1DD.6080402@openlinksw.com>
On 2/17/12 2:18 PM, David Booth wrote: > On Fri, 2012-02-17 at 18:48 +0000, Hugh Glaser wrote: > [ . . . ] >> What happens if I have http://purl.org/dbpedia/Tokyo, which is set to >> go to http://dbpedia.org/resource/Tokyo? >> I have (a), (b) and (c) as before. >> Now if dbpedia.org goes Phut!, we are in exactly the same situation - >> (b) gets lost. > No, the idea is that the administrator for http://purl.org/dbpedia/ > updates the redirect, to point to whatever new site is hosting the > dbpedia data, so the http://purl.org/dbpedia/Tokyo still works. > > > David, But any admin that oversees a DNS server can do the same thing. What's special about purl in this context? Remember, DBpedia URIs are live, so the most important issues are: 1. domain ownership 2. dns admin re. ip address mapping 3. reconstitution of the linked data sets to with the DBpedia URIs resolve. -- 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
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Friday, 17 February 2012 21:09:11 UTC