Skip to content

fix(citations): GPC is now a W3C Privacy WG draft; NodeInfo over HTTPS - #134

Draft
jdevalk wants to merge 1 commit into
mainfrom
fix/citations-privacy-wellknown-2026-07-29
Draft

fix(citations): GPC is now a W3C Privacy WG draft; NodeInfo over HTTPS#134
jdevalk wants to merge 1 commit into
mainfrom
fix/citations-privacy-wellknown-2026-07-29

Conversation

@jdevalk

@jdevalk jdevalk commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Rotating citation slice for this run: privacy + well-known (the two categories longest since a check — accessibility and foundations were swept in #130/#129, performance in #120, i18n/resilience/seo in #112).

What changed

global-privacy-control — the substantive one. GPC has left the Privacy Community Group. It is now published by the W3C Privacy Working Group on the Recommendation track:

"This document was published by the Privacy Working Group as a Working Draft using the Recommendation track."
https://www.w3.org/TR/gpc/ (WD-gpc-20260611, 11 June 2026)

So the page had two things wrong: it cited the editor's draft (w3c.github.io/gpc/) rather than the published /TR/ version, and it attributed the spec to a "W3C Community Group". Both fixed, and the source title now says W3C Working Draft so the citation is honest about maturity — this is a WD, not a REC.

The page's status: recommended does not move. GPC's weight comes from CCPA/CPRA and the Colorado Privacy Act, not from its W3C maturity level, and those citations are unchanged.

nodeinfo — both NodeInfo project sources were cited over plain http://. The HTTPS origin serves them fine, so this was just rot. Mildly embarrassing on a spec that lists HTTPS as required.

One deliberate non-change: the http://nodeinfo.diaspora.software/ns/schema/2.x strings inside the JSON sample are protocol rel identifiers, not fetchable URLs. Rewriting those to https:// would break the example. They stay.

Verification

npm run build passes (164 pages indexed), npm run lint and npm run format:check clean, SKILL.md digest check passes (no page/category count change).

For the maintainer

No changelog entry included. Per CLAUDE.md this is a citation fix, not a change to what the spec says — but the GPC one is borderline, since "this spec is now on the W3C Recommendation track" is a real fact about the topic. Happy to add a changed entry if you'd rather log it.

🤖 Generated with Claude Code

Rotating citation slice for this run: privacy + well-known.

- global-privacy-control: the spec left the Privacy Community Group.
  It is now published by the W3C Privacy Working Group on the
  Recommendation track (WD-gpc-20260611). Cite the published /TR/
  version instead of the editor's draft, and fix the publisher.
- nodeinfo: both project sources were cited over plain http://. The
  HTTPS origin serves them fine. The http:// strings inside the code
  sample are protocol rel identifiers, not URLs, and stay as they are.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying specification-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 354c887
Status: ✅  Deploy successful!
Preview URL: https://4734edaa.specification-website.pages.dev
Branch Preview URL: https://fix-citations-privacy-wellkn.specification-website.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant