--- a/encrypted-media/encrypted-media.html Wed Sep 03 17:18:06 2014 -0700
+++ b/encrypted-media/encrypted-media.html Wed Sep 03 17:18:41 2014 -0700
@@ -142,8 +142,8 @@
<p>The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation).
License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies.</p>
<p>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.</p>
+ 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
+ Clear Key system is required to be implemented as a common baseline.</p>
<p>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 encryption system and a license
or other server.</p>
@@ -190,7 +190,7 @@
<li><a href="#mediakeys">2. MediaKeys Object</a></li>
<li><a href="#mediakeysession">3. MediaKeySession Object</a></li>
<li><a href="#htmlmediaelement-extensions">4. HTMLMediaElement Extensions</a></li>
- <li><a href="#simple-decryption">5. Simple Decryption</a></li>
+ <li><a href="#common-key-systems">5. Common Key Systems</a></li>">
<li><ul style="list-style-type:none">
<li><a href="#clear-key">5.1. Clear Key</a></li>
</ul></li>
@@ -225,7 +225,7 @@
<p>A Key System is a generic term for a decryption mechanism and/or content protection provider.
Key System strings provide unique identification of a Key System.
They are used by the user agent to select the <a href="#cdm">Content Decryption Modules</a> and identify the source of a key-related event.
- <a href="#simple-decryption">Simple Decryption</a> Key Systems are supported by all user agents. User agents may also provide additional CDMs with corresponding Key System strings.
+ The <a href="#common-key-systems">Common Key Systems</a> are supported by all user agents. User agents may also provide additional CDMs with corresponding Key System strings.
</p>
<p>A Key System string is always a reverse domain name. <span class="non-normative">For example, "com.example.somesystem".</span>
@@ -1282,8 +1282,8 @@
video media may be constrained to appear only in rectangular regions with sides parallel to the edges of the window and with normal orientation.</p>
- <h2 id="simple-decryption">5. Simple Decryption</h2>
- <p>All user agents must support the simple decryption capabilities described in this section regardless of whether they support a more advanced <a href="#cdm">CDM</a>.
+ <h2 id="common-key-systems">5. Common Key Systems</h2>
+ <p>All user agents must support the common key systems described in this section.
<span class="non-normative">This ensures that there is a common baseline level of protection that is guaranteed to be supported in all user agents, including those that are entirely open source.
Thus, content providers that need only basic protection can build simple applications that will work on all platforms without needing to work with any content protection providers.</span>
</p>
--- a/encrypted-media/encrypted-media.xml Wed Sep 03 17:18:06 2014 -0700
+++ b/encrypted-media/encrypted-media.xml Wed Sep 03 17:18:41 2014 -0700
@@ -139,8 +139,8 @@
<p>The API supports use cases ranging from simple clear key decryption to high value video (given an appropriate user agent implementation).
License/key exchange is controlled by the application, facilitating the development of robust playback applications supporting a range of content decryption and protection technologies.</p>
<p>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.</p>
+ 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
+ Clear Key system is required to be implemented as a common baseline.</p>
<p>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 encryption system and a license
or other server.</p>
@@ -187,7 +187,7 @@
<li><a href="#mediakeys">2. MediaKeys Object</a></li>
<li><a href="#mediakeysession">3. MediaKeySession Object</a></li>
<li><a href="#htmlmediaelement-extensions">4. HTMLMediaElement Extensions</a></li>
- <li><a href="#simple-decryption">5. Simple Decryption</a></li>
+ <li><a href="#common-key-systems">5. Common Key Systems</a></li>">
<li><ul style="list-style-type:none">
<li><a href="#clear-key">5.1. Clear Key</a></li>
</ul></li>
@@ -222,7 +222,7 @@
<p>A Key System is a generic term for a decryption mechanism and/or content protection provider.
Key System strings provide unique identification of a Key System.
They are used by the user agent to select the <a href="#cdm">Content Decryption Modules</a> and identify the source of a key-related event.
- <a href="#simple-decryption">Simple Decryption</a> Key Systems are supported by all user agents. User agents may also provide additional CDMs with corresponding Key System strings.
+ The <a href="#common-key-systems">Common Key Systems</a> are supported by all user agents. User agents may also provide additional CDMs with corresponding Key System strings.
</p>
<p>A Key System string is always a reverse domain name. <span class="non-normative">For example, "com.example.somesystem".</span>
@@ -1212,8 +1212,8 @@
video media may be constrained to appear only in rectangular regions with sides parallel to the edges of the window and with normal orientation.</p>
- <h2 id="simple-decryption">5. Simple Decryption</h2>
- <p>All user agents must support the simple decryption capabilities described in this section regardless of whether they support a more advanced <a href="#cdm">CDM</a>.
+ <h2 id="common-key-systems">5. Common Key Systems</h2>
+ <p>All user agents must support the common key systems described in this section.
<span class="non-normative">This ensures that there is a common baseline level of protection that is guaranteed to be supported in all user agents, including those that are entirely open source.
Thus, content providers that need only basic protection can build simple applications that will work on all platforms without needing to work with any content protection providers.</span>
</p>