[...] the W3C cannot prevent companies from grafting DRM onto HTML. They do this through nonfree plug-ins such as Flash, and with nonfree Javascript code, thus showing that we need control over the Javascript code we run and over the C code we run. However, where the W3C stands is tremendously important for the battle to eliminate DRM. On a practical level, standardizing DRM would make it more convenient, in a very shallow sense. This could influence people who think only of short-term convenience to think of DRM as acceptable, which could in turn encourage more sites to use DRM. On the political level, making room for DRM in the specifications of the World Wide Web would constitute an endorsement in principle of DRM by the W3C. Standardization by the W3C could facilitate DRM that is harder for users to break than DRM implemented in Javascript code. If the DRM is implemented in the operating system, this could result in distribution of works that can't be played at all on a free operating system such as GNU/Linux.
The acknowledgement put up last week, linked from the home page by a tiny link, was deemed to be "non-compliant" with the order that the court had made in October. The court has now ordered it to correct the statement – and the judges, Lord Justice Longmore, Lord Justice Kitchin and Sir Robin Jacob, indicated that they were not pleased with Apple's failure to put a simpler statement on the site.
It appears the main objection is the statement is on a separate page and only linked from the hompage — and that the statement is buried in marketing blurb, and also put next to references to a case Apple won.
Machines have less problems. I'd like to be a machine. -- Andy Warhol