3 ms·
A key paragraph: link: http://lists.w3.org/Archives/Public/public-restrictedmedia/2014Jan/0066.html http://lists.w3.org/Archives/Public/public-restrictedmedia/
by andybak 13y ago
A key paragraph:
link: http://lists.w3.org/Archives/Public/public-restrictedmedia/2014Jan/0066.html http://lists.w3.org/Archives/Public/public-restrictedmedia/2...
Well, as I say, the actual requirements that lead to the proposal of EME
would be a start. This is how it looks to those who don't agree that
EME is a good fit with the Open Web:
- 'big content' has certain requirements relating to preventing users
copying data streams
- they won't make those requirements public (as you've said, the
agreements are confidential)
- their licensees propose a technical solution that is unacceptable to
many others because it necessitates the use of non-user-modifiable
client components
- all proposed alternatives (e.g. FOSS DRM, server-side watermarking,
client-side watermarking, no DRM at all) are shot down as being either
too expensive or inadequate to the (secret) requirements
In a normal software project, I'd take an apparently insoluble conflict
(the requirement for non-user-modifiable client components) to mean that
we have done a poor job of determining requirements.
Hence my request for either a real user to talk to (e.g. an MPAA rep) or
the actual requirements docs, which you've told me are confidential.
And that sets off my spidey-senses ... something is not quite right
here.
- RexRollman 13y agoWell, my question is does HTML even need to encompass everything it does. It seems to me that we have an ever expanding monster. HTML does not have to be everything for everyone.
- talmand 13y agoI thought that was more-or-less what was being discussed. My understanding was that the media element being accessed would not play the stream unless a specified DRM component was available, most often due to a plugin installed to the browser. It wasn't that they wanted DRM in the open web, they wanted the open web to have the ability to communicate with a third-party DRM. A third-party solution that an individual can decline to install and not participate.
- Nursie 13y ago>> A third-party solution that an individual can decline to install and not participate. A third party solution that they can't get hold of because the 'official' one only runs on windows and intel, and the ps4.
- talmand 13y agoSo? If they don't provide the content you wish to see in a way that's convenient for you but is convenient for the mass of their market I fail to see the problem. If you want to see the content bad enough then you accept the requirements. Otherwise, it says more for you to not participate by not giving money. As more people do this, things will change.
- Nursie 13y agoSo we shouldn't encourage its addition to open standards.
- talmand 13y agoIf it's in the standards to explain how to implement it and make use of it but it's implemented as a third-party item that's up to the individual to decide whether to install or not, what difference does it make? We're eventually going to get that anyway so why not know how it works upfront? Plus, from what I've read Chrome should start losing market share immediately because it already has a form of EME implemented. All these people in an uproar over the W3C's decision should be switching to something else to show their concern.
- jscheel 13y agoExactly. The "just trust us" approach is bogus, antithetical to the open web, and cripples the overall progress in this discussion.