5 ms·
The W3C could have told Netflix et al to get the heck out of the browser, but the outcome of that would have been a different DRM mechanism in each of the main
by onion2k 13y ago
The W3C could have told Netflix et al to get the heck out of the browser, but the outcome of that would have been a different DRM mechanism in each of the main browsers. There's enough money in digital content distribution that browser developers will implement it regardless of what the W3C want. So the W3C had to decide between a standard they have an element of control over that's widely used, or several different DRM mechanisms that they have no input in to. The choice was not between DRM or no DRM. It never will be.
The W3C maintain web standards. They do not maintain what browsers can and can't do.
- dTal 13y agoA different DRM mechanism in each of the main browsers is fine by me, because none of them would ever gain traction in that scenario. It takes everyone getting together and agreeing on one to achieve the critical mass required to make DRM happen. What is the use of having "an element of control" over exactly how you'll get screwed over?
- onion2k 13y agoDRM gains traction from people buying services that use it. It's that simple. If there's enough demand for a Netflix-like service in an ecosystem where only one browser does DRM, a company will spring up that provides such a service only for users of that one browser, even if it's a relatively small market. But, as it happens, watching digital content over the internet is a huge market, so every browser is going to have DRM built-in whether there's a standard or not. The market is big enough to support many different DRM mechanisms (we can tell that by the fact it already does). Consequently we have to accept that DRM is going to exist whether we (the technical "elite" who understand the issues) want it or not. If we want an internet where DRM isn't entirely pervasive, where video will work without being DRM'd, where it doesn't spill out in to things like only running "signed HTML" or something horrible, we will need a decent standard that people on both sides of the debate agreed to on a pragmatic level if not an ideological one. I believe that a W3C sanctioned DRM is a hell of a lot saner than Microsoft, Google and Apple coming up with their own systems.
- hsivonen 13y agoWhat's on track to becoming W3C-sanctioned (EME) is about Microsoft, Google, Apple and now Adobe having their own systems.
- pornel 13y ago> outcome of that would have been a different DRM mechanism in each of the main browsers. That's a common misconception of "W3C DRM". There is no such thing. The EME spec doesn't define any DRM mechanism. There is a different, closed-source proprietary mechanism in each of the main browsers, by design. EME is like the `<object>` tag. It doesn't do anything without a plugin (and the plugins are now called CDMs).