W3C home > Mailing lists > Public > public-html-media@w3.org > April 2013

Re: Chromebook DRM specification

From: Glenn Adams <glenn@skynav.com>
Date: Tue, 16 Apr 2013 10:23:30 -0600
Message-ID: <CACQ=j+duj5BMeE5sVMVtENrSoOJF-F0Ys8LPtGXPxCjnEwvpfg@mail.gmail.com>
To: Florian Bösch <pyalot@gmail.com>
Cc: Mark Watson <watsonm@netflix.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "Mays, David" <David_Mays@comcast.com>, David Dorwin <ddorwin@google.com>, "<public-html-media@w3.org>" <public-html-media@w3.org>, "Philippe Le Hegaret (plh@w3.org)" <plh@w3.org>, "Michael(tm) Smith (mike@w3.org)" <mike@w3.org>
On Tue, Apr 16, 2013 at 10:06 AM, Florian Bösch <pyalot@gmail.com> wrote:

> On Tue, Apr 16, 2013 at 6:02 PM, Mark Watson <watsonm@netflix.com> wrote:
>
>> I am actually saying exactly the opposite. I should have said "You can
>> certainly implement EME and a CDM ..." above.
>>
>
> I disagree with that assessment on three counts:
>
> 1) I cannot implement Widevine to deliver content to Chromebooks, so this
> is no path to satisfy the success criteria set forth by the HTML-WG charter
> 2) I cannot implement a CDM and have Chromebooks support it, so this is
> also no path to satisfy the success criteria.
> 3) I cannot implement a CDM compatible with the HTML-WG charter that would
> be deemed useful by the content industry, so that is also no path to
> satisfy the success criteria.
>

If any of these are true, it is because you have CHOSEN to not implement.
It is is not because it is not possible. Others will implement. There is no
requirement for the W3C (or any other specification/standards development
organization I'm aware of) to limit its work to specifications that
everyone both can and will choose to implement or use.

Which means there is no path to an implementation of HTML-DRM in its
> entirety that would be both feasible and compatible with the HTML-WG
> charter.
>

Oh? Can you cite language from the charter that makes this work infeasible
or incompatible?
Received on Tuesday, 16 April 2013 16:24:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:35 UTC