- From: <bugzilla@jessica.w3.org>
- Date: Mon, 06 Apr 2015 15:22:16 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27509 --- Comment #4 from Bob Lund <b.lund@cablelabs.com> --- (In reply to Silvia Pfeiffer from comment #3) > Bob, would you be ok with reorganising the spec a bit? > > I'm concretely thinking about creating two main sections, > the first being "Media File Fromats" and containing: > * MPEG-2 Transport Streams > * MPEG-4 ISOBMFF > * WebM > * Ogg > > and the second being "Manifest formats for HTTP Adaptive Streaming" and > containing: > * DASH > * HLS > > According to > https://developer.mozilla.org/en-US/Apps/Build/Audio_and_video_delivery/ > Live_streaming_web_audio_and_video , both HLS and DASH have some native > browser support, so it makes sense to limit to these two formats. Silvia, I think this is a good idea. We need to make sure that the relationship between the media file format and the manifest format is correctly reflected. I don't know about HLS but in DASH tracks and associated attributes are first created by information in the initialization segment of the media file, then from MPD information. Perhaps we should also reorganize the spec so that there are separate sections for inband track data format, e.g. WebVTT, TTML, CEA 608/708, and for cue formats. I find that these are redundantly described in the current spec. I would be happy to work with you on this. Last, can this reorganization wait until I update the spec to resolve bug 27306[1]? I can do this by my eod on Tue 4/7. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=27306 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 6 April 2015 15:22:18 UTC