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 standards and drafts index.
Publication as a Registry Draft does not
imply endorsement by W3C and 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 a work in progress.
The
W3C Patent
Policy
does not carry any licensing requirements or commitments on this
document.
This registry is intended to enhance interoperability among implementations and users of encrypted media streams with the
Encrypted Media Extensions (EME) specification [ENCRYPTED-MEDIA]. In particular, this registry provides the means (1) to identify
and avoid collisions among content type strings, and (2) to disclose information about encrypted data formats accepted by EME
implementations to promote interoperability.
2. Organization
The registry maintains a mapping between content type strings and encryption format specifications, which describe the structure, semantics, and processing of the formats.
The strings are those used for the media type/subtype pairs in contentType values provided to Encrypted Media Extensions [ENCRYPTED-MEDIA] APIs.
This registry is not intended to include any information on whether a stream format is encumbered by intellectual property claims. Implementors and users
are advised to seek appropriate legal counsel in this matter if they intend to implement or use a specific stream format.
3. Registration Entry Requirements
Each entry must include a unique MIME-type/subtype pair. If the byte stream format is derived-from an existing file format, then it should use the MIME-type/subtype pairs typically used for the file format.
Each entry must include a link that references a publicly available specification.
It is recommended that such a specification be made available without cost (other than reasonable shipping and handling if not available by online means).
Per the Encrypted Media Extensions specification, the media container for a stream format must not be encrypted.
Per the Encrypted Media Extensions specification, entries must be fully specified and support "common encryption" such that the content can decrypted in a fully specified and compatible way when a key or keys are provided.
Candidate entries must be announced by filing an issue in the
Encrypted Media Extensions GitHub issue tracker
so they can be discussed and evaluated for compliance before being added to
the registry.
If the Media Working Group reaches consensus to accept the candidate,
a pull request should be drafted
(either by the registry editors or by the party requesting the candidate registration)
to register the candidate.
The registry editors will review and merge the pull request.