I don't see how DRM is incompatible with their goals. Of course one might argue that DRM might be platform specific. However, I very much doubt this standard will make DRM more platform specific than it already is.
It is in fact quite possible that it will. DRM, right now, is mainly Flash. For all its faults, Flash runs on all browsers and OSes. However, EME CDM modules may only work in Chrome and Internet Explorer - the two browser vendors pushing the EME spec, and that have their own DRM solutions that they are building as CDMs.
Why would Google or Microsoft create CDMs that work in browsers or OSes that they do not own? If not them, then who would create a CDM that works on all browsers and OSes? Possibly no one.
Of course not! In fact, due to the nature of the web, it will make DRM in general less platform-specific! The problem is that HTML will become more platform-specific.
> will make DRM in general less platform-specific!
Why do you think the inclusion of an EME standard in HTML5 will induce CDM producers to support operating systems that they wouldn't have supported without EME?
Don't like it, don't partake. I can't understand this mentality...
>
> Don't like it, don't partake. I can't understand this mentality...
What mentality? Perhaps you should read my other posts. To summarise, my position is:
- if Netflix wants to build their own DRM system, fine
- if they don't want to include my chosen operating system, that's their perogative, they just lose out on my money
- what is _not_ okay is for Netflix to lobby the W3C to include DRM in HTML5
The point I'm trying to make is that having a DRM standard in HTML5 does not mean that Netflix will suddenly start to support Linux. Several posters have expressed this idea, and it's just plain incorrect.
Who says it has to be made by Netflix or at their expense? I'm sure there are open source developers (e.g. Mozilla) who would be happy to create a multiplatform open source Netflix client. Netflix are the ones who make that impossible, and having done that their remaining alternatives are a) provide the client themselves, or b) incur the wrath of angry users. They've decided to go with (b), so here we are.