Status of This Document
This section describes the status of this document at the time of its publication.
Other documents may supersede this document. A list of current W3C publications and the
latest revision of this technical report can be found in the W3C technical reports index at
http://www.w3.org/TR/.
The Working Group maintains a list of all bug reports that the editors have not yet tried to address.
Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should join the mailing list mentioned below and take part in the discussions.
This document was published by the HTML Working Group as an Editor's Draft.
If you wish to make comments regarding this document, please send them to
public-html-media@w3.org
(subscribe,
archives).
All comments are welcome.
Publication as an Editor's Draft does not imply endorsement by the W3C
Membership. 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.
This document was produced by a group operating under the
5 February 2004 W3C Patent
Policy.
W3C maintains a public list of any patent
disclosures
made in connection with the deliverables of the group; that page also includes
instructions for disclosing a patent. An individual who has actual knowledge of a patent
which the individual believes contains
Essential
Claim(s) must disclose the information in accordance with
section
6 of the W3C Patent Policy.
This document is governed by the 1 August 2014 W3C Process Document.
1. Purpose
This registry is intended to enhance interoperability among implementations and users of encrypted media streams with the
Encrypted Media Extensions (EME) specification. In particular, this registry provides the means (1) to identify
and avoid collisions among initialization data 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 Initialization Data Type strings and encryption format specifications. The encryption format specifications describe the
structure and semantics of initialization data.
This registry is not intended to include any information on whether a byte 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 byte stream format.
3. Registration Entry Requirements
- Each entry must include a unique Initialization Data Type string. 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 publically 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).
- Candidate entries must be announced on public-html-media@w3.org(subscribe,
archives) so they can be discussed and evaluated for compliance before being added to the
registry.