This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
On the introduction section, just above the figure, there is the following text: "This is just an example flow and is not intended to show all possible communication or uses." I think this is too much freedom for EME implementors. The document should keep record of all possible uses.
While I personally agree that more restrictions should be placed on EME implementations, documenting *all* possible use cases is nearly impossible. There is always the possibility of a new use case appearing down the road for which EME would be a perfect fit, and there's no reason to disallow it just because we didn't foresee its usefulness today.
That is precisely what I fear. That implementors will find new ways to control the user. I think we should give them just enough control as to protect the content and no more than that. Just a little. EME is intended to protect content, not to control the user. I agree that documenting *all* possible cases is next to impossible, but we should document some.
Discussed in the 10/15 telcon: http://www.w3.org/2013/10/15-html-media-minutes.html Agreed to use the following text: "This diagram shows an example flow: other combinations of API calls and events are possible." Note that this section is non-normative.
Resolved -> https://dvcs.w3.org/hg/html-media/rev/88e691c3a15e