The ISOBMFF bytestream specification 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).
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 section in the bytestream specification, and added to the mapping in the ISOBMFF entry of the 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?
The ISOBMFF bytestream specification references
audio/mp4
andvideo/mp4
mime types, but notapplication/mp4
which is required for timed text support (and any other non audio/video content according to RFC4337).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 section in the bytestream specification, and added to the mapping in the ISOBMFF entry of the 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?