[Bug 17673] Define Initialization Data for implementations that choose to support the ISO Base Media File Format

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17673

--- Comment #39 from Mark Watson <watsonm@netflix.com> ---
This comment compares the idea of comprehensive additional MIME type parameters
to the alternative of a registry for "short named" for the
container/codec/keysystem/protection scheme.

Additional MIME type parameters would give us something like

video/mp4;codec=avc1.xx.xx;keysystems=<ks2>,<ks2>;protection=cenc

This could be used with isTypeSupported, or even with canPlayType, to determine
support for a specific container/codec/keysystem/protection combination and in
the needkey to indicate the combinations supported by both file and browser
(this implies the browser doing the PSSH <uuid> -> EME keysystem name mapping).

Alternatively, we could have - as pal suggested - a registry which defines
short names for the above discussions. e.g.

mp4-pr-avc-cenc = mp4 file, PlayReady, AVC, CENC
wemb-wv-vp8 = WebM files, Widevine, VP8

etc.

In this case also the UA needs to parse the PSSH boxes to identity which
keysystems are supported by the file.

The proposals are in some sense equivalent, except that with the former UAs can
introduce support for a new combination and this will 'just work' with existing
apps. For the latter the apps would need to be updated to support the new
registered string.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 28 January 2014 16:47:31 UTC