{% extends "prose.html" %} {% block title %}Related{% endblock %} {% macro render_circle(value) -%} {{ schema_status_map[value] }} {% endmacro %} {% macro registry_field_dl(cls, key) -%} {% set field = cls.__fields__[key].field_info %}
An overview on registries covering biomedical ontologies, controlled vocabularies, and databases.
A {{ schema_status_map[True] }} means the field is required. A {{ schema_status_map["present"] }} means it is part of the schema, but not required or incomplete on some entries. A {{ schema_status_map[False] }} means that it is not part of the metadata schema. For lookup services like the OLS, some fields (i.e., Example ID, Default Provider, Alternate Providers) are omitted because inclusion would be redundant.
Caveats: Several of Wikidata's fields can be accessed indirectly with alternative SPARQL queries. BioPortal's data is locked behind an API that requires a key and has rate limited access. The Crop Ontology Curation Tool does not list homepages because it is the homepage itself. Non-english language registries in the OntoPortal Alliance were not included.
Registry | Score | Name | Homepage | Description | Example | Pattern | Provider | Alternate Providers | Alternate Prefixes | License | Version | Contact |
---|---|---|---|---|---|---|---|---|---|---|---|---|
{{ registry.get_short_name() }} | {{ registry.score() }} | {{ render_circle(registry.availability.name) }} | {{ render_circle(registry.availability.homepage) }} | {{ render_circle(registry.availability.description) }} | {{ render_circle(registry.availability.example) }} | {{ render_circle(registry.availability.pattern) }} | {{ render_circle(registry.availability.provider) }} | {{ render_circle(registry.availability.alternate_providers) }} | {{ render_circle(registry.availability.synonyms) }} | {{ render_circle(registry.availability.license) }} | {{ render_circle(registry.availability.version) }} | {{ render_circle(registry.availability.contact) }} |
This section provides a systematic evaluation and comparison of the capabilities of each registry.
Registry | FAIR | Search | Provider | Resolver | Lookup |
---|---|---|---|---|---|
{{ registry.get_short_name() }} | {{ render_circle(registry.availability.fair) }} | {{ render_circle(registry.availability.search) }} | {{ render_circle(registry.provider_uri_format is not none) }} | {{ render_circle(registry.resolver_uri_format is not none and registry.resolver_type != "lookup") }} | {{ render_circle(registry.resolver_uri_format is not none and registry.resolver_type == "lookup") }} |
This section provides a systematic evaluation and comparison of the governance and standard operating procedures for each registry.
Registry | Accepts External Contributions | Public Version Control | Review Team | Scope | Status |
---|---|---|---|---|---|
{{ registry.get_short_name() }} | {{ render_circle(registry.governance.accepts_external_contributions) }} | {{ render_circle(registry.governance.public_version_control) }} | {{ registry.governance.review_team }} | {{ registry.governance.scope }} | {{ registry.governance.status }} |
The semantic web and ontology communities are bound to the use of IRIs as identifiers and therefore are very interested in the interconversion between compact identifiers (i.e., CURIEs) and IRIs. While the Bioregistry provides many tools for one way conversion from CURIEs to IRIs, there are several related packages that help parse CURIEs from IRIs: