W3C

Media Source Extensions Byte Stream Format Registry

W3C Editor's Draft 04 November 2013

This version:
http://dvcs.w3.org/hg/html-media/raw-file/default/media-source/byte-stream-format-registry.html
Latest published version:
http://www.w3.org/TR//
Latest editor's draft:
http://dvcs.w3.org/hg/html-media/raw-file/default/media-source/byte-stream-format-registry.html
Editor:
Aaron Colwell, Google Inc.

1. Purpose

This registry is intended to enhance interoperability among implementations and users of SourceBuffer objects described in the Media Source Extensions(MSE) 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

  1. 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.
  2. 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).
  3. Each entry must comply with all requirements outlined in the byte stream formats section of the Media Source Extensions specification.
  4. 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.

If a registration fails to satisfy a mandatory requirement specified above, then it may be removed from the registry (without prejudice).

4. Registry

MIME type/subtype Public Specification(s)
audio/webm
video/webm
WebM Byte Stream Format
audio/mp4
video/mp4
ISO BMFF Byte Stream Format
audio/mp2t
video/mp2t
MPEG-2 Transport Streams Byte Stream Format
See a problem? Select text and .