Skip to content
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

Entailment check is broken with command line 1.4.6.519 #9

Open
mikael1234 opened this issue May 21, 2020 · 1 comment
Open

Entailment check is broken with command line 1.4.6.519 #9

mikael1234 opened this issue May 21, 2020 · 1 comment

Comments

@mikael1234
Copy link

mikael1234 commented May 21, 2020

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

@ignazio1977
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants