one of the purposes of https://github.com/prefixcommons/biocontext/ is to provide a mechanism to map standardized prefixes to URIs and back, acting as an interoperation layer between semweb world of URIs and bio world of CURIEs/prefixed IDs.
We could explore retiring biocontext in place of bioregistry if we can get a way to indicate the provider preferred way of indicating a semweb/OWL URI.
For example, for any OBO ontology, the OBO PURL is canonical (OK, there are wrinkles when it comes to NCIT and FMA)
As far as I can tell there isn't really a direct way of getting this in bioregistry:
the OBO PURL is there under prefixcommons, which I believe is coming from https://github.com/prefixcommons/biocontext/ which is itself an aggregator, and the real source for this is the OBO registry
one of the purposes of https://github.com/prefixcommons/biocontext/ is to provide a mechanism to map standardized prefixes to URIs and back, acting as an interoperation layer between semweb world of URIs and bio world of CURIEs/prefixed IDs.
We could explore retiring biocontext in place of bioregistry if we can get a way to indicate the provider preferred way of indicating a semweb/OWL URI.
For example, for any OBO ontology, the OBO PURL is canonical (OK, there are wrinkles when it comes to NCIT and FMA)
As far as I can tell there isn't really a direct way of getting this in bioregistry:
the OBO PURL is there under
prefixcommons
, which I believe is coming from https://github.com/prefixcommons/biocontext/ which is itself an aggregator, and the real source for this is the OBO registryhttp://purl.obolibrary.org/meta/obo_prefixes.ttl
Maybe this goes against the bioregistry philosophy of being an aggregation of others' json blobs, but I think this could be quite useful.