importing bfo 1.1 and 2.0 at the same time #39
Comments
|
https://github.com/information-artifact-ontology/IAO/blob/master/docs/BFO%201.1%20to%202.0%20conversion/mapping.txt is extremely useful for transitioning from 1.1 to 2.0 |
tgbugs
added a commit
that referenced
this issue
Oct 16, 2017
uri switch, backend refactor, and 3.0
This pull request includes 3 major changes for the 3.0 release of NIFSTD.
All NIFSTD native identifiers have been switched to use the uri.neuinfo.org resolver. This closes #59.
Major reworking of the import chain (see #115 for reference), including importing most external ontologies from their canonical iris.
All backend ObjectProperties have been switched to use BFO2/RO/IAO. This closes #39.
The current state of the ontology produces reasoning errors because of obophenotype/uberon#1370. These will persist until that issue is resolved or I complete our load time patching infrastructure.
The old backend is not completely gone since we still import an old version of pr that uses the old BFO1.1 backend. The new pr is huge and switching requires further review/planning since it cannot be dropped directly into the ontology as is and thus did not make the cut for updating the 3.0 release. ero.owl was removed from the import chain pending a review of its classes.
This pull request also starts the process of moving documentation into the repository from the GitHub wiki to reduce dependence on external systems.
Note that this pull request also moves the scigraph/ folder and associated loading and curie mapping (which defines the qnames used by the ontology) to pyontutils/scigraph.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If we are going to use bfo we should at least use one of it.
The text was updated successfully, but these errors were encountered: