RE: Please, reject the EME proposal

>Strikes me, sir, that this is the appropriate forum, discussing new forms of media restrictions and whether or not they should be built into the HTML5 specification.. Please demonstrate explicitly how it is not.

Please see my reply at [1] and Sam's reply at [2].

In addition the Media TF email list was originally created to discuss the EME and MSE specifications not media in general.  See [3].

/paulc

[1] http://lists.w3.org/Archives/Public/public-html-media/2013May/0061.html
[2] http://lists.w3.org/Archives/Public/public-html-media/2013May/0062.html
[3] http://lists.w3.org/Archives/Public/public-html/2012May/0092.html

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

From: B. Ross Ashley [mailto:brashley46@tfnet.ca]
Sent: Monday, May 13, 2013 12:38 PM
To: public-html-media@w3.org
Subject: Re: Please, reject the EME proposal

On 13-05-13 10:49 AM, Paul Cotton wrote:
Please take this discussion to a more appropriate forum such as http://www.w3.org/community/restrictedmedia/

/paulc
HTML WG co-chair

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

From: Pascual Conesa [mailto:pasconguero@gmail.com]
Sent: Friday, May 10, 2013 5:41 PM
To: public-html-media@w3.org<mailto:public-html-media@w3.org>
Subject: Please, reject the EME proposal


The W3C's official vision statement also "recognizes that trust is a social phenomenon, but technology design can foster trust and confidence" and asserts that the W3C's mission includes "building trust on a global scale." A specification designed to help companies run secret code on users' computers to restrict what they do on the Web would severely undermine that trust. The only trust being built here is between media companies calling for DRM and their powerful allies promoting EME in the W3C.
Strikes me, sir, that this is the appropriate forum, discussing new forms of media restrictions and whether or not they should be built into the HTML5 specification.. Please demonstrate explicitly how it is not.



--

B. Ross Ashley

registered Linux user 548111