Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

import ontology versioning #59

Open
stuckyb opened this issue Mar 23, 2017 · 3 comments
Open

import ontology versioning #59

stuckyb opened this issue Mar 23, 2017 · 3 comments

Comments

@stuckyb
Copy link
Owner

stuckyb commented Mar 23, 2017

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.

@ramonawalls
Copy link
Collaborator

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.

@stuckyb
Copy link
Owner Author

stuckyb commented Apr 25, 2017

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.

@ramonawalls
Copy link
Collaborator

I see. Sounds like a nice to have feature, but not crucial for most uses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants