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

DisjointClass and PropertyAssertion axioms are not being inferred in the ontology with closure. #1583

Open
1 task
areleu opened this issue Jun 15, 2023 · 0 comments
Labels
ontology infrastructure To do Issues that haven't got discussed yet tricky issue Issues that are not easily to solve and needs thinking outside the box

Comments

@areleu
Copy link
Contributor

areleu commented Jun 15, 2023

Description of the issue

For context see #1465

Disjoint class inference takes very long in the ontology, or is probably not possible.

Just for everyones information:

phillord/hermit-reasoner#13 (comment)

The algorithm is by itself slow for the amount of classes we have in the ontology. So we might have to consider providing the disjoint classes by some other means i don't really know how long would the reasoning would take but I suspect it may be too much for github. So probalby we can use some internal server for that, either from Magdeburg or somewhere else.

The PropertyAssertion error is trickier, could not find the root cause.

Ideas of solution

Ignore DisjointClass inference altogether, unless someone finds a specific usecase.

Workflow checklist

  • I am aware of the workflow for this repository
@areleu areleu added the To do Issues that haven't got discussed yet label Jun 15, 2023
@l-emele l-emele added this to the oeo-release-2.2.0 milestone Nov 21, 2023
@stap-m stap-m added ontology infrastructure tricky issue Issues that are not easily to solve and needs thinking outside the box labels Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ontology infrastructure To do Issues that haven't got discussed yet tricky issue Issues that are not easily to solve and needs thinking outside the box
Projects
None yet
Development

No branches or pull requests

4 participants