SWO prefixes don't resolve

[cmungall]

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

• jsonld context entry for SWO is incorrect, as SWO does not use OBO PURLs OBOFoundry/OBOFoundry.github.io#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]

@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?

[allysonlister]

Apologies, I had intended to devote a couple of weeks to the various ontologies I keep an eye on this month, but that time has evaporated.

I would be happy to sort this out if you all have a preference. This issue happened before my time, when I believe it was originally developed with Manchester and the EBI together, hence the prefix issues.

What would be best? And it would be a big change; I know that despite its low activity, I'm still getting relatively regular citations for it. What is the best way to show this kind of change with a new release? The one time I did it, it was relatively tricky (allysonlister/swo#10). Will likely be simpler as we won't have the possibility for duplicate IRIs like we did the last time.

Happy to help it conform better with OBO standards; this is just an ontology that has been around for a long while, before people were really ensuring OBO prefixes from the start...