On Tue, Apr 16, 2013 at 05:56:56PM +1000, Ben Sturmfels wrote:
> Agenda:

>  - DRM in HTML 5

EME (Encrypted Media Extensions) is not a built-in DRM scheme; it's a
standard interface to DRM schemes in general. Google and the like are
using the excuse "It's not DRM" when it is just a technicality that
doesn't actually make any difference from an end-user perspective. EME
requires "content decryption modules", or CDMs (expected to typically
be a proprietary binary blob) to handle the actually decryption.

I thought I'd post a few links that I've found useful while looking
into this topic, in case anyone else wants to do some light reading
before the meet-up.

Slashdot: W3C Declares DRM In-Scope For HTML

W3C: Encrypted Media Extensions Working Draft

EEF: Defend the Open Web - Keep DRM Out of W3C Standards

Slashdot: Netflix Using HTML5 Video For ARM Chromebook
"Recently Google enabled the much controversial DRM support for HTML5
in Chrome OS to bring services like Netflix to Chromebooks using
HTML5." The technology is already in use and is being heavily pushed
by Google and Netflix (obviously) as well as apparently Apple and
Microsoft. We need to ensure Mozilla does not cave (as they did with

Slashdot: Netflix wants to go HTML5 but not without DRM

W3C: Bugzilla - #20960 EME is not limited to video, reported by Fred Andrews
This is particularly interesting (and scary) - definitely worth a look.

Defective by Design: No DRM in HTML5

W3C wiki: Digital Rights Management (also maintained by Fred Andrews)

Hacker News: Tell W3C: We don't want the Hollyweb
See pyalot2's post near the top for more insight on why this is a bad


Attachment: signature.asc
Description: Digital signature

Free-software-melb mailing list

Free Software Melbourne home page:

Reply via email to