-
Notifications
You must be signed in to change notification settings - Fork 23
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
There is currently only one* OWL Profile availible #1430
Comments
The ontology is supposed to be written in OWL 2 DL, not OWL 2 Full. Could you point out axioms that violate the DL constraints? Concerning extracting different profiles: I don't know about Robot, but the OWL API is able to validate profiles and identify axioms that are outside a given profile. |
Here is an example of the DL profile validation report: https://gist.github.com/areleu/c7d2c5580bc2f6b4fcb3895fcd1838b5 I ran this using the compiled ontology in the OEP: http://openenergy-platform.org/ontology/oeo/releases/oeo-full.omn It seems that the problem is only a specific annotation done multiple times in the file. Also the pipeline is currently validating against the full profile. Would it make sense to change it to DL?
I noticed that validating like this won't make the pipeline fail. If needed I can think of a way of making this check more strict. |
I found the problem (or at least one). That's not supposed to happen. owl:equivalentClass is a reserved term in the OWL language. It is neither an annotation property nor any other property (or part of the signature of the ontology). Hermit and other OWL reasoners haven't detected it, because they ignore annotations anyway. But the validator throws warnings for each class that uses this kind of 'annotation'. The solution would be either to |
We currently use this to annotate same or similar concepts in other ontologies, especially ENVO. In my view, it is best to introduce a special annotation property for this. Something like |
Maybe we could reuse 'may be identical to' from the IAO? (IAO:0006011)? |
Of course reusing an existing annotation property is even better. |
This issue has gone stale, but it would be nice to solve and implement this before the next release which is planned for next week. @areleu @fabianneuhaus @stap-m : Do we all agree replacing |
I will take over this today. |
So I have a pull request almost ready to replace |
After fixing this now we have a single violation:
Any idea on why is this @fabianneuhaus |
I found the solution: |
I am fine with this simplification. |
The ontology is now DL compliant. For any other profile request please add new issue! |
Description of the issue
Is it intentional that the ontology only uses the OWL2 Full profile? Currently it is not a valid DL ontology and it would be nice to have a RL profile. What is the most reasonable way of having automatic convertion to these profiles?
Ideas of solution
Does robot have a function to convert to a lower profile? If not then we have to remove the incopatible axioms with different means.
Workflow checklist
The text was updated successfully, but these errors were encountered: