- From: David Evans via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Sep 2017 09:07:11 +0000
- To: public-html-media@w3.org
bbcrddave has just created a new issue for https://github.com/w3c/media-source: == Add application/mp4 mimetype to ISOBMFF bytestream specification == The [ISOBMFF bytestream specification](https://www.w3.org/TR/mse-byte-stream-format-isobmff/) references `audio/mp4` and `video/mp4` mime types, but not `application/mp4` which is required for timed text support (and any other non audio/video content according to [RFC4337](https://tools.ietf.org/html/rfc4337#section-3.3)). I believe that subtitles encapsulated as described by ISO/IEC 14496-30, for example, already meet all the requirement in the bytestream specification, so it would be great if `application/mp4` could be called out explicitly in [MIME Parameters](https://www.w3.org/TR/mse-byte-stream-format-isobmff/#mime-parameters) section in the bytestream specification, and added to the mapping in the ISOBMFF entry of the [Registry](https://www.w3.org/TR/mse-byte-stream-format-registry/#registry) section of the Format Registry. CMAF and DASH-IF, for example, call out this as the relevant mime type for timed text, so I believe this change should be in scope. Am I right in thinking that changes can be made to the registry and bytestream specifications outside of charter as long as there is consensus? Please view or discuss this issue at https://github.com/w3c/media-source/issues/197 using your GitHub account
Received on Tuesday, 5 September 2017 09:07:10 UTC