Open mikael1234 opened 4 years ago
Not reporting an error on oro:kover
is expected behaviour. In that axiom, an individual is expected, and individual declaration is optional.
Adding random characters after the ontology raises an error about oro:kover
because those are expected to be further properties asserted against the individual. The parser is not complaining because the entity is undeclared - although the particular exception thrown will depend on what patterns the parser is attempting to detect.
Result is true for attached files and command line
java -jar HermiT.jar --premise=file:///tmp/oro1_s.maowl --conclusion=file:///tmp/oro1_s_ck.maowl --checkEntailment
even when last line contains unknown entiry oro:kover. When some garbage is added after that, parser gives correct error about oro:kover. There are many similar cases when entailment result is true regardless of the content of the check file. HermiT 1.38 works for those cases.
files.zip