-
Notifications
You must be signed in to change notification settings - Fork 13
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
[owlapi] incomplete complex assertion to KB transformation. #199
Comments
Do we actually ever produce any owl:Thing facts for individuals? If we want completeness w.r.t. owl:Thing, we would also need to add further facts of this kind ... Probably the converter should also clarify in its documentation what the expected behaviour is; maybe completness w.r.t. to owl:Thing is not desirable anyway (too many facts); but cases like in this bug should of course be covered.. |
Indeed, we never create any owl:Thing facts. We only use owl:Thing for rules with empty bodies and owl:Nothing for rules with empty heads. Is this intended? Are we supposed to clarify in the documentation that the ontology provider has the responsibility to ensure completeness w.r to owl:Thing? (for example, creating axioms that insure that each class in the ontology is a subclass of owl:Thing, and each role has domain and range owl:Thing)? |
Wouldn't it be a fix to allow for rules with an empty body? Then one could translate the problematic OWL class assertion into the rule There is also a difference in the treatment of the notion "fact". In the IJCAR2018 paper a fact is a rule with an empty body. Thus |
For an OWL ontology containing (only) the following complex assertion
ClassAssertion(ObjectSomeValuesFrom(<a> <b>) <c>)
OwlToRulesConverter
generates a kb with an empty set of facts and the single rulea(c, !Y1), b(!Y1) :- <http://www.w3.org/2002/07/owl#Thing>(c) .
As our reasoner is agnostic of the fact that
<http://www.w3.org/2002/07/owl#Thing>(x)
is true for any individualx
, a complete transformation must also produce the fact<http://www.w3.org/2002/07/owl#Thing>(c) .
.Find attached a java class with code that reproduces the bug (in .txt format)
The text was updated successfully, but these errors were encountered: