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

My sympathies lie with Tab, but assuming this spec proceeds in some form
I'd like to make my own objection --- which I think can actually be
resolved without tossing out the spec or its goals:

In the sub-thread starting at
http://lists.w3.org/Archives/Public/public-html/2012Apr/0059.html, I argued
that instead of treating CDMs as an unbounded set of black boxes, for the
sake of interoperability each supported CDM should be registered and
documentation/specification provided to maximise interoperability of UAs
and content providers with CDMs (possibly by reference to non-W3C specs).
For example if a CDM is based on a platform DRM framework with a public
API, the behavior of the CDM should be specified in terms of that public
API. At least Mark Watson seemed broadly sympathetic to this goal, so I'm
disappointed to see that the current draft has nothing in this direction
whatsoever. So I object to publication of the draft on the same grounds
that I objected last year.

Rob
-- 
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 Wednesday, 23 January 2013 10:50:02 UTC