You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All version IRIs that look like OBO purls, i.e. http://purl.obolibrary.org/obo/t4fs/releases/2022-05-05/t4fs.owl, always resolve to some Berkley page. To be really consistent, we need to check if the ontology located at the version IRI is identical to the one in the analysis, or, at least, to check that it is, indeed, an ontology.
The text was updated successfully, but these errors were encountered:
For the cited ontology it is easy to see why: There's no purl configuration YAML file (see list at https://github.com/OBOFoundry/purl.obolibrary.org/tree/master/config). For others, it is probably because the version IRIs weren't set up. I can see that some ontologies have that (pr, chebi, doid, obi, probably others).
Yeah, what I would have hoped is that our Dashboard check would catch that and say: "Version IRI does not resolve" - but it does resolve. Just not to the right file!
Oh, sorry, it seemed that you were referring to some defect in the PURL redirect system itself. By the way, once in a while that system does seem to fail, so even a properly-formed PURL--that points to the correct file under normal circumstances--will redirect to that Berkeley page. Hopefully this won't happen while a dashboard check is being run.
All version IRIs that look like OBO purls, i.e. http://purl.obolibrary.org/obo/t4fs/releases/2022-05-05/t4fs.owl, always resolve to some Berkley page. To be really consistent, we need to check if the ontology located at the version IRI is identical to the one in the analysis, or, at least, to check that it is, indeed, an ontology.
The text was updated successfully, but these errors were encountered: