search

solid / web-access-control-spec

Web Access Control (WAC)
https://solid.github.io/web-access-control-spec/
MIT License
121 stars 25 forks source link

Feat: update HTTP refs #119

Closed woutermont closed 1 year ago

woutermont commented 1 year ago

Following up on https://github.com/solid/specification/issues/471, this PR updates the references to HTTP RFCs from 723x to 911x, and removes the (here unused) reference to the obsoleted RFC3864.

Changes

Commit Target Correction class Note
b4752b9 #resource 2 (no conformance impact; no change in semantics of 'resource') updates reference RFC7231 => RFC9110 in resource definition
e1901de #server-get-acl-without-representation 2 (no conformance impact; no change in semantics of GET, HEAD or 404 updates reference RFC7231 => RFC9110 in behavior of ACR without representation
4499168 5cde143 #wac-allow 2 (no conformance impact; RFC9110 only adds notation for case sensitive syntax, which does not clash with the wac-allow defintion) updates reference RFC7231 (notation) => RFC9110 (notation) + corrects section number
41fd394 #consider-uri-http 2 (no conformance impact; considerations were shuffled but not changed) updates links to RFC7230/7231 => RFC9110/9112 in security considerations
5d8d55a #bib-rfc3864 1 (no content change, only bibliography) removes (unused) reference to obsolete RFC3864
820ead3 #bib-rfc7231 1 (no content change, only bibliography) removes reference to obsolete RFC7231
ac6b920 7921df4 #bib-rfc9110 1 (no content change, only bibliography) inserts reference to replacing RFC9110
16028e8 7921df4 #bib-rfc9112 1 (no content change, only bibliography) inserts reference to replacing RFC9112

HTML Preview | HTML Diff

If there still are any concerns about impact to conformance, you can check the relevant changelogs here:

On a sidenote: do you all manually update the HTML here? Bikeshed or ReSpec are quite handy in keeping track of references, amongst other things.

woutermont commented 1 year ago

Given the lack of impact of this change, I suggest merging this by next meeting 2023-08-30, at the discretion of the editors, of course. @csarven

Also: should I include these changes in the changelog, or is that done when a new version is actually published?

woutermont commented 1 year ago

Pinging @csarven again for approval and merge.