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

Some reasoners not working with the ontology #1957

Open
madbkr opened this issue Oct 21, 2024 · 3 comments
Open

Some reasoners not working with the ontology #1957

madbkr opened this issue Oct 21, 2024 · 3 comments
Labels
meta issue Issue that collects information about topics and will be closed after detailled issues are solved. To do Issues that haven't got discussed yet

Comments

@madbkr
Copy link
Contributor

madbkr commented Oct 21, 2024

Description of the issue

I agreed to take a look at the question why the OEO doesn't seem to work with Pellet but works fine with Hermit or ELK. I agreed to document all findings in one issue.

Ideas of solution

If you already have ideas for the solution describe them here

Workflow checklist

  • [x ] I am aware of the workflow for this repository
@madbkr madbkr added To do Issues that haven't got discussed yet meta issue Issue that collects information about topics and will be closed after detailled issues are solved. labels Oct 21, 2024
@madbkr
Copy link
Contributor Author

madbkr commented Oct 21, 2024

First of all:
Not working in the case of pellet means that the reasoner doesn't even initialize. No error message, no progress bar.
HermiT works fine with all OEO files, ELK also works but gives out warnings:

INFO  11:55:25  Potential incompleteness due to occurrences of DataProperty
   INFO  11:55:25  1 occurrence of DataProperty found in the current ontology. Enable DEBUG for details
   INFO  11:55:25  Potential incompleteness due to occurrences of DataPropertyDomain
   INFO  11:55:25  1 occurrence of DataPropertyDomain found in the current ontology. Enable DEBUG for details
   INFO  11:55:25  Potential incompleteness due to occurrences of Datatype
   INFO  11:55:25  6 occurrences of Datatype found in the current ontology. Enable DEBUG for details
   INFO  11:55:25  Potential incompleteness due to occurrences of DisjointObjectProperties
   INFO  11:55:25  16 occurrences of DisjointObjectProperties found in the current ontology. Enable DEBUG for details
   INFO  11:55:25  Potential incompleteness due to occurrences of InverseObjectProperties
   INFO  11:55:25  15 occurrences of InverseObjectProperties found in the current ontology. Enable DEBUG for details
   INFO  11:55:25  ... 6 different incompleteness problem types detected

I will look into those warnings in the future.

@madbkr
Copy link
Contributor Author

madbkr commented Oct 21, 2024

Some testing indicates that Pellet actually does work with the OEO. It only does it very very slowly.

I started the reasoner in all the separate OEO files and Pellet started with no problem - excepts foroeo-physicalwhere it took several minutes.
oeo-shared-axioms which imports oeo-physical was the only file that didn't even show a progress bar anymore.

So I tested if removing some imports from oeo-shared-axioms would make a difference and it does:
Removing oeo-physical fixes the problem entirely.
Keeping oeo-physical and ONE other same level import (like oeo-model or oeo-sector) will still work but Pellet takes several hours to start.

From this I would conclude that Pellet would eventually start in the whole OEO - but may very well take days to do so.

In my opinion the problem is either:

@madbkr
Copy link
Contributor Author

madbkr commented Oct 21, 2024

Apparently it is possible to set up Pellet directly via command line or via the ontology tool NeOn. Sadly I couldn't get NeOn or the command option to run on my system to test it - at least not yet.

This would test if the problem may be related to Protégé.

However as we are also working with the ROBOT tool we might want to stay away from Pellet anyway as ROBOT doesn't support it in it's reasoning functions while HermiT and ELK are supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta issue Issue that collects information about topics and will be closed after detailled issues are solved. To do Issues that haven't got discussed yet
Projects
Status: To do
Development

No branches or pull requests

1 participant