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

Feature request: Option to exclude obsolete classes from results #15

Closed
matentzn opened this issue May 30, 2018 · 2 comments
Closed

Feature request: Option to exclude obsolete classes from results #15

matentzn opened this issue May 30, 2018 · 2 comments

Comments

@matentzn
Copy link

At the moment, owlery returns obsolete classes as part of their responses. It would be great (and for applications probably necessary) to be able to exclude those. Example: this query returns http://purl.obolibrary.org/obo/FBbt_00002047, which is obsolete.

@balhoff balhoff closed this as completed in 387951e Jun 5, 2018
@balhoff
Copy link
Member

balhoff commented Jun 5, 2018

This is implemented in master now. Use includeDeprecated=false (default is true).

@balhoff
Copy link
Member

balhoff commented Jun 5, 2018

This depends on performance of OWL API to search for annotations here:

EntitySearcher.getAnnotations(entity, o, factory.getOWLDeprecated).asScala.exists { v =>

I don't know if they have an index, or it just scans through. If that is slow for some reason, we can make an index of deprecated classes at startup.

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