← Governance
Spec maintainers
Editors
Editors maintain the specification's text, its versioning, and the merges. They execute the council's and working groups' decisions — they do not make them.
Mandate
Someone has to keep the document coherent: consistent naming, clean versioning, a spec that's pleasant to implement against. That's the editors' job — stewardship of the text, not authority over its content.
How they function
- Maintain the text
- Keep the spec readable and internally consistent, and enforce the naming conventions across every domain.
- Versioning
- Manage semantic versioning and the RFC → candidate → ratified lifecycle, and merge accepted changes into releases.
- No unilateral decisions
- Editors implement what working groups and the council accept. They don't decide spec content on their own.
What they bring
- Consistency
- One voice across many contributors, so the spec reads as a single coherent document.
- Version discipline
- Predictable releases and a clear deprecation story vendors can plan around.
Today
Editors are appointed during the founding phase. Editor seats formalize alongside the steering committee as founding members join.
Help shape the standard.
Founding partners get a seat on the council and a hand on v1 of the spec. Anyone can contribute revisions in the open today.