W3C home > Mailing lists > Public > public-html-admin@w3.org > January 2013

Re: CfC: to publish Encrypted Media Extensions specification as a First Public Working Draft (FPWD)

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 25 Jan 2013 17:12:52 +1300
Message-ID: <CAOp6jLbe+YaznDHsK37aTPvQ6a3zS0z8Rxd_39cqRPi89=4rUw@mail.gmail.com>
To: Mark Watson <watsonm@netflix.com>
Cc: Paul Cotton <Paul.Cotton@microsoft.com>, "public-html-admin@w3.org" <public-html-admin@w3.org>, "David Dorwin <ddorwin@google.com> (ddorwin@google.com)" <ddorwin@google.com>, Adrian Bateman <adrianba@microsoft.com>
On Fri, Jan 25, 2013 at 11:48 AM, Mark Watson <watsonm@netflix.com> wrote:

> I'm still sympathetic to that goal, specifically the idea that where an OS
> or other platform supports a DRM framework with a public API, then there
> should be a public specification allowing people to fill the gap between
> the EME API and that platform API. And I think that where there is a DRM
> framework built in to an OS or other platform, then the APIs to that should
> be public.


But I am not sure what we can do in the W3C process or specification to
> cause or even require that.

How about making the EME spec require that CDMs used with EME be registered
in a central registry, and then making such registration conditional on the
above requirements be met?

Jesus called them together and said, “You know that the rulers of the
Gentiles lord it over them, and their high officials exercise authority
over them. Not so with you. Instead, whoever wants to become great among
you must be your servant, and whoever wants to be first must be your
slave — just
as the Son of Man did not come to be served, but to serve, and to give his
life as a ransom for many.” [Matthew 20:25-28]
Received on Friday, 25 January 2013 04:13:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:57:21 UTC