SWO prefixes don't resolve - Githubissues

biopragmatics / bioregistry

📮 An integrative registry of biological databases, ontologies, and nomenclatures.

https://bioregistry.io

MIT License

115 stars 49 forks source link

SWO prefixes don't resolve #1168

Open cmungall opened 1 month ago

cmungall commented 1 month ago

SWO is registed with OBO so you might think it has OBO prefixes, but this isn't the case:

https://github.com/OBOFoundry/OBOFoundry.github.io/issues/2307

Example CURIE on https://bioregistry.io/registry/swo => https://bioregistry.io/reference/swo:/0000144 => the RDF entry => http://purl.obolibrary.org/obo/SWO_0000144 => redirects to https://www.ebi.ac.uk/ols4/ontologies/swo/entities/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FSWO_0000144

which hangs with a spinning circle of doom

In fact it's necessary to create multiple sub-prefixes for SWO since the URIs follow unusual practice.

This is the prefixmap I am using for OAK/semantic-sql

https://github.com/INCATools/semantic-sql/pull/91/files#diff-0cfe34663a838a843313de1ef13ccd6ab9e0aac209d6313a26dfcc88c24d38fd

Happy to change if there is consensus, cc @allysonlister

bgyori commented 4 weeks ago

@cmungall just to clarify, do you think we should touch the URI pattern in bioregistry (i.e., http://purl.obolibrary.org/obo/SWO_$1) at all, or would this be updated in the resolver for purl.obolibrary.org URIs?