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

Term completes then isn't accepted in class expression box #1217

Closed
alanruttenberg opened this issue Jun 10, 2024 · 4 comments
Closed

Term completes then isn't accepted in class expression box #1217

alanruttenberg opened this issue Jun 10, 2024 · 4 comments

Comments

@alanruttenberg
Copy link

I have a term "Earth's Moon". When completing it completes as 'Earth's Moon', which it then red-underlines and won't accept.

@ykazakov
Copy link
Contributor

I cannot reproduce that. What kind of term? A class? Is that the name of the class or the name of the rdfs:label? With the label both with or without double quotes, autocompletion produces an escaped string, which is accepted.

Screenshot 2024-06-10 at 18 45 20 Screenshot 2024-06-10 at 18 46 30

@alanruttenberg
Copy link
Author

alanruttenberg commented Jun 11, 2024

"Earth's Moon" is an instance. Try it in a value restriction. c value 'Earth<complete>
Also it looks like the double quote are part of the label in your example?

@ykazakov
Copy link
Contributor

Also it looks like the double quote are part of the label in your example?

I did not know whether they should be, so I tried both ways.

"Earth's Moon" is an instance. Try it in a value restriction. c value 'Earth

OK, with individual I could reproduce the problem!

Screenshot 2024-06-11 at 12 22 27

@ykazakov
Copy link
Contributor

I think the problem is in OWLEntityFinderImpl: for OWLClasses the escape characters are preprocessed, whereas for all other entities they are not:

OWLClass cls = renderingCache.getOWLClass(stripAndEscapeRendering(rendering));

OWLNamedIndividual individual = renderingCache.getOWLIndividual(rendering);

The fix should be easy.

gouttegd added a commit that referenced this issue Jun 18, 2024
Process escape characters when searching for entities, fix #1217
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