Skip to content

Publish: parameter declarations on the query library - #15

Merged
rousso merged 6 commits into
mainfrom
develop
Aug 26, 2026
Merged

rousso merged 6 commits into
mainfrom
develop

Conversation

@rousso

@rousso rousso commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Publishes the parameter declarations, ready for the 2.4.0 web app.

Since main was last published, develop has 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:

# ?publicationDate: Publication date

FILTER (?publicationDate >= "2025-01-01"^^xsd:date &&
        ?publicationDate <= "2025-12-31"^^xsd:date)

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 README and CONTRIBUTING explain 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.

rousso and others added 6 commits August 22, 2026 14:08
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 Anoop-Variyan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed this is exactly the union of #13 and #14 (diffed main..develop: 35 files, matching both already-reviewed PRs, nothing extra). Both were individually reviewed and approved. Approving.

@rousso
rousso merged commit 4d1ccfa into main Aug 26, 2026
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants