- From: <bugzilla@jessica.w3.org>
- Date: Sat, 23 Feb 2013 13:04:34 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20964 --- Comment #18 from Fred Andrews <fredandw@live.com> --- (In reply to comment #16) > (In reply to comment #13) > > (In reply to comment #12) ... > > You need to clarify the scope of the CDM and the architecture you > > propose so that it can be reviewed. I do not believe any progress > > can be made resolving these bugs without such clarification. > > It's not the object this specification to define precisely what CDMs can and > cannot do or precisely what the interface between CDM and UA should be. You > seem to think that this is something we should define. I'd suggest opening > another bug "EME should define precisely the functions performed by CDMs" > and explain why you think that. > > The kind of review you seem to wish to perform here should be done by UA > implementors when they consider whether to integrate a given CDM. I have no > problem including text that highlights things that they should consider but > ultimately it is up to them. There are already a range of open bugs that require clarification to be able to make progress. For example, enough detail to be able to assess the security and privacy implications, and enough detail to be able to decide if 'strong DRM' is possible on open source stacks. The community also needs enough information to decide if this specification should even advance. Detailing the scope in more detail would help. For example, noting that 'strong DRM' will not be possible on open source stacks, etc would help in deciding if EME is an appropriate 'open' standard. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 23 February 2013 13:04:40 UTC