[Bug 20944] EME should do more to encourage/ensure CDM-level interop

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944

--- Comment #26 from Michael[tm] Smith <mike@w3.org> ---
(In reply to comment #22)
> > I will draft a proposed registry along the lines I propose. If you feel the
> > urge and think you can gain sufficient support for your proposal, then you
> > are free to draft an alternative form.
> 
> http://www.w3.org/html/wg/wiki/KeySystemRegistry

The phrase "a public available specification (PAS) which the registrant
believes satisfies some standard of openness" pretty obviously places no real
requirement on registrants at all. And "Each entry listed as a Non-Open Key
System is encouraged to include a link that references some form of publicly
available information about the Key System" does even less.

(In reply to comment #23)
> I was hoping we would be able to do a little more here, especially for the
> case of DRMs supported by the operating system.
> 
> Specifically, if a DRM is included in the OS, can be accessed through public
> APIs and can be used to implement EME in a browser then the specification of
> how to do this should be public. The registry should encourage or require
> this.

I agree that the registry could and should require that any DRM system listed
in the registry must make available a clear specification about how it can be
used to implement EME in a browser. Otherwise, there's really no point in
having a registry at all.

> Otherwise we have an obvious interoperability problem where multiple
> browsers use public OS APIs to implement a CDM, but they do so in different,
> incompatible, ways.
> 
> Potentially, we could go further and say that when a CDM is built using
> platform APIs then it should be a condition of registration that these APIs
> are public, rather than secret APIs only available to a single browser.

I agree it should be a requirement of registration that the APIs are public and
not only available to a single browser. Because there would otherwise really no
point in registering them at all.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 16 August 2013 08:40:29 UTC