Spec references RFC7231 which is obsoleted about graphql-over-http

[michaelstaib]

Sure, the thing here is that we started work on this SPEC in 2019 so references might get obsoleted by the time we are finished with it. Before we ratify it we must go through and update spec links again. We will put an action item on this for when we do the finishing touches to go over spec references and validate / update them.

[michaelstaib]

That the specs get out of date sometimes is not so much a problem, in these case we just need to check the changelog to verify and do PR to update. I went over the changes and there is nothing changed that concerns the accept/content-negotiation semantics.

I like the suggestion adding the RFC title. Could be in braces.

[michaelstaib]

I agree, we should make it easier for the reader and refer to concrete sections that we refer to if possible. In the concrete case it would be content negotiation.

https://datatracker.ietf.org/doc/html/rfc9110/#section-12.4

[rivantsov]

well, links get obsolete over time - that's understandable. But in this case, it's at time of spec publishing. Better be updated i think