Version announcement #207
Version announcement #207
Conversation
gkellogg
added
the
spec:editorial
spec/index.html
Outdated
| <p class="note">As HTTP <a data-cite="webarch#frag-coneg">content negotiation</a> is advisory, | ||
| clients recieving a document should be prepared to properly handle a document | ||
| of the requested media type but potentially having a `version` other than what was | ||
| requested. | ||
| Systems may consider down-grading the content to an appropriate version | ||
| as discussed in <a href="#defined-version-labels" class="sectionRef"></a>, | ||
| or by returning a `406 "Not Acceptable"` status in the response.</p> |
There was a problem hiding this comment.
Does "Systems" in the second sentence refer to clients (as mentioned in the first sentence) or to servers?
There was a problem hiding this comment.
Probably better to use "Clients" to be consistent. I'll do an update for this later today.
There was a problem hiding this comment.
But clients wouldn't return a 406, as the sentence would suggest after this change.
There was a problem hiding this comment.
This came from a suggestion in the document, that if a client had requested 1.1, but received 1.2 they could do the downgrade on their side. Not unlike how in JSON-LD clients may receive a document and re-frame it or apply a context to get it into a better format. However, the 406 would not be something a client would do.
Suggestions from @hartig. Co-authored-by: Olaf Hartig <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]> Co-authored-by: Olaf Hartig <[email protected]>
Server and parser behavior on unexpected version announcement.
Also: Mark "atomic" term as exported to silence warnings.
Fixes #161. Fixes #205.
See also w3c/rdf-star-wg#161 and Minutes from 2025-02-29.
Preview | Diff