You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User should optionally be able to specify a path to the most recent editors version of the ontology prior to this release.
Prior to building, Oort can compare the current editors version with the previous one and check that every ID in the previous one is accounted for in the most recent one. In OBODoc terms, every ID should still be there (either for a deprecated or non-deprecated class) OR should be present as an altId.
In future we can also allow plugging in of OWLDiff or Amelia visual ontology differencing tool (though we may want to do this outside Oort, e.g. in Jenkins)
From cmung...@gmail.com on December 20, 2011 14:53:04
User should optionally be able to specify a path to the most recent editors version of the ontology prior to this release.
Prior to building, Oort can compare the current editors version with the previous one and check that every ID in the previous one is accounted for in the most recent one. In OBODoc terms, every ID should still be there (either for a deprecated or non-deprecated class) OR should be present as an altId.
In future we can also allow plugging in of OWLDiff or Amelia visual ontology differencing tool (though we may want to do this outside Oort, e.g. in Jenkins)
Original issue: http://code.google.com/p/owltools/issues/detail?id=28
The text was updated successfully, but these errors were encountered: