- From: Booth, David (HP Software - Boston) <dbooth@hp.com>
- Date: Wed, 22 Aug 2007 15:24:16 -0400
- To: "Hilmar Lapp" <hlapp@duke.edu>, "Eric Jain" <Eric.Jain@isb-sib.ch>
- Cc: "Phillip Lord" <phillip.lord@newcastle.ac.uk>, "public-semweb-lifesci hcls" <public-semweb-lifesci@w3.org>
> From: Hilmar Lapp > [ . . . ] > In the LSID resolver spec resolution doesn't depend on the authority > domain name. Just so you're aware, the *exact* same thing can be achieved with HTTP URIs, as described here: http://dbooth.org/2006/urn2http/ For example, given the URI > http://entrez.example/2007/lsid:authority:namespace:identifier:revision an agent that is aware of this approach (which is analogous to an agent being LSID-savvy) could recognize the "http://entrez.example/2007/lsid:" prefix, replace it with "urn:lsid:" to make the following LSID > urn:lsid:authority:namespace:identifier:revision and perform LSID resolution on that. On the other hand, an agent that is *not* aware of the special "http://entrez.example/2007/lsid:" prefix (which is analogous to not being LSID-savvy) *might* be able to find useful information by dereferencing the URI via HTTP. David Booth, Ph.D. HP Software +1 617 629 8881 office | dbooth@hp.com http://www.hp.com/go/software Opinions expressed herein are those of the author and do not represent the official views of HP unless explicitly stated otherwise.
Received on Wednesday, 22 August 2007 19:25:44 UTC