The Arabidopsis Information Resource (TAIR) maintains a database of genetic and molecular biology data for the model higher plant Arabidopsis thaliana. This provides protein information for a given gene model and provides links to other sources such as UniProtKB and GenPept

Prefix

tair.protein

Keywords

protein

Links

Homepage

Contact

Aisling Doyle   0000-0003-3871-858X

Pattern for Local Unique Identifiers

Local identifiers in TAIR Protein should match this regular expression:
^\d{10}$

Example Local Unique Identifier

1009107926   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from TAIR Protein should match this regular expression:
^tair\.protein:\d{10}$

Example CURIE

tair.protein:1009107926

Namespace Embedded in LUI

This resource has been annotated by the Semantic Farm as having a potential namespace embedded in LUI. This means that you may see local unique identifiers that include a redundant prefix and delimiter (also known as a banana) and therefore look like a CURIE. For , the banana looks like AASequence:. Therefore, you may see local unique identifiers for this resource that look like AASequence:1009107926 (instead of the canonical form 1009107926) and CURIEs for this resource that look like tair.protein:AASequence:1009107926 (instead of the canonical form tair.protein:1009107926). The Semantic Farm will automatically strip off the banana when standardizing local unique identifiers and CURIEs.

Publications

2002 TAIR: a resource for integrated Arabidopsis data

Contributors

• contributor Benjamin M. Gyori   0000-0001-9439-5346   bgyori

The metaregistry provides mappings between the Semantic Farm and other registries. There are 4 mappings to external registries for this resource with 1 unique external prefixes.

A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).

The local unique identifier 1009107926 is used to demonstrate the providers available for TAIR Protein. Some providers may use a different example, which is displayed in the table below. A guide for curating additional providers can be found here.

Additional providers curated in the Semantic Farm are listed here. These are typically inherited from Identifiers.org or Prefix Commons, and need extra curation.