Conversation
chore: back-merge main into develop
Names the values a reader may change, so the web app can offer them as a form. Two variables on one line declare a range.
Annotate queries with parameter declarations
Label the date parameters after what the form offers
Anoop-Variyan
approved these changes
Aug 26, 2026
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
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.
Publishes the parameter declarations, ready for the 2.4.0 web app.
Since
mainwas last published,develophas gained two things.Parameter declarations on 33 of the 38 queries (#13). A query can now name a variable in a comment, and the web app offers that value as a field when the query is run:
The comment carries only which variable is offered and what to call it on screen. Everything else — the type of the field, the value it opens with, whether two bounds are a range — the application reads from the query itself. Nothing here is a second copy of the query that can fall out of step with it, and every query still runs unchanged in any SPARQL client that ignores comments.
Labels corrected on five of them (#14). Five declarations said "Publication month" or "Publication year" where the form offers days. They now say "Publication date". What the queries group by has not changed.
The
READMEandCONTRIBUTINGexplain the convention and what to check before opening a pull request.Order of publishing
Nothing here requires the web app: a query that declares a parameter reads exactly as it did to a client that does not know about the convention, and the current published app ignores the comment. So this can be merged whenever it suits, before or after OP-TED/ted-open-data#132.