- From: Eric Jain <Eric.Jain@isb-sib.ch>
- Date: Thu, 09 Aug 2007 13:58:17 +0200
- To: wangxiao@musc.edu
- CC: Bijan Parsia <bparsia@cs.man.ac.uk>, ogbujic@ccf.org, public-semweb-lifesci hcls <public-semweb-lifesci@w3.org>
Xiaoshu Wang wrote: > [...] why not designate a top domain name > like "tmp" to signal this. For instance, use > "http://example.com.tmp/doc" as the temporary URI for the eventual > resource of "http://example.com/doc". There are in fact already several reserved TLDs such as .test and .invalid, see http://www.faqs.org/rfcs/rfc2606.html. But I'm not sure this is needed. In a closed world, I guess something like "urn:my:1345" is fine, but in an open world you want to avoid collisions, and to ensure that you either need to use some kind of GUID (not always practical), or you need some kind of registry. Unfortunately setting up a registry and getting it accepted seems to be rather difficult business. Fortunately there is an existing registry that is working fine and has been accepted globally (quite an achievement). Making use of that system for any identifier scheme seems like a good idea -- unless you happen to have massive money and political power backing you! Both PURLs and LSIDs make use of domain names; once you have domain names involved, my feeling is that you might as well stick the http: in front... Regarding the problem of having your website swamped with requests from crawlers that all result in 404: Just use a subdomain in your identifiers, for example we use purl.uniprot.org, so if we hadn't set up our nameserver to handle this subdomain, there would be no 404 errors filling up our logs.
Received on Thursday, 9 August 2007 11:58:38 UTC