Phillip Lord wrote: > TH> Background: The "info" URI scheme is a means of grandfathering > TH> legacy namespaces onto the Web in their own right (e.g. PubMed > TH> identifiers, ADS bibcodes, etc., etc.). Many Web applications > TH> expect identifiers to be packaged as URIs (Uniform Resource > TH> Identifiers) and "info" fulfils that need. > > So do LSID's. Would you like to comment and advantages/disadvantages? Three reasons I can think of: 1. People may be reluctant to use something called "life sciences identifiers" in a non-life-sciences context (even if they could see that there isn't anything life-sciences-specific about these identifiers). 2. Squeezing legacy identifiers into LSIDs can be tricky; some life sciences databases use colons in their identifiers (GO and MGD), or separate version numbers with dots (EMBL). 3. LSIDs are a bit verbose, and once you provide an LSID you may be expected to implement the entire WS resolution stack, which some people may not consider worth the trouble.Received on Tuesday, 11 April 2006 12:37:21 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:16:32 GMT