{% extends "prose.html" %} {% block title %}Related{% endblock %} {% macro render_circle(value) -%} {{ schema_status_map[value] }} {% endmacro %} {% block styles %} {{ super() }} {% endblock %} {% block scripts %} {{ super() }} {% endblock %} {% block content %}

Comparison of Registry Schemata

An overview on registries covering biomedical ontologies, controlled vocabularies, and databases.

A 🟢 means the field is required. A 🟡 means it is part of the schema, but not required or incomplete on some entries. A 🔴 means that it is not part of the metadata schema. The FAIR column denotes that a structured dump of the data is easily findable, accessible, and in a structured format in bulk. For lookup services, some fields (i.e., Example ID, Default Provider, Alternate Providers) are omitted because inclusion would be redundant. The search column means there is a URL into which a search query can be formatted to show a list of results. The provider column means there is a URL into which a prefix can be formatted to show a dedicated page for its metadata.

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.

{% for registry in registries %} {% endfor %}
Registry Score Name Homepage Description Example Pattern Provider Alternate Providers Alternate Prefixes License Version Contact FAIR Search Provider Resolver Lookup
{{ registry.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) }} {{ 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 == "redirect") }} {{ render_circle(registry.resolver_uri_format is not none and registry.resolver_type == "lookup") }}

Conversion between CURIEs and IRIs

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:

{% endblock %}