LSID

Life Science Identifiers [Clark T., Martin S., Liefeld T. Briefings in Bioinformatics 5.1:59-70, March 1, 2004.] [ [http://xml.coverpages.org/lsid.html Technology Report on OMG Life Sciences Identifiers Specification (LSID)] ] are a way to name and locate pieces of information on the web. Essentially, an LSID is a unique identifier for some data, and the LSID protocol specifies a standard way to locate the data (as well as a standard way of describing that data). They are a little like DOIs used by many publishers. There has been a lot of interest in LSIDs in both the bioinformatics and the biodiversity communities. However, more recently, as understanding has increased of how HTTP URIs can perform a similar naming task, [http://dbooth.org/2006/urn2http/#lsid Booth, David: "Converting New URI Schemes or URN Sub-Schemes to HTTP"] ] [ [http://lists.w3.org/Archives/Public/public-semweb-lifesci/2006Jul/0206.html Thompson, Henry S.: "A precedent suggesting a compromise for the SWHCLS IG Best Practices", publicly archived email message] ] the use of LSIDs as identifiers has been criticized [ [http://lists.w3.org/Archives/Public/www-tag/2006Jul/0041 Mendelsohn, Noah: "My conversation with Sean Martin about LSIDs", public email to W3C TAG mailing list 25-Jul-2006] ] as violating the [http://www.w3.org/TR/webarch/#pr-reuse-uri-schemes Web Architecture] good practice of reusing existing URI schemes [ [http://www.w3.org/TR/webarch/#pr-reuse-uri-schemes W3C Architecture of the World Wide Web] ] .

The World Wide Web provides a globally distributed communication framework that is essential for almost all scientific collaboration, including bioinformatics. However, several limits and inadequacies were thought to exist, one of which was the inability to programmatically identify locally named objects that may be widely distributed over the network. This perceived shortcoming would have limited our ability to integrate multiple knowledgebases, each of which gives partial information of a shared domain, as is commonly seen in bioinformatics. The Life Science Identifier (LSID) and LSID Resolution System (LSRS) were designed to provide simple and elegant solutions to this problem, consistent with next-generation semantic web and semantic grid, based on the extension of existing internet technologies. However, it has more recently been pointed out that these perceived shortcomings are not intrinsic to HTTP URIs, and much of the functionality that LSIDs provide can be obtained using properly crafted HTTP URIs.this text is ignored but apparently required]

An LSID is represented as a Uniform Resource Name (URN) with the following format.
* URN:LSID::: [:]

ee also

* Resource Description Framework
* MicroArray and Gene Expression

Notes

External links

* [http://www.omg.org/cgi-bin/doc?dtc/04-10-08 Life Sciences Identifiers: OMG Final Available Specification]
* [http://lsids.sourceforge.net/ LSID Resolution Project]
* [http://www-128.ibm.com/developerworks/opensource/library/os-lsidbp/ LSID best practices] from IBM
* [http://www.morphster.org/lsid.html LSID Assigning and Resolution Authority] from The University of Texas at Austin
* [http://lsid.biopathways.org/ Life Science Identifier] from BioPathways Consortium
* [http://linnaeus.zoology.gla.ac.uk/~rpage/lsid/tester/ LSID Tester]