Closed vmedea closed 1 year ago
I suspect this is an owl2obo pecularity due to odd URL structures (specifically possible ambiguity of multiunderscores)
In fact at the OWL level they are are all URLs
✗ curl -L -s http://purl.obolibrary.org/obo/NCBITaxon_2 | grep superking
<ns3:has_rank rdf:resource="http://purl.obolibrary.org/obo/NCBITaxon_superkingdom"/>
<!-- http://purl.obolibrary.org/obo/NCBITaxon_superkingdom -->
<Class rdf:about="http://purl.obolibrary.org/obo/NCBITaxon_superkingdom">
<rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string">superkingdom</rdfs:label>
While this should be fixed independently, I don't think it's a good idea to inject rank into the NCBITaxon namespace. These URLs resolve in neither OBO nor in NCBI itself.
@balhoff is https://obofoundry.org/ontology/taxrank still active?
Should we use it?
in order not to break existing code we could use a second assertion
http://purl.obolibrary.org/obo/TAXRANK_1000000
to taxrank
or maybe just use wikidata URIs?
I haven't had a chance to look into this, but I thought it was just a new rank that we hadn't seen before and should add to this list: https://github.com/obophenotype/ncbitaxon/blob/master/src/ncbitaxon.py#L45. All the other ranks have similar IRIs, and we define them like this: https://github.com/obophenotype/ncbitaxon/blob/master/src/ncbitaxon.py#L314.
Taxrank is not really active, but we could add to it and I should be able to make a release. I think it would be fine to use it in the NCBI taxonomy product.
I don't know if it is intentional, but ran into this irregularity while parsing. Where all other ranks are represented as local terms
NCBITaxon:superorder
etc, there's one that is represented as URL throughout the obo file: