- From: <bugzilla@jessica.w3.org>
- Date: Wed, 13 Mar 2013 23:49:58 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21231 --- Comment #13 from Fred Andrews <fredandw@live.com> --- (In reply to comment #12) > (In reply to comment #4) > > This is not directly related to the <small> element. The <small> element > > may well be used to communicate a message to the user, just as a <p> element > > may, but neither gives the semantic information needed to address the use > > cases in this bug report. > > I object to introducing a feature that requires the browser to interpret a > REL, since that would bring the complexity of managing restrictions out of > the CDM into the browser. (But I'd also object to requiring CDMs to > interpret a REL. I think decisions that one might imagine a REL to cover > should be performed by the server by deciding the either allow or disallow > data flows into the CDM given knowledge about what the CDM is designed to > hide.) It is not technically possible for the server to have 'knowledge about what the CDM is designed to hide' unless the CDM and platform is already implements strong DRM, and this bug only deals with non-DRM solutions. If the user has control over their computer then they can access the decoded stream without the knowledge of the server and thus it is not possible for the server to control access to content on this basis. Further, it would seem to be far more consistent with the open web development process to document the flags in open and unencumbered specifications rather than deferring to a black box. > I also object to introducing features that make the > scope of DRM potentially broader than video. The scope of solutions for this bug do not include DRM - it specifically deals only with the non-DRM use cases. > I request that this bug be WONTFIXed. Given that the claimed technical basis for objecting to this bug is invalid, and that it is clearly not introducing DRM support, I request that it remain open for further discussion. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 13 March 2013 23:49:59 UTC