I've written before here about the move to get the World Wide Web consortium (W3C) to cram digital rights management (DRM) into the next version of HTML, called HTML5. This week, EFF filed a formal objection with the group, setting out some of the risks to the open Web from standardizing DRM in the Web's core technical specs. Now, writing in the Guardian, W3C staffer Dr Harry Halpin makes an important, well-thought-through case for keeping DRM out of the HTML5 standard. Haplin's got an invaluable insider view of the "crisis of representation" that let a few giant companies shift the most open, most vital standards body involved with the Web into the position of standardizing ways to have your computer and browser take control away from you, and to set the stage for a ban on free and open source software in Web browsers and computers.
The most important part is what you can do to help shift the direction of the W3C back towards the open Web:
The Advisory Committee of the W3C is composed of companies as well as universities and non-profits. If your employer is a W3C member, now is the time to open the discussion internally with your management. Questions over whether DRM should be part of the HTML Working Group or part of another Working Group - or outside of W3C entirely! - are dealt with in the review of charters by Advisory Committee representatives. It's at this level that the EFF objected to EME in HTML. If your organisation is not a member, your organisation can join the W3C. W3C membership fees have been adapted to organisations large and small, for-profit and non-profit, start-ups, and for organisations in developing countries.
If you work for a W3C member, now is the time to join the HTML Working Group. The HTML Working Group are working through the technical details of Encrypted Media Extensions in the HTML Working Group Media Task Force. Also, the HTML WG has a very liberal Invited Expert policy to allow participation by those domain experts who don't work for W3C member organisations. Questions and objections that go beyond the technical content and charter are generally considered out of scope.
Questions that go beyond technically working on EME should be aimed at the Restricted Media Community Group, which anyone can join. Unlike Working Groups, W3C Community Groups provide a forum for discussion but do not themselves publish standards. Disappointingly, so far the discussion has been pretty weak, but this Community Group is monitored by many people deeply involved in the DRM debates.
Also, W3C Working Groups such as the HTML Working Group take technical comments from anyone on the entire web. Public comments can be made by ordinary users; the Working Group must formally address these comments if the comment is within the scope of the charter and done before the standard is complete. That means you can in public comment on EME or any other standard like the cryptographic primitives as pursued by the Web Cryptography Working Group, which can be used to exchange private messages between human rights activists as well as be part of Netflix's plan to switch to HTML5.
I write books. My latest is a YA science fiction novel called Homeland (it's the sequel to Little Brother). More books: Rapture of the Nerds (a novel, with Charlie Stross); With a Little Help (short stories); and The Great Big Beautiful Tomorrow (novella and nonfic). I speak all over the place and I tweet and tumble, too.