26811 2014-09-15 20:24:43 +0000 Separate definitions of Initialization Data Types from Stream Format parsing 2015-10-19 23:47:29 +0000 1 1 1 Unclassified HTML WG Encrypted Media Extensions unspecified All All RESOLVED MOVED to_be_implemented editorial P4 normal CR 26573 26738 1 ddorwin adrianba b.lund mike public-html-media public-html-bugzilla oldest_to_newest 111542 0 ddorwin 2014-09-15 20:24:43 +0000 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 112054 1 ddorwin 2014-09-24 00:24:20 +0000 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. 114955 2 ddorwin 2014-11-14 23:38:41 +0000 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 ... 117464 3 b.lund 2015-01-23 21:28:13 +0000 (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 123790 4 ddorwin 2015-10-19 23:47:29 +0000 Migrated to https://github.com/w3c/encrypted-media/issues/105.