- From: <bugzilla@jessica.w3.org>
- Date: Tue, 29 Jan 2013 19:31:47 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20760 Aaron Colwell <acolwell@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acolwell@chromium.org --- Comment #1 from Aaron Colwell <acolwell@chromium.org> --- As mentioned on the call today, I have a few concerns about adding this to the MSE spec. - This feels like scope creep. I don't want MSE to start including a variety of media related things that didn't make it into HTML 5. - Implementing MSE does not require these metrics. Some web applications that use MSE may benefit from them, but MSE is still useful without them. I'd prefer to keep the MSE spec focused on the minimal set of extensions needed to implement the media buffering & splicing functionality. - It seems like this should be pursued in the broader metrics proposal & discussion that Adrian linked to. Perhaps a metrics extension spec could be created or this could be added to HTML 5.1. In either case it seems like the old discussions should be revived. - There may be stakeholders that care about these metrics and others, but have no interest in implementing MSE. What is the spec compliance story for them? Why is it better to do this in the MSE/Media TF context instead of the standard HTML-WG one? I do think that metrics like these are useful. I just don't think the MSE spec is the right home for their definition. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 29 January 2013 19:31:49 UTC