Skip to content

Update description of normative expectations of query results.#43

Merged
kasei merged 5 commits intow3c:mainfrom
kasei:gtw-query-result-type
Apr 26, 2026
Merged

Update description of normative expectations of query results.#43
kasei merged 5 commits intow3c:mainfrom
kasei:gtw-query-result-type

Conversation

@kasei
Copy link
Copy Markdown
Contributor

@kasei kasei commented Apr 14, 2026

Changes the wording so that the expected results of a query request is any valid SPARQL results or RDF format (instead of expecting specifically SPARQL XML, JSON, or CSV/TSV in the case of SPARQL results).


Preview | Diff

Changes the wording so that the expected results of a query request is any
valid SPARQL results or RDF format (instead of expecting specifically
SPARQL XML, JSON, or CSV/TSV in the case of SPARQL results).
@kasei kasei requested review from Tpt, afs and rubensworks April 14, 2026 03:09
Comment thread spec/index.html Outdated
Comment thread spec/index.html Outdated
<ul>
<li>SPARQL Results:
<ul>
<li>[[[SPARQL12-RESULTS-XML]]]</li>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I would make these references informative and not normative ones:

Suggested change
<li>[[[SPARQL12-RESULTS-XML]]]</li>
<li>[[[?SPARQL12-RESULTS-XML]]]</li>

(same everywhere else)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Agreed,. Fixed.

Comment thread spec/index.html Outdated
@kasei kasei marked this pull request as ready for review April 14, 2026 15:58
@kasei
Copy link
Copy Markdown
Contributor Author

kasei commented Apr 16, 2026

@lisp – I'm responding to your emailed comments here so that we can keep the discussion centralized and understand when all issues have been resolved.

the change would establish the terms to use in the manifest.

I'm not sure what this means. Can you clarify?

my only suggestion would be to either replace "be in a format corresponding to" to "be a media type corresponding to" or to adopt the phasing which appears later, which refers to sparql results documents and rdf graphs.

For context, the start of that sentence is: "The response to a query request must be in a format corresponding to SPARQL Results, or RDF…". I don't think your suggested wording makes sense, because the response Is not "a media type" (it has a media type). Would you accept "response to a query request must use a media type corresponding to…"?

@kasei
Copy link
Copy Markdown
Contributor Author

kasei commented Apr 26, 2026

@lisp – I'm going to go ahead and merge this. If you have ongoing concerns, let's discuss in a new issue or PR.

@kasei kasei merged commit 161a863 into w3c:main Apr 26, 2026
2 checks passed
@lisp
Copy link
Copy Markdown

lisp commented Apr 27, 2026

i had none.
i believe that the manifest document in w3c/rdf-tests#324 adopts the same formulation.

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.

6 participants