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

Consistency check produces wrong results when using imports #42

Open
buergerj opened this issue Jun 26, 2019 · 2 comments
Open

Consistency check produces wrong results when using imports #42

buergerj opened this issue Jun 26, 2019 · 2 comments
Labels
bug Developper confirm there is a bug in the product. wontfix Developpers don't have energy to solve that, or the problem can't be solve because of theoric limits

Comments

@buergerj
Copy link

I have a problem concerning the inconsistency check for ontologies using imports.
I provide 2 minimal working examples.
In one case (inconsistency_wo_import), an inconsistent ontology is provided. Openllet detects that and also produces explanations.
But, in case I split this ontology in one providing the classes and object property assertions (inc2) and a second one which imports the first one and defines the individuals and relations (inc2u), Openllet says the ontology is consistent.
inconsistency_wo_import.owl.txt
inc2.owl.txt
inc2u.owl.txt

@Galigator
Copy link
Owner

Thank for the report.

As I remember Openllet simply ignore the 'import' declaration because it can't do a fast check for changes. In many way Pellet/Openllet is design to be efficient way data changes (it is often faster that Fact++ when data change).

So this is a bug, but a bug that probably will never be fix.
I understand the deception, but the easy fix could be to look for import axioms and do manually the import.

@Galigator Galigator added bug Developper confirm there is a bug in the product. wontfix Developpers don't have energy to solve that, or the problem can't be solve because of theoric limits labels Jul 16, 2019
@Locke
Copy link
Contributor

Locke commented Jul 29, 2019

As I currently have another problem with imported ontologies I investigated your report - but cannot reproduce it.

In general, my experience is, that the processing of imports depends on the used framework. I believe that you are missing the pre-loading of the imported ontology.

I uploaded a project (with both OWL API and Jena) where all four tests are detecting the inconsistency: https://github.com/Locke/openllet-issue-42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Developper confirm there is a bug in the product. wontfix Developpers don't have energy to solve that, or the problem can't be solve because of theoric limits
Projects
None yet
Development

No branches or pull requests

3 participants