[EME] Clean up Clear Key format examples.
Move the Clear Key format examples and Using base64url to their own non-normative sections.
Also, use the "example" class directly in <pre> as appropriate.
--- a/encrypted-media/encrypted-media.html Fri May 30 15:07:09 2014 -0700
+++ b/encrypted-media/encrypted-media.html Fri May 30 15:08:32 2014 -0700
@@ -378,7 +378,8 @@
</div>
partial interface <dfn id="dom-htmlsourceelement">HTMLSourceElement</dfn> {
attribute DOMString <a href="#dom-sourcekeysystem">keySystem</a>;
-};</pre>
+};
+</pre>
<div class="note">
<div class="noteHeader">Note</div>
@@ -965,7 +966,8 @@
dictionary <dfn id="dom-mediakeyneededeventinit">MediaKeyNeededEventInit</dfn> : <a href="http://www.w3.org/TR/dom/#eventinit">EventInit</a> {
DOMString <a href="#dom-initdatatype">initDataType</a>;
Uint8Array? <a href="#dom-initdata">initData</a>;
-};</pre>
+};
+</pre>
<pre class="idl">
[Constructor(DOMString type, optional <a href="#dom-mediakeymessageeventinit">MediaKeyMessageEventInit</a> eventInitDict)]
@@ -977,7 +979,8 @@
dictionary <dfn id="dom-mediakeymessageeventinit">MediaKeyMessageEventInit</dfn> : <a href="http://www.w3.org/TR/dom/#eventinit">EventInit</a> {
Uint8Array <a href="#dom-message">message</a>;
DOMString? <a href="#dom-destinationurl">destinationURL</a>;
-};</pre>
+};
+</pre>
<dl class="domintro">
<dt>
@@ -1337,7 +1340,7 @@
This Key System is described below.
</p>
- <h4 id="clear-key-capabilities">Capabilities</h4>
+ <h4 id="clear-key-capabilities">5.1.1. Capabilities</h4>
<p>The following describe how Clear Key supports key system-specific capabilities:</p>
<ul>
<li><p>The <code><a href="#dom-setmediakeys">setMediaKeys()</a></code> method: Implementations may support associating the <code><a href="#dom-mediakeys">MediaKeys</a></code> object with more than one <code><a href="#dom-htmlmediaelement">HTMLMediaElement</a></code>.</p></li>
@@ -1346,7 +1349,7 @@
<li><p>The "<code><a href="#dom-sessiontypepersistent">persistent</a></code>" <code><a href="#dom-sessiontype">SessionType</a></code>, including the <code><a href="#dom-loadsession">loadSession()</a></code> and <code><a href="#dom-remove">remove()</a></code> methods: Implementations may support these.</p></li>
</ul>
- <h4 id="clear-key-behavior">Behavior</h4>
+ <h4 id="clear-key-behavior">5.1.2. Behavior</h4>
<p>The following describe how Clear Key implements key system-specific behaviors:</p>
<ul>
<li>
@@ -1368,11 +1371,11 @@
</ul>
</li>
<li><p><a href="#initialization-data">Initialization Data</a>: Implementations may support any combination of <a href="initdata-format-registry.html">registered and Initialization Data types</a>.
- Implementations should support the "<a href="keyids-format.html%20">keyids</a>" type and other types appropriate for content supported by the user agent.
+ Implementations should support the "<a href="keyids-format.html%20">keyids</a>" type and other types appropriate for content types supported by the user agent.
</p></li>
</ul>
- <h4 id="clear-key-request-format">Licese Request Format</h4>
+ <h4 id="clear-key-request-format">5.1.3. Licese Request Format</h4>
<p>This section describes the format of the license request provided to the application via the <code><a href="#dom-message">message</a></code> attribute of the <a href="#dom-eventmessage">message</a> event.</p>
<p>The format is a JSON object containing the following members:</p>
@@ -1384,10 +1387,15 @@
</dd>
</dl>
- <div class="nonnormative">
- <p>The following example is a license request for a temporary license for two key IDs. (Line breaks are for readability only.)</p>
- <div class="example nonnormative">
- <pre class="code">
+ <p>When contained in the Uint8Array <code><a href="#dom-message">message</a></code> attribute of a <code><a href="#dom-mediakeymessageevent">MediaKeyMessageEvent</a></code> object, the JSON string is encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
+ Applications may decode the contents of the Uint8Array to a JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textdecoder">TextDecoder interface</a>.
+ </p>
+
+
+ <h5 id="clear-key-licese-format">5.1.3.1. Example</h5>
+ <p><i>This section is non-normative.</i></p>
+ <p>The following example is a license request for a temporary license for two key IDs. (Line breaks are for readability only.)</p>
+ <pre class="example">
{
"kids":
[
@@ -1395,15 +1403,10 @@
"77ef0gd8pvfd0"
],
"type":"<a href="#dom-sessiontypetemporary">temporary</a>"
-}</pre>
- </div>
- </div>
+}
+</pre>
- <p>When contained in the Uint8Array <code><a href="#dom-message">message</a></code> attribute of a <code><a href="#dom-mediakeymessageevent">MediaKeyMessageEvent</a></code> object, the JSON string is encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
- Applications may decode the contents of the Uint8Array to a JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textdecoder">TextDecoder interface</a>.
- </p>
-
- <h4 id="clear-key-licese-format">Licese Format</h4>
+ <h4 id="clear-key-licese-format">5.1.4. Licese Format</h4>
<p>This section describes the format of the license to be provided via the <var title="true">response</var> parameter of the <code><a href="#dom-update">update()</a></code> method.</p>
<p>The format is a JSON Web Key (JWK) Set containing representation of the symmetric key to be used for decryption, as defined in the <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-key">IETF Internet-draft JSON Web Key (JWK) specification</a>.</p>
@@ -1419,21 +1422,21 @@
<dt>"kid" (key ID)</dt>
<dd>The base64url encoding of the octet sequence containing the <a href="#decryption-key-id">key ID</a> value</dd>
</dl>
- <div class="nonnormative">
- <p>For more information on base64url and working with it, see the Base64url Encoding entry in the <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#section-2">Terminology section</a> and <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#appendix-C">Notes on implementing base64url encoding without padding</a> of the JSON Web Signature (JWS) specification.
- Specifically, there is no '=' padding and '-' and '_' must be used instead of '+' and '/', respectively.
- </p>
- </div>
<p>The JSON object may have an optional "type" member value, which may be any of the <code><a href="#dom-sessiontype">SessionType</a></code> values.
If not specified, the default value of "<code><a href="#dom-sessiontypetemporary">temporary</a></code>" is used.
The <code><a href="#dom-update">update()</a></code> algorithm compares this value to the <var title="true">sessionType</var>.
</p>
- <div class="nonnormative">
- <p>The following example is a JWK Set containing a single symmetric key. (Line breaks are for readability only.)</p>
- <div class="example nonnormative">
- <pre class="code">
+ <p>When passed to the <code><a href="#dom-update">update()</a></code> method as the Uint8Array <var title="true">response</var> parameter, the JSON string must be encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
+ Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a>.
+ </p>
+
+
+ <h5 id="clear-key-licese-format">5.1.4.1. Example</h5>
+ <p><i>This section is non-normative.</i></p>
+ <p>The following example is a JWK Set containing a single symmetric key. (Line breaks are for readability only.)</p>
+ <pre class="example">
{
"keys":
[{
@@ -1444,13 +1447,15 @@
}],
"type":"<a href="#dom-sessiontypetemporary">temporary</a>"
}</pre>
- </div>
- </div>
- <p>When passed to the <code><a href="#dom-update">update()</a></code> method as the Uint8Array <var title="true">response</var> parameter, the JSON string must be encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
- Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a>.
+
+ <h4 id="using-base64url">5.1.5. Using base64url</h4>
+ <p><i>This section is non-normative.</i></p>
+ <p>For more information on base64url and working with it, see the Base64url Encoding entry in the <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#section-2">Terminology section</a> and <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#appendix-C">Notes on implementing base64url encoding without padding</a> of the JSON Web Signature (JWS) specification.
+ Specifically, there is no '=' padding, and the characters '-' and '_' must be used instead of '+' and '/', respectively.
</p>
+
<h2 id="security">6. Security Considerations</h2>
<div class="nonnormative">
@@ -1573,8 +1578,7 @@
<p class="exampledescription">In this simple example, the source file and <a href="#clear-key">clear-text license</a> are hard-coded in the page.
Only one session will ever be created.</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
function load() {
var video = document.getElementById("video");
@@ -1618,8 +1622,8 @@
<body onload="load()">
<video src="foo.webm" autoplay id="video"></video>
-</body></pre>
- </div>
+</body>
+</pre>
<h3 id="example-selecting-key-system" class="exampleheader">8.2. Selecting a Supported Key System and Using Initialization Data from the "needkey" Event</h3>
<p class="exampledescription">This example selects a supported <a href="#key-system">Key System</a> using the <code><a href="#dom-istypesupported">isTypeSupported()</a></code> method then uses
@@ -1627,8 +1631,7 @@
One of the supported key systems uses a serverCertificate, which is provided proactively.
</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1715,8 +1718,8 @@
}
</script>
-<video src="foo.webm" autoplay on<a href="#dom-needkey">needkey</a>="handleKeyNeeded(event)"></video></pre>
- </div>
+<video src="foo.webm" autoplay on<a href="#dom-needkey">needkey</a>="handleKeyNeeded(event)"></video>
+</pre>
<h3 id="example-mediakeys-before-source" class="exampleheader">8.3. Create MediaKeys Before Loading Media</h3>
<p class="exampledescription">Initialization is much simpler if needkey events do not need to be handled during MediaKeys initialization.
@@ -1724,8 +1727,7 @@
This example does the latter.
</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1756,15 +1758,14 @@
);
</script>
-<video id="v" autoplay on<a href="#dom-needkey">needkey</a>="handleKeyNeeded(event)"></video></pre>
- </div>
+<video id="v" autoplay on<a href="#dom-needkey">needkey</a>="handleKeyNeeded(event)"></video>
+</pre>
<h3 id="example-using-all-events" class="exampleheader">8.4. Using All Events</h3>
<p class="exampledescription">This is a more complete example showing all events being used.</p>
<p class="exampledescription">Note that <code>handleMessage()</code> could be called multiple times, including in response to the <code><a href="#dom-update">update()</a></code> call if multiple round trips are required and for any other reason the Key System might need to send a message.</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1841,14 +1842,13 @@
);
</script>
-<video id="v" autoplay on<a href="#dom-needkey">needkey</a>="handleKeyNeeded(event)"></video></pre>
- </div>
+<video id="v" autoplay on<a href="#dom-needkey">needkey</a>="handleKeyNeeded(event)"></video>
+</pre>
<h3 id="example-stored-license" class="exampleheader">8.5. Stored License</h3>
<p class="exampledescription">This example requests a persistent license for future use and stores it. It also provides functions for later retrieving the license and for destroying it.</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1947,8 +1947,8 @@
);
</script>
-<video id="v" src="foo.webm" autoplay></video></pre>
- </div>
+<video id="v" src="foo.webm" autoplay></video>
+</pre>
<h2 id="revision-history">9. Revision History</h2>
--- a/encrypted-media/encrypted-media.xml Fri May 30 15:07:09 2014 -0700
+++ b/encrypted-media/encrypted-media.xml Fri May 30 15:08:32 2014 -0700
@@ -369,7 +369,8 @@
<div class="issue"><div class="issue-title"><span>Issue 1</span></div><p class="">Extensions to <precoderef>HTMLSourceElement</precoderef> may be at risk as discussed in <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=23827">Bug 23827</a>.</p></div>
partial interface <precodedfn>HTMLSourceElement</precodedfn> {
attribute DOMString <precoderef prefix="source">keySystem</precoderef>;
-};</pre>
+};
+</pre>
<div class="note"><div class="noteHeader">Note</div>
<p>All errors are reported asynchronously by rejecting the returned Promise. This includes WebIDL type mapping errors.</p>
@@ -908,7 +909,8 @@
dictionary <precodedfn>MediaKeyNeededEventInit</precodedfn> : <dom4ref name="eventinit">EventInit</dom4ref> {
DOMString <precoderef>initDataType</precoderef>;
Uint8Array? <precoderef>initData</precoderef>;
-};</pre>
+};
+</pre>
<pre class="idl">
[Constructor(DOMString type, optional <precoderef>MediaKeyMessageEventInit</precoderef> eventInitDict)]
@@ -920,7 +922,8 @@
dictionary <precodedfn>MediaKeyMessageEventInit</precodedfn> : <dom4ref name="eventinit">EventInit</dom4ref> {
Uint8Array <precoderef>message</precoderef>;
DOMString? <precoderef>destinationURL</precoderef>;
-};</pre>
+};
+</pre>
<dl class="domintro">
<dt><var title="">event</var> . <coderef>initDataType</coderef></dt>
@@ -1261,7 +1264,7 @@
This Key System is described below.
</p>
- <h4 id="clear-key-capabilities">Capabilities</h4>
+ <h4 id="clear-key-capabilities">5.1.1. Capabilities</h4>
<p>The following describe how Clear Key supports key system-specific capabilities:</p>
<ul>
<li><p>The <methodref>setMediaKeys</methodref> method: Implementations may support associating the <coderef>MediaKeys</coderef> object with more than one <coderef>HTMLMediaElement</coderef>.</p></li>
@@ -1270,7 +1273,7 @@
<li><p>The "<coderef prefix="sessiontype">persistent</coderef>" <coderef>SessionType</coderef>, including the <methodref>loadSession</methodref> and <methodref>remove</methodref> methods: Implementations may support these.</p></li>
</ul>
- <h4 id="clear-key-behavior">Behavior</h4>
+ <h4 id="clear-key-behavior">5.1.2. Behavior</h4>
<p>The following describe how Clear Key implements key system-specific behaviors:</p>
<ul>
<li><p>In the <methodref>createSession</methodref> algorithm:</p>
@@ -1294,7 +1297,7 @@
</p></li>
</ul>
- <h4 id="clear-key-request-format">Licese Request Format</h4>
+ <h4 id="clear-key-request-format">5.1.3. Licese Request Format</h4>
<p>This section describes the format of the license request provided to the application via the <coderef>message</coderef> attribute of the <precoderef prefix="event">message</precoderef> event.</p>
<p>The format is a JSON object containing the following members:</p>
@@ -1305,10 +1308,15 @@
<dd>The requested <coderef>SessionType</coderef></dd>
</dl>
- <div class="nonnormative">
- <p>The following example is a license request for a temporary license for two key IDs. (Line breaks are for readability only.)</p>
- <div class="example nonnormative">
- <pre class="code">
+ <p>When contained in the Uint8Array <coderef>message</coderef> attribute of a <coderef>MediaKeyMessageEvent</coderef> object, the JSON string is encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
+ Applications may decode the contents of the Uint8Array to a JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textdecoder">TextDecoder interface</a>.
+ </p>
+
+ <!-- Will be <section class="informative"> -->
+ <h5 id="clear-key-licese-format">5.1.3.1. Example</h5>
+ <non-normative-section/>
+ <p>The following example is a license request for a temporary license for two key IDs. (Line breaks are for readability only.)</p>
+ <pre class="example">
{
"kids":
[
@@ -1316,15 +1324,10 @@
"77ef0gd8pvfd0"
],
"type":"<precoderef prefix="sessiontype">temporary</precoderef>"
-}</pre>
- </div>
- </div>
+}
+</pre>
- <p>When contained in the Uint8Array <coderef>message</coderef> attribute of a <coderef>MediaKeyMessageEvent</coderef> object, the JSON string is encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
- Applications may decode the contents of the Uint8Array to a JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textdecoder">TextDecoder interface</a>.
- </p>
-
- <h4 id="clear-key-licese-format">Licese Format</h4>
+ <h4 id="clear-key-licese-format">5.1.4. Licese Format</h4>
<p>This section describes the format of the license to be provided via the <var title="true">response</var> parameter of the <methodref>update</methodref> method.</p>
<p>The format is a JSON Web Key (JWK) Set containing representation of the symmetric key to be used for decryption, as defined in the <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-key">IETF Internet-draft JSON Web Key (JWK) specification</a>.</p>
@@ -1340,21 +1343,21 @@
<dt>"kid" (key ID)</dt>
<dd>The base64url encoding of the octet sequence containing the <a href="#decryption-key-id">key ID</a> value</dd>
</dl>
- <div class="nonnormative">
- <p>For more information on base64url and working with it, see the Base64url Encoding entry in the <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#section-2">Terminology section</a> and <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#appendix-C">Notes on implementing base64url encoding without padding</a> of the JSON Web Signature (JWS) specification.
- Specifically, there is no '=' padding and '-' and '_' must be used instead of '+' and '/', respectively.
- </p>
- </div>
<p>The JSON object may have an optional "type" member value, which may be any of the <coderef>SessionType</coderef> values.
If not specified, the default value of "<coderef prefix="sessiontype">temporary</coderef>" is used.
The <methodref>update</methodref> algorithm compares this value to the <var title="true">sessionType</var>.
</p>
- <div class="nonnormative">
- <p>The following example is a JWK Set containing a single symmetric key. (Line breaks are for readability only.)</p>
- <div class="example nonnormative">
- <pre class="code">
+ <p>When passed to the <methodref>update</methodref> method as the Uint8Array <var title="true">response</var> parameter, the JSON string must be encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
+ Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a>.
+ </p>
+
+ <!-- Will be <section class="informative"> -->
+ <h5 id="clear-key-licese-format">5.1.4.1. Example</h5>
+ <non-normative-section/>
+ <p>The following example is a JWK Set containing a single symmetric key. (Line breaks are for readability only.)</p>
+ <pre class="example">
{
"keys":
[{
@@ -1365,13 +1368,15 @@
}],
"type":"<precoderef prefix="sessiontype">temporary</precoderef>"
}</pre>
- </div>
- </div>
- <p>When passed to the <methodref>update</methodref> method as the Uint8Array <var title="true">response</var> parameter, the JSON string must be encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
- Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a>.
+ <!-- Will be <section class="informative"> -->
+ <h4 id="using-base64url">5.1.5. Using base64url</h4>
+ <non-normative-section/>
+ <p>For more information on base64url and working with it, see the Base64url Encoding entry in the <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#section-2">Terminology section</a> and <a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature#appendix-C">Notes on implementing base64url encoding without padding</a> of the JSON Web Signature (JWS) specification.
+ Specifically, there is no '=' padding, and the characters '-' and '_' must be used instead of '+' and '/', respectively.
</p>
+
<h2 id="security">6. Security Considerations</h2>
<div class="nonnormative">
@@ -1492,8 +1497,7 @@
<p class="exampledescription">In this simple example, the source file and <a href="#clear-key">clear-text license</a> are hard-coded in the page.
Only one session will ever be created.</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
function load() {
var video = document.getElementById("video");
@@ -1537,8 +1541,8 @@
<body onload="load()">
<video src="foo.webm" autoplay id="video"></video>
-</body></pre>
- </div>
+</body>
+</pre>
<h3 id="example-selecting-key-system" class="exampleheader">8.2. Selecting a Supported Key System and Using Initialization Data from the "needkey" Event</h3>
<p class="exampledescription">This example selects a supported <a href="#key-system">Key System</a> using the <methodref>isTypeSupported</methodref> method then uses
@@ -1546,8 +1550,7 @@
One of the supported key systems uses a serverCertificate, which is provided proactively.
</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1634,8 +1637,8 @@
}
</script>
-<video src="foo.webm" autoplay on<precoderef>needkey</precoderef>="handleKeyNeeded(event)"></video></pre>
- </div>
+<video src="foo.webm" autoplay on<precoderef>needkey</precoderef>="handleKeyNeeded(event)"></video>
+</pre>
<h3 id="example-mediakeys-before-source" class="exampleheader">8.3. Create MediaKeys Before Loading Media</h3>
<p class="exampledescription">Initialization is much simpler if needkey events do not need to be handled during MediaKeys initialization.
@@ -1643,8 +1646,7 @@
This example does the latter.
</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1675,15 +1677,14 @@
);
</script>
-<video id="v" autoplay on<precoderef>needkey</precoderef>="handleKeyNeeded(event)"></video></pre>
- </div>
+<video id="v" autoplay on<precoderef>needkey</precoderef>="handleKeyNeeded(event)"></video>
+</pre>
<h3 id="example-using-all-events" class="exampleheader">8.4. Using All Events</h3>
<p class="exampledescription">This is a more complete example showing all events being used.</p>
<p class="exampledescription">Note that <code>handleMessage()</code> could be called multiple times, including in response to the <methodref>update</methodref> call if multiple round trips are required and for any other reason the Key System might need to send a message.</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1760,14 +1761,13 @@
);
</script>
-<video id="v" autoplay on<precoderef>needkey</precoderef>="handleKeyNeeded(event)"></video></pre>
- </div>
+<video id="v" autoplay on<precoderef>needkey</precoderef>="handleKeyNeeded(event)"></video>
+</pre>
<h3 id="example-stored-license" class="exampleheader">8.5. Stored License</h3>
<p class="exampledescription">This example requests a persistent license for future use and stores it. It also provides functions for later retrieving the license and for destroying it.</p>
- <div class="example">
- <pre class="code">
+ <pre class="example">
<script>
var keySystem;
var licenseUrl;
@@ -1866,8 +1866,8 @@
);
</script>
-<video id="v" src="foo.webm" autoplay></video></pre>
- </div>
+<video id="v" src="foo.webm" autoplay></video>
+</pre>
<h2 id="revision-history">9. Revision History</h2>
--- a/encrypted-media/keyids-format-respec.html Fri May 30 15:07:09 2014 -0700
+++ b/encrypted-media/keyids-format-respec.html Fri May 30 15:08:32 2014 -0700
@@ -75,6 +75,8 @@
<dt>"kids"</dt>
<dd>An array of <a href="encrypted-media.html#decryption-key-id">key IDs</a>. Each element of the array is the base64url encoding of the octet sequence containing the key ID value.</dd>
</dl>
+
+ <p class="note">See <a href="encrypted-media.html#using-base64url"> Using base64url</a>.</p>
<p>When passed to the <code><a href="encrypted-media.html#dom-update">update()</a></code> method as the Uint8Array <var>response</var> parameter, the JSON string must be encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a>.
--- a/encrypted-media/keyids-format.html Fri May 30 15:07:09 2014 -0700
+++ b/encrypted-media/keyids-format.html Fri May 30 15:08:32 2014 -0700
@@ -152,6 +152,45 @@
aside.example div.example div.example-title {
color: #999;
}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+ padding-right: 1em;
+ min-width: 7.5em;
+ color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #2b2; }
+div.issue-title span, div.note-title span {
+ text-transform: uppercase;
+}
+div.note, div.issue {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+ padding: .5em;
+ border-left-width: .5em;
+ border-left-style: solid;
+}
+div.issue, div.note {
+ padding: 1em 1.2em 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+ border-color: #e05252;
+ background: #fbe9e9;
+}
+.note {
+ border-color: #52e052;
+ background: #e9fbe9;
+}
+
+
</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-ED"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
<body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
<p>
@@ -161,7 +200,7 @@
</p>
<h1 class="title p-name" id="title" property="dcterms:title">Key IDs Initialization Data</h1>
- <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-05-31T04:29:17.000Z" id="w3c-editor-s-draft-30-may-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2014-05-30">30 May 2014</time></h2>
+ <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-05-31T04:51:08.000Z" id="w3c-editor-s-draft-30-may-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2014-05-30">30 May 2014</time></h2>
<dl>
<dt>This version:</dt>
@@ -301,6 +340,8 @@
<dt>"kids"</dt>
<dd>An array of <a href="encrypted-media.html#decryption-key-id">key IDs</a>. Each element of the array is the base64url encoding of the octet sequence containing the key ID value.</dd>
</dl>
+
+ <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><p class="">See <a href="encrypted-media.html#using-base64url"> Using base64url</a>.</p></div>
<p>When passed to the <code><a href="encrypted-media.html#dom-update">update()</a></code> method as the Uint8Array <var>response</var> parameter, the JSON string must be encoded in utf-8 as specified in the <a href="http://www.w3.org/TR/encoding/">Encoding</a> specification.
Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a>.