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/.
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 Media Working Group as
an Editor's Draft.
Publication as an Editor's 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 work in progress.
This document was produced by a group
operating under the
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 registry is intended to enhance interoperability among implementations and users of SourceBuffer objects described in the
Media Source Extensions™ specification. In particular, this registry provides the means (1) to identify
and avoid MIME-type collisions among byte stream formats, and (2) to disclose information about byte stream formats accepted by MSE
implementations to promote interoperability.
2. Organization
The registry maintains a mapping between MIME-type/subtype pairs and byte stream format specifications. The byte stream format specifications describe the
structure and semantics of byte streams accepted by SourceBuffer objects
created with the associated MIME-type/subtype pair.
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 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 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. The Media Working Group may seek expertise from outside the Working Group as part of its evaluation, e.g., from the codec specification editors or relevant standards group. If the Media Working Group reaches 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.
If a registration fails to satisfy a mandatory requirement specified above, then it MAY be removed from the registry (without prejudice). Existing entries cannot be deleted or deprecated otherwise.
Existing entries MAY be changed after being published through the same process as candidate entries. Possible changes include modification of the link to the publically available specification.
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY, MUST, and SHOULD in this document
are to be interpreted as described in
BCP 14
[RFC2119] [RFC8174]
when, and only when, they appear in all capitals, as shown here.