This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently, the Encrypted Media Extensions Stream Format and Initialization Data Format Registry [1] is organized such that each Initialization Data Type has its own page, which covers both the Initialization Data format and - where applicable - how to parse the associated stream (i.e. container). However: * The Initialization Data Type and stream format are used by two different parts of implementations: - The user agent uses the stream format to extract the initialization data, but does not necessarily care about its format. - The CDM only needs to know how to parse the Initialization Data format and does not need to parse the stream/container. - Note: A packager, which is not covered by the spec, needs to know both. * Initialization Data Types do not necessarily have an associated container (e.g. "keyids") * An Initialization Data Type may apply to more than one stream/container format (bug 26738). We should have a table and page for Initialization Data Types and separate pages for stream/container parsing information. Maybe we can use the MIME type as the index for a table pointing to the latter pages. [1] https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/initdata-format-registry.html
Section 3 of the webm and cenc pages is currently called "Initialization Data and Events," but events are not discussed. We can probably drop "and Events" as part of this change. (Those entire sections will probably become a new page.
When implementing this, we should move the registries to their own directories. For example: encrypted-media\ ... registry\ stream-format\ bmff.html webm.thml ... initdata-format\ cenc.html webm.thml ...
(In reply to David Dorwin from comment #2) > When implementing this, we should move the registries to their own > directories. For example: > > encrypted-media\ > ... > registry\ > stream-format\ > bmff.html > webm.thml > ... > initdata-format\ > cenc.html > webm.thml > ... I've taken a stab at separating the cenc-format-respec.html into an cenc init data spec[1] and a cenc in bmff stream format spec[2]. [1] references [2]. [1] http://rawgit.com/boblund/encrypted-media/bug26811/cenc-init-format-respec.html [2] http://rawgit.com/boblund/encrypted-media/bug26811/bmff-format-respec.html
Migrated to https://github.com/w3c/encrypted-media/issues/105.