- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Mar 2015 22:09:33 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27509 --- Comment #2 from JP Abello <Jp.abello@nielsen.com> --- Hello Silvia, Bob, Cyril, Eric and Giuseppe, I hope you are all doing well. Did you see the Jan 29 announcement about Microsoft adding native support for HLS and DASH in Internet Explorer on Windows 10? http://blogs.msdn.com/b/ie/archive/2015/01/29/simplified-adaptive-video-streaming-announcing-support-for-hls-and-dash-in-windows-10.aspx In the light of this new development, it might make more sense now to add HLS along with DASH in http://dev.w3.org/html5/html-sourcing-inband-tracks Silvia had also proposed back in November to move DASH and HLS into their own dedicated section in the document: > On 11/2/14, 2:45 AM, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com> wrote: > > For the record: I do have some reservations about adding DASH and HLS > support, since browsers do not typically support these formats > natively. Actually, HLS is supported in Safari, so it has some excuse, > but DASH is only supported via Media Source Extensions. I have been > worried about that a bit. > > I think these facts probably need to be explained better in the > document. This is particularly important, since different target > audiences are addressed with the different formats: DASH and HLS > address Web Developers (+Safari), MPEG-4, WebM and Ogg address Browser > developers, and MPEG-2 addresses Web-enabled set-top box vendors > (these are still UA devs). So, DASH and HLS are bascially in a league > of their own and should probably be moved to an appendix or so. > > Silvia. Thanks, JP -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 3 March 2015 22:09:35 UTC