Refer rfc 9110, over obsolated 7230, 7231, 7232, 7233, 7235, 7538, 7615, 7694

[damooo]

RFC 9110 HTTP Semantics obsolates previous many scattered specs like 7230, 7231, 7232, 7233, 7235, 7538, 7615, 7694, etc in one consistant http-semantics rfc.

It may be useful if 9110 is referred instead of many of those.

[woutermont]

Since I am also regularly bumping into this, you can assign this to me to check for any changes and create the necessary PRs, @csarven.

Just to be complete: RFC9110 also updates RFC3864, so let's not forget that one.

[csarven]

Wouter, all yours! Thanks. Happy to review this.

Suggestions:

• Note any changes in behaviour that may effect conformance.
• Note if such changes above may impact interoperability for (some of the) existing implementations.
• Use most specific or closest identifiers in (sentence-level) anchors when referring to notions in cited documents. The items in the Reference section can still use the document URL (without fragment).

[woutermont]

Tracking specs with updates here.

• Solid QA (Feat: update HTTP refs in QA #559)
• WebID Profile (Feat: update HTTP refs webid-profile#99)
• Web Access Control (Feat: update HTTP refs web-access-control-spec#119)
• Solid Notifications (Feat: update HTTP refs notifications#187)
• Solid Protocol (Feat: update HTTP refs in protocol #561)