fix: unbounded ?focus_node variable in generated SPARQL query for top concepts - #454
Merged
Conversation
…he sparql ?focus_node variable is unbounded #453
edmondchuc
changed the title
Collaborator
|
Thanks Edmond, I don't really understand the implications for concept-heierachy queries, but the change seems pretty self contained. |
recalcitrantsupplant
approved these changes
Jan 12, 2026
|
🎉 This PR is included in version 4.23.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the generated sparql query for top-concepts api route where the sparql ?focus_node variable is unbounded.
Fixes #453
This PR prevents
?focus_node <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ?default_class_var .from being added if the query is aconcept_hierarchy_query.