W3C home > Mailing lists > Public > public-html@w3.org > March 2012

Re: Encrypted Media proposal (was RE: ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals)

From: Mark Watson <watsonm@netflix.com>
Date: Fri, 2 Mar 2012 23:50:09 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: Boris Zbarsky <bzbarsky@mit.edu>, "<public-html@w3.org>" <public-html@w3.org>
Message-ID: <8E6D5E52-7465-4DF9-A330-47F73FBC7F3C@netflix.com>

On Mar 2, 2012, at 3:31 PM, Tab Atkins Jr. wrote:

> On Fri, Mar 2, 2012 at 3:21 PM, Mark Watson <watsonm@netflix.com> wrote:
>> On Mar 2, 2012, at 2:42 PM, Tab Atkins Jr. wrote:
>>>  Having
>>> service-lock-in based on my hardware is just so brain-breakingly bad I
>>> can't imagine how this even crossed your fingers without them cramping
>>> from the blasphemy. :/
>>> 
>> 
>> Either you mis-understood me, or we have remarkably different views of the world ;-)
>> 
>> I'm not talking about any kind of lock-in, just about products which ship with some apps pre-installed. I hope that soon it will be possible for users to install apps on these products, including web apps. And I hope that those web apps will be able to stream all kinds of video. That's exactly why we need the standardization we propose.
> 
> You said "[customers] don't expect to be able to watch Netflix on the
> one without the badge".  How should I have interpreted that?

Ok, what I meant was that customers should not expect to buy a TV that does not support Netflix, plug it into the Internet and *without any other device* access our service. People intuitively understand that the TV needs some kind of 'Netflix-stuff' inside it to be able to access Netflix on the TV alone.

A customer can, of course, get *another* device that supports our service, plug that into the TV, and watch on the TV.

I was pointing out a qualitative difference from the expectation of a customer who buys an mp3 from vendor X and expects it work on any mp3 player, whether or not the player contains any 'X-stuff'

...Mark

> 
> ~TJ
> 
Received on Friday, 2 March 2012 23:50:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:46 GMT