Draft 1.0, proposed
Governance
ARV is maintained by AgentCDN with open contributions. The spec is a draft, and it says "proposed" until an outside implementation passes the validator.
Maintainer #
AgentCDN maintains the spec, the schemas and the validator. Contact: team@agentreadyvideo.org.
Licenses #
| What | License |
|---|---|
| Spec text | Contributed to the W3C Agent-Ready Video Community Group under the W3C CLA at launch. Until launch, contributions are accepted under the same CLA terms. |
| Code: schemas, validator, adapters, reference producer | Apache-2.0 |
| Docs and explanatory material | CC-BY-4.0 |
At launch the group governs the evolution of the spec and publishes it as a Community Group Report. AgentCDN remains one implementer and the initial editor, with no special rights over the text. Use of the name "Agent-Ready Video", the short form "ARV" and the badge follows a short conformance mark policy: you may say your site conforms at a level only when a current validator report shows it.
How a feature becomes required #
A feature becomes required only after two independent implementations pass the validator for it. Until then it is optional, even if the spec defines it. Two implementations are independent when different organizations build them from the spec text, without shared code for that feature.
How to propose a change #
- Open an issue with the Proposal template. Say what problem you have, what you propose, and what it breaks.
- Discuss in the issue. Anyone may comment. The maintainer labels the issue
accepted,needs-workordeclined, with a reason. - Open a pull request for an accepted proposal. Change the spec text, schemas and examples together.
npm testmust pass. - Merge. The maintainer merges and adds a
CHANGELOG.mdentry.
Rules for changes:
- A change that breaks a valid 1.0 document needs a new major version. Within 1.x, changes are additive: new optional fields, new enum values that consumers may ignore, clearer text.
- Published schema URLs are immutable once 1.0 is final. Until then they may change, and every change is listed in the changelog.
- Every normative change comes with an example that validates.
Status and roadmap #
- Now: Draft 1.0, proposed, published 2026-09-23 at /spec/1.0. Spec text, JSON Schemas at /schema/1.0/, example objects, the quick start and llms.txt are live. Every change is in the changelog.
- Next: the validator and badge, and three starters.
- Announced for support: W3C has announced the Agent-Ready Video Community Group proposal. It launches once five people support it. Support the proposal at W3C. It is not formed yet. A Community Group can publish reports, but those are not W3C Recommendations. Charter (draft), not yet adopted.
- Submitted: provisional registration of the
arv:URI scheme with IANA, requested 2026-09-24. - Filed: a schema.org guidance issue on Clip ids for video moments, schemaorg/schemaorg#4923.
- Not claimed: no implementations yet (see implementations). The draft stays "proposed" until an outside one passes the validator.
Contribute #
GitHub
Spec text, schemas and examples are public. File issues, suggest wording, or send a pull request.
W3C Community Group
Support the proposal at W3C. A free group where anyone with a W3C account can join, comment and back the work. It is proposed and not yet formed. Email us to be told when it opens.
Tell us what you publish or build and what you need from the spec.
How to cite #
Agent-Ready Video (ARV) Specification, Draft 1.0 (proposed). AgentCDN, 23 September 2026. https://agentreadyvideo.org/spec/1.0
More answers on scope, rights and adoption: FAQ.