This registry is intended to enhance interoperability among
implementations and users of [WEBCODECS]. In particular, this
registry provides the means to identify and avoid collisions among codec
strings and provides a mechanism to define codec-specific members of [WEBCODECS] codec configuration dictionaries.
This registry is not intended to include any information on whether a codec
format is encumbered by intellectual property claims. Implementers and
users are advised to seek appropriate legal counsel in this matter if they
intend to implement or use a specific codec format. Implementers of
WebCodecs are not required to support any particular codec nor registry
entry.
This registry is non-normative.
Status of this document
This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
Feedback and comments on this specification are welcome. GitHub Issues are preferred for discussion on this specification. Alternatively, you can send comments to the Media Working Group’s mailing-list, public-media-wg@w3.org (archives).
This draft highlights some of the pending issues that are still to be discussed in the working group.
No decision has been taken on the outcome of these issues including whether they are valid.
Group Draft Notes are not endorsed
by W3C nor its Members.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time.
It is inappropriate to cite this document as other than work in progress.
The W3C Patent Policy does not carry any licensing requirements or commitments on this document.
This registry maintains a mapping between codec strings and registration
specifications as described below.
2. Registration Entry Requirements
Each entry must include a unique codec string, a common name string, and a
link to a public specification.
The codec string must be crafted as follows:
If the codec string contains a fixed prefix with variable suffix values,
the suffix must be represented by an asterisk and the registration’s
public specification must describe how to fully qualify the variable
portion of the string.
Otherwise, if the codec is recognized by multiple strings, a single
preferred string should be listed and the registration’s specification
must list the other allowed strings.
Otherwise, the codec is identified by a simple fixed string.
Each registration’s specification must include a sequence of sections
describing:
Where applicable, a registration specification may include a section
describing extensions to VideoEncoderConfig or AudioEncoderConfig dictionaries.
Candidate entries must be announced by filing an issue in the WebCodecs GitHub issue tracker so they can be discussed and evaluated for compliance before being added to
the registry. If registry editors reach consensus to accept the candidate,
a pull request should be drafted (either by editors or by the party
requesting the candidate registration) to register the candidate. The
registry editors will review and merge the pull request.