Announcing the GraphQL over HTTP specification
Comments on “Announcing the GraphQL over HTTP specification”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
The GraphQL Foundation has released the first version of the GraphQL over HTTP specification, a supplementary document that standardizes how GraphQL runs over HTTP. It introduces a dedicated media type and status-code rules so clients can tell well-formed GraphQL responses from proxy or cache errors, improving interoperability and observability for…
Why it ranked
No. 28 of 123 with a score of 0.63. The panel rated it highest on new information (0.93) and practical relevance (0.79), lowest on significance (0.59). Placed No. 28, No. 34 by score alone: the fifth Programming & dev tools story of the day (−0.040). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Announcement of a new HTTP-transport spec for a widely used API standard; practically useful to API builders with concrete status-code guidance, though a moderate-significance release with a bit of promotional framing.
- AI judgeJudge 3gpt-5.6-luna
- A new HTTP transport specification for a widely used API protocol improves interoperability, observability, and error handling. It is practically useful and technically specific, though primarily a standards release rather than a landmark breakthrough.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.63total under rubric v2.3
- Significance0.59
- Reader interest0.67
- Audience breadth0.62
- Practical relevance0.79
- Substantiated0.68
- Technical depth0.65
- New information0.93
- Counts against: Promotional0.16
- Counts against: Overclaim0.16
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.64 | 0.45 | 0.68 | 0.59 | 0.23 | +0.24 | +0.142 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.57 | 0.62 | 0.82 | 0.67 | 0.25 | +0.26 | +0.174 |
| Audience breadthHow many people who build technology does it concern? | 0.56 | 0.60 | 0.70 | 0.62 | 0.14 | +0.13 | +0.080 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.85 | 0.70 | 0.82 | 0.79 | 0.15 | +0.22 | +0.174 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.59 | 0.60 | 0.84 | 0.68 | 0.25 | +0.05 | +0.034 |
| Technical depthHow technically substantive is it? | 0.72 | 0.60 | 0.62 | 0.65 | 0.12 | +0.05 | +0.032 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.90 | 0.98 | 0.93 | 0.08 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.17 | 0.20 | 0.12 | 0.16 | 0.08 | −0.19 | −0.031 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.21 | 0.20 | 0.08 | 0.16 | 0.13 | −0.11 | −0.018 |
| Sum of contributions | +0.634 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.633 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-14/28/"><img src="https://rubric.hrih.si/badge/2026-11-14/28.svg" alt="Ranked #28 on Rubric, 14 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 3 matches source · 2 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkDate
The GraphQL specification has been transport agnostic since GraphQL's initial release in 2015.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Since the initial release of GraphQL in 2015, the GraphQL specification has always been transport agnostic”
The source says No passage could be compared.
Source cited by the article: github.com/graphql/graphql-spec/releases/tag/July2015
Couldn’t checkVersion
The first release of the GraphQL over HTTP specification is being published, as a new document supplementary to the main GraphQL specification.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “This is changing today with the first release of the GraphQL over HTTP specification”
The source says No passage could be compared.
Source cited by the article: http-spec.graphql.org/September2026
No source givenCausal conclusion
Most GraphQL implementations previously set the status code to 200 so that clients could know the response had not been tampered with and was safe to parse as a GraphQL response.
The article gives no link or citation for it.
The article says “most implementations set the status code to : if a client received a status code, it knew the response wasn’t tampered with and was safe to parse as a GraphQL…”
The source says No source to compare with.
Matches sourceGeneralization
The GraphQL over HTTP specification includes detailed guidance on which status codes to use, with a general rule that requests returning only errors return a 4xx or 5xx status code.
The cited source says the same thing.
The article says “The specification includes detailed guidance on which status codes should be used, but implementers may choose to use an alternative status code if it better fits the situation”
The source says “If the GraphQL result does not contain the data entry then it represents a GraphQL request error result and the server MUST reply with an appropriate 4xx or 5xx status…”
Source cited by the article: http-spec.graphql.org/September2026
Matches sourceVersion
The specification introduces a new status code, 294 Partial Success, for responses where both data and errors are present.
The cited source says the same thing.
The article says “The specification also introduces a new status code for use when both and are present; you can read more about 294 Partial Success in the non-normative notes”
The source says “we recommend using the custom code 294 Partial Success”
Source cited by the article: http-spec.graphql.org/September2026
Matches sourceDate
The IETF has just moved the QUERY HTTP verb to a proposed standard.
The cited source says the same thing.
The article says “The IETF just moved the QUERY HTTP verb to a proposed standard”
The source says “This is an Internet Standards Track document”
Source cited by the article: rfc-editor.org/info/rfc10008
Couldn’t checkDate
Persisted queries have been in use since before GraphQL was open sourced in 2015, with different implementations solving performance, security and observability problems.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The technique of persisting GraphQL documents (“persisted queries”) has been in use since before GraphQL was open sourced in 2015”
The source says No passage could be compared.
Source cited by the article: github.com/graphql/graphql-over-http/pull/264
No source givenGeneralization
Most GraphQL frameworks and libraries already support the new specification.
The article gives no link or citation for it.
The article says “Most GraphQL frameworks and libraries out there already support the new specification”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.