-
Notifications
You must be signed in to change notification settings - Fork 28
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 UBERON into BFO based ontology #1220
Comments
I'm updating the build process to include bridging axioms to BFO then run everything through the test suite. You shouldn't need to make any changes, provided you can wait til the next release, probably next week |
Hmm travis still shows build passing, need to investigate further... can I confirm the exact combination of purls you are combining? |
Latest on this: a few releases ago we noticed that combing RO with Uberon resulted in Elk hanging. This was resolved by reverting to a previous RO. This is possibly the reason for the difference in our results. The RO issue will be hard to resolve, there is no axiom that is obviously problematic, and if Elk hangs it makes it very hard to debug the ontology... |
The PURL I've been using for UBERON is http://purl.obolibrary.org/obo/uberon.owl. The ontology version IRI is http://purl.obolibrary.org/obo/uberon/releases/2016-05-11/uberon.owl. I tried building UBERON myself from the git repos. But, I can't seem to get it working correctly. Is there a document that explains how to do this and what libraries you need? |
I can provide docs if you really need to do that, but I suspect you don't. Uberon has a very particular and complex development cycle... the PURLs should be fine. Would you be able to post a screenshot of the explanation of the unsatisfiability? I'm still having trouble reproducing. |
Also if you can post the ELk version too |
The version of ELk is 0.4.3. The version of Protege is 5-RC-1. The attached screenshots are:
I've also attached the MIREOT of UBERON (as a zip file) that I am using. |
Thanks! |
…/auditory apparatus; changed to part-of. This fixes many dual classifications under material and immaterial See obophenotype/uberon#1220
WARNING: This issue has been automatically closed because it has not been updated in more than 3 years. Please re-open it if you still need this to be addressed addressed addressed – we are now getting some resources to deal with such issues. |
I am trying to use UBERON for an ontology of GYN cancers. My import of UBERON, however, is not aligned with BFO in the sense that UBERON:material anatomical entity is not a subtype of BFO:material entity and UBERON:immaterial anatomical entity is not a subtype of BFO:immaterial anatomical entity.
When I add axioms to align the UBERON and BFO types, UBERON becomes inconsistent (using ELK reasoner). This presents me with interesting choices:
Has anyone else dealt with this?
Thanks,
Bill
The text was updated successfully, but these errors were encountered: