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

Using an individual as the object of an annotation axiom #9

Open
dosumis opened this issue Apr 18, 2017 · 4 comments
Open

Using an individual as the object of an annotation axiom #9

dosumis opened this issue Apr 18, 2017 · 4 comments

Comments

@dosumis
Copy link

dosumis commented Apr 18, 2017

It is not possible to use an individual as the object of an annotation axiom specified using scowl annotation or annotations.

I believe this is legal (if slightly odd) OWL. Protege handles it fine, e.g.:

image

Would it be too much of a stretch to extend SCOWL to handle this?

@dosumis
Copy link
Author

dosumis commented Apr 18, 2017

Example (Manchester Syntax):

image
image

image

@dosumis
Copy link
Author

dosumis commented Apr 25, 2017

This issue is now a blocker for me (urgently required for SynGO project). Any chance you could let me know how likely it is you'll be able to add this functionality and if so what a likely timescale might be? If this is not likely to be added soon, could you share some code showing how to do this directly with the OWL-API?

Many thanks!

@dosumis
Copy link
Author

dosumis commented Apr 25, 2017

Scratch that. Now got it working by converting all OWLNamedIndividuals to IRIs (after figuring out javadoc for OWLAnnotationAxiom). Perhaps worth adding an example of how to do this do your docs?

@balhoff
Copy link
Member

balhoff commented Apr 25, 2017

David, it's the same situation as for using OWLIndividuals as subjects of annotations. It works much more cleanly if your object is typed as either an OWLNamedIndividual or an OWLAnonymousIndividual. There is some awkwardness in the class hierarchy there, and if I add the implicit conversions needed for supporting OWLIndividual, the implicits become ambiguous because more than one can apply, so the compiler complains.

Can you type everything as OWLNamedIndividual? I don't think you need to collapse them to IRIs.

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