16542 2012-03-27 18:43:10 +0000 Clarify abstract about "No 'DRM' is added" 2012-09-01 22:42:12 +0000 1 1 1 Unclassified HTML WG Encrypted Media Extensions unspecified All All RESOLVED FIXED http://dvcs.w3.org/hg/html-media/raw-file/c996f5dc1e3c/encrypted-media/encrypted-media.html P3 normal --- 1 adrianba adrianba ddorwin eric.carlson mike philipj public-html-media public-html-wg-issue-tracking watsonm public-html-bugzilla oldest_to_newest 66136 0 adrianba 2012-03-27 18:43:10 +0000 The abstract of the spec says "No "DRM" is added to the HTML5 specification, and only simple clear key decryption is required as a common baseline." This should better describe how the underlying implementation of a DRM/content protection system is not included in this spec, not required to implement the spec, and that the spec mediates access to such a system allowing the page to communicate with a license service as necessary. 68327 1 watsonm 2012-05-30 22:26:57 +0000 (In reply to comment #0) > The abstract of the spec says "No "DRM" is added to the HTML5 specification, > and only simple clear key decryption is required as a common baseline." > > This should better describe how the underlying implementation of a DRM/content > protection system is not included in this spec, not required to implement the > spec, and that the spec mediates access to such a system allowing the page to > communicate with a license service as necessary. I propose the following text to replace the statement above: "This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Implementation of Digital Rights Management is not required for compliance with this specification: only the simple clear key system is required to be implemented as a common baseline. The common API supports a simple set of content encryption capabilities, leaving application functions such as authentication and authorization to page authors. This is achieved by requiring content protection system-specific messaging to be mediated by the page, rather than assuming out-of-band communication between the Content Decryption Module and a license or other server." 68526 2 ddorwin 2012-06-01 19:12:01 +0000 I like it. nit: We might want to avoid specific terms like "Content Decryption Module" in the abstract. Maybe replace it with "encryption system". 68529 3 ddorwin 2012-06-01 19:36:07 +0000 While we're editing the Abstract, we should try to address bug 16543 too. That is, we should have one cohesive update that introduces the document. 72920 4 adrianba 2012-08-28 20:51:13 +0000 Assigned to Adrian to add text. Will also ensure that bug 16543 is addressed by this change. 72924 5 adrianba 2012-08-28 20:52:48 +0000 *** Bug 16543 has been marked as a duplicate of this bug. *** 73147 6 adrianba 2012-09-01 22:42:12 +0000 Fixed. Change set -> http://dvcs.w3.org/hg/html-media/rev/1ca7610af922