stuckyb
import ontology versioning
Ideally, OntoPilot should check if newer versions of imported ontologies are available and if so, at a minimum, ask the user if he/she wants to use the newer version.
If importing an OBO Foundry ontology, unless you specify a version in your import statement, using the PURL to import should always get the latest version.
This is a slightly different issue, @ramonawalls. The problem is once you have a local copy of a remote ontology cached, how do you determine if the remote ontology has been revised or updated without downloading the whole thing every time? Turns out that is not an easy problem to solve, but we are investigating what might be possible by examining HTTP response headers.
I see. Sounds like a nice to have feature, but not crucial for most uses.