ProteomicsDB is an effort dedicated to expedite the identification of the human proteome and its use across the scientific community. This human proteome data is assembled primarily using information from liquid chromatography tandem-mass-spectrometry (LC-MS/MS) experiments involving human tissues, cell lines and body fluids. Information is accessible for individual proteins, or on the basis of protein coverage on the encoding chromosome, and for peptide components of a protein. This collection provides access to the peptides identified for a given protein.


The fact that this has .peptide as a subspace is a bit of a misnomer. Its original registration with MIRIAM uses a subview over the protein to point to peptides, but the identifiers in this semantic space seem to be about proteins.

Missing Contact
Pattern for Local Unique Identifiers

Local identifiers in ProteomicsDB Peptide should match this regular expression:

Example Local Unique Identifier
53504   Resolve
Pattern for CURIES

Compact URIs (CURIEs) constructed from ProteomicsDB Peptide should match this regular expression:

Example CURIE
Metaregistry ProteomicsDB Peptide

The metaregistry provides mappings between the Bioregistry and other registries. There are 3 mappings to external registries for proteomicsdb.peptide with 1 unique external prefixes.

Registry Name Registry Metaprefix External Prefix Curate
BioContext biocontext PROTEOMICSDB.PEPTIDE logo miriam proteomicsdb.peptide
Name-to-Thing Name-to-Thing logo n2t proteomicsdb.peptide

Providers are various services that resolve CURIEs to URLs. The example CURIE proteomicsdb.peptide:53504 is used to demonstrate the provides available for proteomicsdb.peptide. Generation of OLS and BioPortal URLs requires additional programmatic logic beyond string formatting.

Name Metaprefix URI
ProteomicsDB Peptide proteomicsdb.peptide
Bioregistry bioregistry miriam
Name-to-Thing n2t