This specification defines the byte stream formats for use with the Media Source Extensions™ specification [MEDIA-SOURCE].

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 https://www.w3.org/TR/.

The working group maintains a list of all bug reports that the editors have not yet tried to address; there may also be open bugs in the previous bug tracker.

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 Media Extensions Working Group as a Working Group Note. 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 a Working Group Note 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 September 2015 W3C Process Document.

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 generate timestamps flag value that MUST be used by SourceBuffer when handling the byte stream format.
  3. 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).
  4. Each entry MUST comply with all requirements outlined in the byte stream formats section of the Media Source Extensions™ specification.
  5. 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) Generate Timestamps Flag
WebM Byte Stream Format [MSE-FORMAT-WEBM] false
ISO BMFF Byte Stream Format [MSE-FORMAT-ISOBMFF] false
MPEG-2 Transport Streams Byte Stream Format [MSE-FORMAT-MP2T] false
MPEG Audio Byte Stream Format [MSE-FORMAT-MPEG-AUDIO] true

5. Conformance

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 are to be interpreted as described in [RFC2119].

A. References

A.1 Normative references

Matthew Wolenetz; Jerry Smith; Mark Watson; Aaron Colwell; Adrian Bateman. W3C. Media Source Extensions. 5 July 2016. W3C Candidate Recommendation. URL: https://www.w3.org/TR/media-source/
Matthew Wolenetz; Jerry Smith; Mark Watson; Aaron Colwell; Adrian Bateman. W3C. ISO BMFF Byte Stream Format. URL: https://www.w3.org/TR/mse-byte-stream-format-isobmff/
Matthew Wolenetz; Jerry Smith; Mark Watson; Aaron Colwell; Adrian Bateman. W3C. MPEG-2 Transport Streams Byte Stream Format. URL: https://www.w3.org/TR/mse-byte-stream-format-mp2t/
Dale Curtis; Matthew Wolenetz; Aaron Colwell. W3C. MPEG Audio Byte Stream Format. URL: https://www.w3.org/TR/mse-byte-stream-format-mpeg-audio/
Matthew Wolenetz; Jerry Smith; Aaron Colwell. W3C. WebM Byte Stream Format. URL: https://www.w3.org/TR/mse-byte-stream-format-webm/
S. Bradner. IETF. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119