Evidence codes can be used to specify the type of supporting evidence for a piece of knowledge. This allows inference of a 'level of support' between an entity and an annotation made to an entity.

Prefix

eco

Preferred Prefix

ECO

Version

2022-08-05

License

CC0 1.0

Links

Homepage Repository OBO OWL

Contact

Michelle Giglio   0000-0001-7628-5565   mgiglio99

Pattern for Local Unique Identifiers

Local identifiers in Evidence ontology should match this regular expression:
^\d{7}$

Example Local Unique Identifier

0007807   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from Evidence ontology should match this regular expression:
^eco:\d{7}$

Example CURIE

eco:0007807

MIRIAM Namespace Embedded in LUI

The legacy MIRIAM standard for generating CURIEs with this resource includes the namespaceEmbeddedInLUI as true. The actual part that gets prefixed before the local unique identifier regex, otherwise known as the banana, is ECO:. Therefore, you might see local unique identifiers written out as CURIEs.

Publications

• 2019 ECO, the Evidence & Conclusion Ontology: community standard for evidence information.
• 2017 The Evidence and Conclusion Ontology (ECO): Supporting GO Annotations.
• 2014 Standardized description of scientific evidence using the Evidence Ontology (ECO).
• 2004 An evidence ontology for use in pathway/genome databases.

The metaregistry provides mappings between the Bioregistry and other registries. There are 11 mappings to external registries for eco with 2 unique external prefixes.

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