Re: [BioPAX-discuss] LSID Best practices...

EJ>I think the DOI system got this right; they specify that an identifier 
such
EJ>as doi:10.1000/182 can be resolved using http://xyz/10.1000/182, where 
xyz
EJ>is your favorite resolver server.

EJ>Any chance to see this being standardized, as a light weight 
alternative to
EJ>the web service resolution mechanism?

Perhaps we could, if we could decide what was returned. The data or 
metadata (and who's?). Perhaps the answer is to create some standard verbs 
like:

http://xyz/data/urn:lsid...  http://xyz/metadata/urn:lsid...  and 
http://xyz/3rdpartymetadata/urn:lsid...

I am not sure that it would be a good idea to remove the "urn:lsid" 
prefix, otherwise how would my software know to be able to use my favorite 
resolver instead of someone else's. This is important, otherwise we are 
just back to URL's and the problems with them.

Kindest regards, Sean

--
Sean Martin
IBM Corp.






Eric Jain <Eric.Jain@isb-sib.ch> 
Sent by: public-semweb-lifesci-request@w3.org
04/07/2005 11:42 AM

To
Eric.Neumann@sanofi-aventis.com
cc
public-semweb-lifesci@w3.org
Subject
Re: [BioPAX-discuss]  LSID Best practices...







Eric.Neumann@sanofi-aventis.com wrote:
> http://lsid.biopathways.org/resolver/data/urn:lsid:
> ncbi.nlm.nih.gov.lsid.biopathways.org:genbank_gi:5851672

Really useful! However, someone else may use

http://xyz/resolve?lsid=
urn:lsid:ncbi.nlm.nih.gov.lsid.biopathways.org:genbank_gi:5851672

or

http://xyz/
ncbi.nlm.nih.gov.lsid.biopathways.org/genbank_gi/5851672

or who knows what else...

I think the DOI system got this right; they specify that an identifier 
such
as doi:10.1000/182 can be resolved using http://xyz/10.1000/182, where xyz
is your favorite resolver server.

Any chance to see this being standardized, as a light weight alternative 
to
the web service resolution mechanism?