Summary

  • W3C's public WebTransport group and charter-history pages showed the active charter ending on 30 August 2026 when checked on 31 August.
  • The proposed successor charter still said PROPOSED, carried placeholder start and end dates, and the public strategy issue remained open.
  • The WebTransport Candidate Recommendation Snapshot, published on 30 July, remains in wide review until at least 30 October and still needs implementation evidence.
  • A technical report can continue to exist after a charter date. The missing public fact is narrower: which current authority instrument governs the group's next decisions.
  • W3C should publish a charter-authority receipt joining adopted charter, extensions, successor decision, deliverable clocks, participation and Patent Policy state without pretending that an unpublished act did not occur.

Two clocks crossed at midnight

On 30 July, W3C published WebTransport as a Candidate Recommendation Snapshot. Its status section gives reviewers until at least 30 October. It asks for implementation experience, requires two independent interoperable user agents to pass the test suite before advancement, and says the Working Group will prepare an implementation report.

The institutional clock is shorter on the public record. W3C's WebTransport group page said “Chartered until 30 August 2026” when checked the next day. The charter-history page still marked the charter that began in September 2024 as active, with extensions through 30 June and then 30 August.

Those statements do not cancel each other. A published technical report is not a lease that vanishes when its authoring group reaches a date. Public comments can still be filed. Implementers can still test. The CR itself remains a W3C publication governed by the Process identified in its status section.

But a review period does not answer a different question: who may make the next group decision? Someone must evaluate implementation evidence, decide what change belongs in scope, authorize a later publication, manage objections, and maintain or close the work. Those actions depend on an institutional authority path, not on the mere persistence of a URL.

The public successor is still a proposal

W3C began refinement of a replacement charter on 6 May. The notice pointed participants to Strategy issue 537 and estimated that refinement would last until roughly 3 June. The issue recorded practical comments: the draft used an older template; one coordination body had closed; milestones no longer matched the work; success criteria and Patent Policy language needed attention.

By 1 June, the charter editor said the draft had been aligned with the newer template, the closed group removed, the timeline revised and the external WebSocket reference repaired. That is visible review producing visible changes.

The next formal public step arrived on 17 July. W3C invited Advisory Committee review through 21 August and extended the existing charter through 30 August to accommodate it. The notice did not say that 30 August was a grace period after approval. It identified the extension as support for the review period.

After the review deadline, the strategy thread still moved. A late, non-blocking security comment about possible peer-to-peer incubation received a response on 24 August. Yet at the 31 August cutoff, the public charter was still headed PROPOSED. Its start field still contained a date placeholder tied to the Call for Participation, and its end field still contained a placeholder for two years after approval. Strategy issue 537 remained open.

This is not evidence that W3C took no decision. An Advisory Committee review has Member-only components, and a public projection may lag an authoritative internal notice. The responsible claim is simply that the checked public surfaces did not yet show an approved successor or another extension after the date they displayed.

The CR carries its own, different state

WebTransport's publication history makes the separation unusually useful. On 22 July, the chairs reported five email responses supporting the transition from the 6 July Working Draft to a Candidate Recommendation Snapshot and no objections. They found Working Group consensus to publish. W3C completed the transition eight days later.

The CR is careful about what that means. Publication does not imply endorsement by W3C or its Members. Candidate Recommendation is a stage for wide review and implementation experience. Advancement depends on tests and independent interoperable implementations. Future changes remain possible.

Five supportive messages therefore establish a recorded group publication decision, not a public electorate and not a decision to recharter the group. Likewise, a CR status does not extend a charter. These are separate acts with separate decision makers and separate evidence.

The proposed successor charter makes the intended future machinery visible. It projects a September 2026 CR milestone and a December 2027 Recommendation, requires open tests and two interoperable implementations, describes public technical work, sets a consensus and asynchronous decision policy, and moves the group under the 15 May 2025 Patent Policy. It also contemplates a two-year duration.

Yet intention is not current authority. Until an approved instrument and effective dates are visible, the proposal can explain where the institution wants to go but not prove the state from which it is acting.

“Expired” is too strong; “current” is too easy

There are two common mistakes at this boundary.

The first is to look at 30 August and declare the group unauthorized. A status page may be stale. A Member announcement may exist. A decision may be awaiting public projection. None of the public sources checked here establishes misconduct, invalid publication or a breach of Process.

The second mistake is to assume continuity because work continues. Technical continuity does not itself settle scope, participation, patent commitments or decision authority. A proposal to incubate peer-to-peer capability, for example, raises a scope question that is different from maintaining the client-server CR already published. The correct charter matters precisely when the work changes.

The W3C Process treats duration as a required charter term. A new or substantially changed charter needs a W3C Decision after Advisory Committee review. A short extension is a distinct Team act, and the announcement must carry the new duration, rationale, charter reference and group homepage. Closure has Patent Policy implications. These are not decorative labels around engineering; they define who can do what next.

The public record should therefore distinguish four states: approved and active, extended, decision made but not yet projected, and public status unverified. Collapsing all four into “active” hides the evidence. Collapsing them into “expired” invents a conclusion.

A charter-authority receipt

The remedy is small enough to be boring, which is a virtue. Every chartered group should have one current, machine-readable and human-readable authority receipt.

It should name the adopted charter, the approving decision, effective dates and every extension. It should show the successor charter's state—refinement, AC review, decision pending, approved, abandoned or superseded—and link the public disposition, decision and Call for Participation where available.

It should also answer the operational question. Which decisions can the group still take today? Which deliverables remain active? Who owns maintenance if a technical report outlives the group's ordinary term? What participation designations and Patent Policy commitments apply to new contributions? Which authority event superseded the previous end date?

Finally, the receipt needs a confidence boundary: last verified time, source visibility, correction history, and an explicit difference between not publicly posted and not decided.

The current W3C group page already centralizes leadership, tools, participation and charter links. The missing piece is not a new bureaucracy. It is one authoritative state transition that updates atomically when a charter is extended, replaced or closed.

What this case does not decide

Nothing here judges WebTransport's technical quality. The CR may be strong or weak; that is a different review. The article does not reconstruct Advisory Committee votes, Formal Objections or Member-only correspondence. It does not say the group met, published or changed text after its authority ended. It does not say the CR becomes invalid when the displayed charter date passes.

The IETF-W3C directory link is contextual. The CR says the API is being developed with protocol specifications from the IETF WEBTRANS Working Group; the directory entry is not a claim that it represents the W3C WebTransport Working Group itself.

The finding is deliberately narrow. On 31 August, one official public surface described a charter ending on 30 August, another still described the successor as proposed, and the technical report continued on a review calendar through October. That is enough to require a clearer public receipt. It is not enough to allege an absent decision.

Sources

  1. W3C — WebTransport Working Group
  2. W3C — WebTransport Working Group charter history
  3. W3C — 2024 WebTransport Working Group Charter
  4. W3C — Proposed 2026 WebTransport Working Group Charter
  5. W3C — Proposed Charter and extension notice, 17 July 2026
  6. W3C — Start of charter refinement, 6 May 2026
  7. w3c/strategy Issue 537
  8. W3C — CR publication CfC outcome, 22 July 2026
  9. W3C — WebTransport Candidate Recommendation Snapshot
  10. W3C — Call for Wide Review
  11. W3C Process Document, 18 August 2025
  12. W3C — How to create a Working Group or Interest Group Charter
  13. Heng Lu — On the Multi-Stakeholder Mirage