[Bug 18601] Contradictory requirements for initialization segments

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

Aaron Colwell <acolwell@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |acolwell@chromium.org,
                   |                            |watsonm@netflix.com
         AssignedTo|adrianba@microsoft.com      |acolwell@chromium.org

--- Comment #3 from Aaron Colwell <acolwell@chromium.org> 2012-08-17 20:41:37 UTC ---
(In reply to comment #0)
> The spec seems confused about whether or not initialization segments are
> mandatory or not.
> 
> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#source-buffer-basic-append
> 
> "The first segment appended MUST be an initialization segment."

I could soften this to the following:
"If the format defines an initialization segment format, the first segment
appended must be an initialization segment."

> 
> (IMHO, this entire section should be non-normative, but currently it isn't.)
> 
> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#dom-append
> 
> A bunch of steps here are triggered by the first initialization segment.
> 
> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#byte-stream-formats
> 
> "A byte stream format specification MAY define initialization segments and MUST
> define media segments."

I'm CC'ing Mark Watson because I believe he is the one that wanted to make
initialization segments optional. All the formats we currently support have
initialization segments so I'd be fine with dropping the "init segments are
optional" text until we have a more concrete idea of how a format w/o init
segments would work.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 17 August 2012 20:41:39 UTC