- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 Oct 2014 15:58:45 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27053 --- Comment #3 from Mark Watson <watsonm@netflix.com> --- Sergey, I think the main issue here is that some of these aspects are not in the gift of any specification the W3C might choose to write and so the most we can do is not to preclude such outcomes in our design. For example, it seems you imagine a situation where a keysystem implementor could publish a software component that supports an open standard API and that this component could then work - at least technically - with any browser. This would be similar to the way people could publish NPAPI plugins and have those work with any browser. Putting aside the various reasons that browsers are trying to move away from this model for plugins, enabling this is a decision for browser implementors, not for W3C. The browsers would have to agree on this new open API. Nothing in the EME specification prevents them from doing so. Are you happy with a resolution that says that nothing in the EME design precludes the outcomes you seek ? Or, are there specific aspects of the current design which you think do preclude these outcomes and so should be changed ? What are they ? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 22 October 2014 15:58:47 UTC