Welcome to the Life Sciences Identifiers (LSID)

Life Science Identifiers (LSIDs) are persistent, location-independent, resource identifiers for uniquely naming biologically significant resources including species names, concepts, occurrences, genes or proteins, or data objects that encode information about them. To put it simply, LSIDs are a way to identify and locate pieces of biological information on the web.

The LSID concept introduces a straightforward approach to naming and identifying data resources stored in multiple, distributed data stores in a manner that overcomes the limitations of naming schemes in use today. Almost every public, internal, or department-level data store today has its own way of naming individual data resources, making integration between different data sources a tedious, never-ending chore for informatics developers and researchers.

By defining a simple, common way to identify and access biologically significant data, whether that data is stored in files, relational databases, in applications, or in internal or public data sources, LSID provides a naming standard underpinning for wide-area science and interoperability.

The Life Sciences Identifier is an Object Management Group (OMG) Final Adopted Specification developed by the Life Sciences Research (LSR).

What does an LSID look like?

LSIDs are Universal Resource Names (URN) that conform to the following syntax:

LSID Syntax Diagram

Every LSID consists of up to five parts, each separated by a colon:

  1. the Network Identifier (NID), i.e., the "urn:lsid:" label;
  2. the Authority Identification, usually the root DNS name of the issuing authority;
  3. the Namespace Identification chosen by the issuing authority;
  4. the Object Identification unique in that namespace; and
  5. an optional Revision Id to represent versioning information.

 

Here are a few examples of LSIDs:

These LSIDs name and refer to one unchanging data object each. Unlike the familiar URLs of the World-Wide-Web, LSIDs are location independent. This means that a program or a user can be certain, through the use of LSIDs, that what they are dealing with is exactly the same data because an LSID guarantees to persistently and uniquely identify a data object.