Capability Matrix - Taking different API, codec and platform combinations into account

[dsilhavy]

Description

The current OTT matrix outlines support for various capabilities such as streaming formats, supported codecs and DRM support. While this can be interpreted as one common denominator, there are multiple dimensions to such a capability matrix.

As an example, a platform might support Widevine L1 for AVC but not for HEVC. Or only Widevine L1 for HEVC but not Widevine L3. Another example are differences in terms of codec support for browser based implementations and native applications. For instance, an AC-3 codec might be supported natively but not on MSE/EME browser based implementations.

Suggested Solutions / Discussion Items

I suggest discussing how we want to account for such cases, as described above. Do we provide a general overview of what is possible on a platform, not tailored to a specific implementation or a specific API stack? Or do we want to create multiple dimensions to the capabilities matrix in which API/codec/format/DRM information are directly connected to each other?