a few small changes for interaction with the reasoner #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
effect on reasoning results (only those applied to ontologies in the import closure may have)
matthewhorridge
added a commit
that referenced
this pull request
Mar 30, 2015
Thanks a lot for the contribution Yevgeny!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I made a small change which catches and ignores the UnsupportedOperationException when executing reasoning task. This way, owl reasoners can throw exception for reasoning tasks that they do not support and Protege will not misbehave (it should act, in principle, the same as if the reasoning task is not enabled).
The second change is a bit more clever way for a reasoner in non-buffering mode to understand when changes in ontology may require reclassification. Essentially, only logical or import changes to ontologies in the import closure should be considered.