Closed tmprd closed 7 months ago
ThHanke
commented
7 months ago Can confirm that bug. Redirect must be corrected here: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/bfo.yml At least all links including string "BFO-ontology/BFO-2020" are broken!
johnbeve
commented
7 months ago @ThHanke @tmprd Thanks to you both; @alanruttenberg and I are working out a solution and will hopefully have this resolved today.
For others observing the issue: redirects need correcting owing to changes from this PR: https://github.com/BFO-ontology/BFO-2020/pull/73
linikujp
commented
7 months ago post related issues opened in BFO repo here: https://github.com/BFO-ontology/BFO/issues/235
johnbeve
commented
7 months ago @tmprd @ThHanke PURLs updated in this PR: https://github.com/OBOFoundry/purl.obolibrary.org/pull/971
Quick summary -
Point to the BFO-Core file in OWL and TTL respectively, while
points to the temporalized relations version of BFO.
Please see documentation here explaining the distinction.
@linikujp dashboard issues addressed too, see: https://github.com/BFO-ontology/BFO/issues/235
http://purl.obolibrary.org/obo/bfo/2020/bfo.owl points to the old location of bfo-2020.owl in this repo, which now yields a 404 response.
I think now there should be a PURL which points to bfo-core.ttl. Would it be http://purl.obolibrary.org/obo/bfo/2020/bfo-core.ttl ?
I'm not familiar with best practices for https://github.com/OBOFoundry/purl.obolibrary.org which I think manages this. This seems like a tricky thing to test prior to changing the directory or filenames referenced on a particular branch.