--- a/encrypted-media/encrypted-media.html Thu Jun 28 17:27:15 2012 -0700
+++ b/encrypted-media/encrypted-media.html Thu Jun 28 17:47:28 2012 -0700
@@ -36,7 +36,7 @@
<div class="head">
<p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" width="72" height="48"></a></p>
<h1>Encrypted Media Extensions</h1>
- <h2>W3C Editor's Draft 27 June 2012</h2>
+ <h2>W3C Editor's Draft 28 June 2012</h2>
<dl>
<dt>Latest editor's draft:</dt>
<dd><a href="http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html">http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html</a></dd>
@@ -109,8 +109,8 @@
<li><a href="#key-release">4. Key Release</a></li>
<li><a href="#algorithms">5. Algorithms</a></li>
<li><ul style="list-style-type:none">
- <li><a href="#algorithms-enrypted-block">5.1. Potentially Encrypted Stream Encountered</a></li>
- <li><a href="#algorithms-encrypted-stream">5.2. Potentially encrypted stream encountered</a></li>
+ <li><a href="#algorithms-enrypted-block">5.1. Encrypted Block Encountered</a></li>
+ <li><a href="#algorithms-encrypted-stream">5.2. Potentially Encrypted Stream Encountered</a></li>
<li><a href="#algorithms-load">5.3. Addition to Media Element Load Algorithm</a></li>
</ul></li>
<li><a href="#simple-decryption">6. Simple Decryption</a></li>
@@ -162,6 +162,7 @@
</ul>
<h3 id="definitions">1.2. Definitions</h3>
+ <p>Text in <span class="non-normative">this font and color</span> is non-normative.</p>
<h4 id="cdm">1.2.1. Content Decryption Module (CDM)</h4>
<p><i>This section is non-normative.</i></p>
@@ -182,7 +183,7 @@
<span class="non-normative">For example, "com.example.somesystem.1" and "com.example.somesystem.1_5".</span>
<span class="non-normative">Key system providers should keep in mind that these will be used for comparison and discovery, so they should be easy to compare and the structure should remain reasonably simple.</span>
</p>
- <p class="issue">It may make sense to provide informal guidelines to avoid these diverging too much. There are probably best practices too. Should platform-specific or <a href="#faq-provider-capabilities">protection capability information</a> be contained in these strings?)</p>
+ <p class="issue">It may make sense to provide informal guidelines to avoid these diverging too much. There are probably best practices too. Should platform-specific or <a href="#faq-provider-capabilities">protection capability information</a> be contained in these strings?</p>
<p>If a user agent returns "maybe" or "probably" for any subsystem string, it must return "maybe" when a parent system string is passed to <code><a href="#dom-canplaytype">canPlayType()</a></code>.
<span class="non-normative">For example, if a user agent returns "maybe" or "probably" for "com.example.somesystem.1_5", it must return "maybe" for "com.example.somesystem".</span>
@@ -240,7 +241,7 @@
<pre class="idl">
partial interface <dfn id="dom-htmlmediaelement">HTMLMediaElement</dfn> {
- // No API changes. 'type' string is extended.
+ // Adds optional 'keySystem' parameter.
DOMString <a href="#dom-canplaytype">canPlayType</a>(in DOMString type, in DOMstring? <a href="#key-system">keySystem</a>);
void <a href="#dom-generatekeyrequest">generateKeyRequest</a>(in DOMString <a href="#key-system">keySystem</a>, in Uint8Array? initData);
@@ -325,7 +326,7 @@
<ol>
<li><p>Load <var title="true">handler</var> if necessary.</p></li>
- <li><p>Let <var title="true">defaultUrl</var> be null.</p></li>
+ <li><p>Let <var title="true">defaultURL</var> be null.</p></li>
<li>
<p>Use <var title="true">handler</var> to generate a key request and follow the steps for the first matching condition from the following list:</p>
<dl class="switch">
@@ -336,7 +337,7 @@
<p>Let <var title="true">key request</var> be a key request generated by the <a href="#cdm">CDM</a> using <var title="true">initData</var>, if provided.</p>
<p>Note: <var title="true">handler</var> must not use any data, including <a href="http://dev.w3.org/html5/spec/video.html#media-data">media data</a>, not provided via <var title="true">initData</var>.</p>
</li>
- <li><p>If <var title="true">initData</var> is not null and contains a default URL for <var title="true">keySystem</var>, let <var title="true">defaultUrl</var> be that URL.</p></li>
+ <li><p>If <var title="true">initData</var> is not null and contains a default URL for <var title="true">keySystem</var>, let <var title="true">defaultURL</var> be that URL.</p></li>
</ol>
</dd>
<dt>Otherwise</dt>
@@ -360,7 +361,7 @@
<code><a href="#dom-keysystem">keySystem</a></code> = <var title="true">keySystem</var><br>
<code><a href="#dom-sessionid">sessionId</a></code> = <var title="true">sessionId</var><br>
<code><a href="#dom-message">message</a></code> = <var title="true">key request</var><br>
- <code><a href="#dom-defaulturl">defaultUrl</a></code> = <var title="true">defaultUrl</var>
+ <code><a href="#dom-defaulturl">defaultURL</a></code> = <var title="true">defaultURL</var>
</li></ul>
<p class="non-normative">Note: <code><a href="#dom-message">message</a></code> may be a request for multiple keys, depending on the <var title="true"><a href="#key-system">keySystem</a></var> and/or <var title="true">initData</var>. This is transparent to the application.</p>
</li>
@@ -496,7 +497,7 @@
<code><a href="#dom-keysystem">keySystem</a></code> = <var title="true">keySystem</var><br>
<code><a href="#dom-sessionid">sessionId</a></code> = <var title="true">sessionId</var><br>
<code><a href="#dom-message">message</a></code> = <var title="true">next message</var><br>
- <code><a href="#dom-defaulturl">defaultUrl</a></code> = null
+ <code><a href="#dom-defaulturl">defaultURL</a></code> = null
<p class="issue">Is there a reason that this cannot be null?</p>
</li></ul>
</dd>
@@ -594,7 +595,7 @@
It seems that except for #1, which should only occur in applications that do not support encrypted media, these are all application bugs and not something that would improve the user experience.
Any unique handling of the error codes by an application would essentially be describing a bug type.
Unique codes might be helpful in tracking down the cause of the bug, but there are probably other options.
- It is also possible that some of these cases should be reported via <code><a href="#dom-mediakeyerroreventinit">MediaKeyErrorEventInit</a></code>.
+ It is also possible that some of these cases should be reported via <code><a href="#dom-mediakeyerrorevent">MediaKeyErrorEvent</a></code>.
</p>
<p>A <code><a href="#dom-mediakeyerror">MediaKeyError</a></code> may be one of the following:</p>
@@ -647,14 +648,14 @@
readonly attribute DOMString <a href="#dom-keysystem">keySystem</a>;
readonly attribute DOMString? <a href="#dom-sessionid">sessionId</a>;
readonly attribute Uint8Array <a href="#dom-message">message</a>;
- readonly attribute DOMString? <a href="#dom-defaulturl">defaultUrl</a>;
+ readonly attribute DOMString? <a href="#dom-defaulturl">defaultURL</a>;
};
dictionary <dfn id="dom-mediakeymessageeventinit">MediaKeyMessageEventInit</dfn> : <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#eventinit">EventInit</a> {
DOMString <a href="#dom-keysystem">keySystem</a>;
DOMString? <a href="#dom-sessionid">sessionId</a>;
Uint8Array <a href="#dom-message">message</a>;
- DOMString? <a href="#dom-defaulturl">defaultUrl</a>;
+ DOMString? <a href="#dom-defaulturl">defaultURL</a>;
};</pre>
<pre class="idl">
@@ -711,7 +712,7 @@
<p>Returns the message <span class="non-normative">(i.e. key request)</span> to send.</p>
</dd>
<dt>
-<var title="">event</var> . <code><a href="#dom-defaulturl">defaultUrl</a></code>
+<var title="">event</var> . <code><a href="#dom-defaulturl">defaultURL</a></code>
</dt>
<dd>
<p>Returns the default key exchange URL.</p>
@@ -736,7 +737,7 @@
<p>The <dfn id="dom-sessionid"><code>sessionId</code></dfn> attribute is the <a href="#session-id">Session ID</a> for the key or license that this event refers to. It may be null.</p>
<p>The <dfn id="dom-initdata"><code>initData</code></dfn> attribute contains <a href="#initialization-data">Initialization Data</a> specific to the event.</p>
<p>The <dfn id="dom-message"><code>message</code></dfn> attribute contains a message from the CDM. Messages are Key System-specific. <span class="non-normative">In most cases, it should be sent to a key server.</span></p>
- <p>The <dfn id="dom-defaulturl"><code>defaultUrl</code></dfn> is the default URL to send the key request to as provided by the <a href="http://dev.w3.org/html5/spec/video.html#media-data">media data</a>. It may be null.</p>
+ <p>The <dfn id="dom-defaulturl"><code>defaultURL</code></dfn> is the default URL to send the key request to as provided by the <a href="http://dev.w3.org/html5/spec/video.html#media-data">media data</a>. It may be null.</p>
<p>The <dfn id="dom-errorcode"><code>errorCode</code></dfn> attribute contains the <code><a href="#dom-mediakeyerror">MediaKeyError</a></code> code for the error that occurred.</p>
<p>The <dfn id="dom-systemcode"><code>systemCode</code></dfn> attribute contains a <a href="#key-system">Key System</a>-dependent status code for the error that occurred.
<span class="non-normative">This allows a more granular status to be returned than the more general <code><a href="#dom-errorcode">errorCode</a></code>.</span>
@@ -871,7 +872,7 @@
<code><a href="#dom-keysystem">keySystem</a></code> = <var title="true">keySystem</var><br>
<code><a href="#dom-sessionid">sessionId</a></code> = the sessionId originally associated with the provision of the key<br>
<code><a href="#dom-message">message</a></code> = <var title="true">key release message</var><br>
- <code><a href="#dom-defaulturl">defaultUrl</a></code> = value of the default URL, if stored by the CDM.
+ <code><a href="#dom-defaulturl">defaultURL</a></code> = value of the default URL, if stored by the CDM.
</li></ul>
</li>
</ol>
@@ -1173,7 +1174,7 @@
<code><a href="#dom-keysystem">keySystem</a></code> = <code>"org.w3.clearkey"</code><br>
<code><a href="#dom-sessionid">sessionId</a></code> = a unique numerical string<br>
<code><a href="#dom-message">message</a></code> = a container-specific unique key identifier extracted from the <var title="true">initData</var> parameter (if <var title="true">initData</var> was and null one could not be extracted; otherwise null)<br>
- <code><a href="#dom-defaulturl">defaultUrl</a></code> = value of the default URL if present in the <a href="http://dev.w3.org/html5/spec/video.html#media-data">media data</a> and null otherwise.
+ <code><a href="#dom-defaulturl">defaultURL</a></code> = value of the default URL if present in the <a href="http://dev.w3.org/html5/spec/video.html#media-data">media data</a> and null otherwise.
</li></ul>
<p>To provide a key using this Key System, pass the following to <code><a href="#dom-addkey">addKey()</a></code>:</p>
@@ -1532,7 +1533,7 @@
<p>It is an open question whether CDMs should</p>
<ul>
<li>Use <code><a href="#dom-keymessage">keymessage</a></code> to continue the current session</li>
- <li>OR start a new message exchange procedes in exactly the same way as the initial message exchange, with the exception that the <a href="#key-system">Key System</a>and <a href="#session-id">Session ID</a> are known when the needley event is sent.</li>
+ <li>OR start a new message exchange procedes in exactly the same way as the initial message exchange, with the exception that the <a href="#key-system">Key System</a> and <a href="#session-id">Session ID</a> are known when the <code><a href="#dom-needkey">needkey</a></code> event is sent.</li>
</ul>
The latter option may impact the <code><a href="#dom-mediakeyneededevent">MediaKeyNeededEvent</a></code> definition. See the <a href="#issue-multiple-keys">related issue</a>.
</div>
@@ -1765,12 +1766,12 @@
[Constructor(DOMString type, optional <a href="#dom-mediakeymessageeventinit">MediaKeyMessageEventInit</a> eventInitDict)]
interface <dfn id="dom-alternate-oomediakeymessageevent">MediaKeyMessageEvent</dfn> : <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event">Event</a> {
readonly attribute Uint8Array <a href="#dom-message">message</a>;
- readonly attribute DOMString? <a href="#dom-defaulturl">defaultUrl</a>;
+ readonly attribute DOMString? <a href="#dom-defaulturl">defaultURL</a>;
};
dictionary <dfn id="dom-alternate-oomediakeymessageeventinit">MediaKeyMessageEventInit</dfn> : <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#eventinit">EventInit</a> {
Uint8Array <a href="#dom-message">message</a>;
- DOMString? <a href="#dom-defaulturl">defaultUrl</a>;
+ DOMString? <a href="#dom-defaulturl">defaultURL</a>;
};</pre>
<p>Note that in the <code><a href="#dom-mediakeysession">MediaKeySession</a></code> interface, <code><a href="#dom-sessionid">sessionId</a></code> is guaranteed to be initialized only after the first <code><a href="#dom-mediakeymessageevent">MediaKeyMessageEvent</a></code>.</p>
@@ -1858,7 +1859,11 @@
</thead>
<tbody>
<tr>
- <td>0.1</td>
+ <td><a href="http://dvcs.w3.org/hg/html-media/raw-file/eme-v0.1a/encrypted-media/encrypted-media.html">0.1a</a></td>
+ <td>Corrects minor mistakes in 0.1.</td>
+ </tr>
+ <tr>
+ <td><a href="http://dvcs.w3.org/hg/html-media/raw-file/eme-v0.1/encrypted-media/encrypted-media.html">0.1</a></td>
<td>Initial Proposal</td>
</tr>
</tbody>
--- a/encrypted-media/encrypted-media.xml Thu Jun 28 17:27:15 2012 -0700
+++ b/encrypted-media/encrypted-media.xml Thu Jun 28 17:47:28 2012 -0700
@@ -35,7 +35,7 @@
<div class="head">
<p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" width="72" height="48" /></a></p>
<h1>Encrypted Media Extensions</h1>
- <h2>W3C Editor's Draft 27 June 2012</h2>
+ <h2>W3C Editor's Draft 28 June 2012</h2>
<dl>
<dt>Latest editor's draft:</dt>
<dd><a href="http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html">http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html</a></dd>
@@ -108,8 +108,8 @@
<li><a href="#key-release">4. Key Release</a></li>
<li><a href="#algorithms">5. Algorithms</a></li>
<li><ul style="list-style-type:none">
- <li><a href="#algorithms-enrypted-block">5.1. Potentially Encrypted Stream Encountered</a></li>
- <li><a href="#algorithms-encrypted-stream">5.2. Potentially encrypted stream encountered</a></li>
+ <li><a href="#algorithms-enrypted-block">5.1. Encrypted Block Encountered</a></li>
+ <li><a href="#algorithms-encrypted-stream">5.2. Potentially Encrypted Stream Encountered</a></li>
<li><a href="#algorithms-load">5.3. Addition to Media Element Load Algorithm</a></li>
</ul></li>
<li><a href="#simple-decryption">6. Simple Decryption</a></li>
@@ -160,6 +160,7 @@
</ul>
<h3 id="definitions">1.2. Definitions</h3>
+ <p>Text in <span class="non-normative">this font and color</span> is non-normative.</p>
<h4 id="cdm">1.2.1. Content Decryption Module (CDM)</h4>
<non-normative-section/>
@@ -180,7 +181,7 @@
<span class="non-normative">For example, "com.example.somesystem.1" and "com.example.somesystem.1_5".</span>
<span class="non-normative">Key system providers should keep in mind that these will be used for comparison and discovery, so they should be easy to compare and the structure should remain reasonably simple.</span>
</p>
- <p class="issue">It may make sense to provide informal guidelines to avoid these diverging too much. There are probably best practices too. Should platform-specific or <a href="#faq-provider-capabilities">protection capability information</a> be contained in these strings?)</p>
+ <p class="issue">It may make sense to provide informal guidelines to avoid these diverging too much. There are probably best practices too. Should platform-specific or <a href="#faq-provider-capabilities">protection capability information</a> be contained in these strings?</p>
<p>If a user agent returns "maybe" or "probably" for any subsystem string, it must return "maybe" when a parent system string is passed to <methodref>canPlayType</methodref>.
<span class="non-normative">For example, if a user agent returns "maybe" or "probably" for "com.example.somesystem.1_5", it must return "maybe" for "com.example.somesystem".</span>
@@ -238,7 +239,7 @@
<pre class="idl">
partial interface <precodedfn>HTMLMediaElement</precodedfn> {
- // No API changes. 'type' string is extended.
+ // Adds optional 'keySystem' parameter.
DOMString <premethodref>canPlayType</premethodref>(in DOMString type, in DOMstring? <a href="#key-system">keySystem</a>);
void <premethodref>generateKeyRequest</premethodref>(in DOMString <a href="#key-system">keySystem</a>, in Uint8Array? initData);
@@ -317,7 +318,7 @@
<ol>
<li><p>Load <var title="true">handler</var> if necessary.</p></li>
<!-- Everything above here should be the same for all methods. -->
- <li><p>Let <var title="true">defaultUrl</var> be null.</p></li>
+ <li><p>Let <var title="true">defaultURL</var> be null.</p></li>
<li><p>Use <var title="true">handler</var> to generate a key request and follow the steps for the first matching condition from the following list:</p>
<dl class="switch">
<dt>If a request is successfully generated</dt>
@@ -326,7 +327,7 @@
<li><p>Let <var title="true">key request</var> be a key request generated by the <a href="#cdm">CDM</a> using <var title="true">initData</var>, if provided.</p>
<p>Note: <var title="true">handler</var> must not use any data, including <videoanchor name="media-data">media data</videoanchor>, not provided via <var title="true">initData</var>.</p>
</li>
- <li><p>If <var title="true">initData</var> is not null and contains a default URL for <var title="true">keySystem</var>, let <var title="true">defaultUrl</var> be that URL.</p></li>
+ <li><p>If <var title="true">initData</var> is not null and contains a default URL for <var title="true">keySystem</var>, let <var title="true">defaultURL</var> be that URL.</p></li>
</ol>
</dd>
<dt>Otherwise</dt>
@@ -348,7 +349,7 @@
<coderef>keySystem</coderef> = <var title="true">keySystem</var><br></br>
<coderef>sessionId</coderef> = <var title="true">sessionId</var><br></br>
<coderef>message</coderef> = <var title="true">key request</var><br></br>
- <coderef>defaultUrl</coderef> = <var title="true">defaultUrl</var>
+ <coderef>defaultURL</coderef> = <var title="true">defaultURL</var>
</li></ul>
<p class="non-normative">Note: <coderef>message</coderef> may be a request for multiple keys, depending on the <var title="true"><a href="#key-system">keySystem</a></var> and/or <var title="true">initData</var>. This is transparent to the application.</p>
</li>
@@ -473,7 +474,7 @@
<coderef>keySystem</coderef> = <var title="true">keySystem</var><br></br>
<coderef>sessionId</coderef> = <var title="true">sessionId</var><br></br>
<coderef>message</coderef> = <var title="true">next message</var><br></br>
- <coderef>defaultUrl</coderef> = null
+ <coderef>defaultURL</coderef> = null
<p class="issue">Is there a reason that this cannot be null?</p>
</li></ul>
</dd>
@@ -567,7 +568,7 @@
It seems that except for #1, which should only occur in applications that do not support encrypted media, these are all application bugs and not something that would improve the user experience.
Any unique handling of the error codes by an application would essentially be describing a bug type.
Unique codes might be helpful in tracking down the cause of the bug, but there are probably other options.
- It is also possible that some of these cases should be reported via <coderef>MediaKeyErrorEventInit</coderef>.
+ It is also possible that some of these cases should be reported via <coderef>MediaKeyErrorEvent</coderef>.
</p>
<p>A <coderef>MediaKeyError</coderef> may be one of the following:</p>
@@ -613,14 +614,14 @@
readonly attribute DOMString <precoderef>keySystem</precoderef>;
readonly attribute DOMString? <precoderef>sessionId</precoderef>;
readonly attribute Uint8Array <precoderef>message</precoderef>;
- readonly attribute DOMString? <precoderef>defaultUrl</precoderef>;
+ readonly attribute DOMString? <precoderef>defaultURL</precoderef>;
};
dictionary <precodedfn>MediaKeyMessageEventInit</precodedfn> : <dom4ref name="eventinit">EventInit</dom4ref> {
DOMString <precoderef>keySystem</precoderef>;
DOMString? <precoderef>sessionId</precoderef>;
Uint8Array <precoderef>message</precoderef>;
- DOMString? <precoderef>defaultUrl</precoderef>;
+ DOMString? <precoderef>defaultURL</precoderef>;
};</pre>
<pre class="idl">
@@ -668,7 +669,7 @@
<dd>
<p>Returns the message <span class="non-normative">(i.e. key request)</span> to send.</p>
</dd>
- <dt><var title="">event</var> . <coderef>defaultUrl</coderef></dt>
+ <dt><var title="">event</var> . <coderef>defaultURL</coderef></dt>
<dd>
<p>Returns the default key exchange URL.</p>
</dd>
@@ -688,7 +689,7 @@
<p>The <codedfn>sessionId</codedfn> attribute is the <a href="#session-id">Session ID</a> for the key or license that this event refers to. It may be null.</p>
<p>The <codedfn>initData</codedfn> attribute contains <a href="#initialization-data">Initialization Data</a> specific to the event.</p>
<p>The <codedfn>message</codedfn> attribute contains a message from the CDM. Messages are Key System-specific. <span class="non-normative">In most cases, it should be sent to a key server.</span></p>
- <p>The <codedfn>defaultUrl</codedfn> is the default URL to send the key request to as provided by the <videoanchor name="media-data">media data</videoanchor>. It may be null.</p>
+ <p>The <codedfn>defaultURL</codedfn> is the default URL to send the key request to as provided by the <videoanchor name="media-data">media data</videoanchor>. It may be null.</p>
<p>The <codedfn>errorCode</codedfn> attribute contains the <coderef>MediaKeyError</coderef> code for the error that occurred.</p>
<p>The <codedfn>systemCode</codedfn> attribute contains a <a href="#key-system">Key System</a>-dependent status code for the error that occurred.
<span class="non-normative">This allows a more granular status to be returned than the more general <coderef>errorCode</coderef>.</span>
@@ -817,7 +818,7 @@
<coderef>keySystem</coderef> = <var title="true">keySystem</var><br></br>
<coderef>sessionId</coderef> = the sessionId originally associated with the provision of the key<br></br>
<coderef>message</coderef> = <var title="true">key release message</var><br></br>
- <coderef>defaultUrl</coderef> = value of the default URL, if stored by the CDM.
+ <coderef>defaultURL</coderef> = value of the default URL, if stored by the CDM.
</li></ul>
</li>
</ol>
@@ -1096,7 +1097,7 @@
<coderef>keySystem</coderef> = <code>"org.w3.clearkey"</code><br></br>
<coderef>sessionId</coderef> = a unique numerical string<br></br>
<coderef>message</coderef> = a container-specific unique key identifier extracted from the <var title="true">initData</var> parameter (if <var title="true">initData</var> was and null one could not be extracted; otherwise null)<br></br>
- <coderef>defaultUrl</coderef> = value of the default URL if present in the <videoanchor name="media-data">media data</videoanchor> and null otherwise.
+ <coderef>defaultURL</coderef> = value of the default URL if present in the <videoanchor name="media-data">media data</videoanchor> and null otherwise.
</li></ul>
<p>To provide a key using this Key System, pass the following to <methodref>addKey</methodref>:</p>
@@ -1447,7 +1448,7 @@
<p>It is an open question whether CDMs should</p>
<ul>
<li>Use <coderef>keymessage</coderef> to continue the current session</li>
- <li>OR start a new message exchange procedes in exactly the same way as the initial message exchange, with the exception that the <a href="#key-system">Key System</a>and <a href="#session-id">Session ID</a> are known when the needley event is sent.</li>
+ <li>OR start a new message exchange procedes in exactly the same way as the initial message exchange, with the exception that the <a href="#key-system">Key System</a> and <a href="#session-id">Session ID</a> are known when the <coderef>needkey</coderef> event is sent.</li>
</ul>
The latter option may impact the <coderef>MediaKeyNeededEvent</coderef> definition. See the <a href="#issue-multiple-keys">related issue</a>.
</div>
@@ -1679,12 +1680,12 @@
[Constructor(DOMString type, optional <precoderef>MediaKeyMessageEventInit</precoderef> eventInitDict)]
interface <precodedfn prefix="alternate-oo">MediaKeyMessageEvent</precodedfn> : <dom4ref name="event">Event</dom4ref> {
readonly attribute Uint8Array <precoderef>message</precoderef>;
- readonly attribute DOMString? <precoderef>defaultUrl</precoderef>;
+ readonly attribute DOMString? <precoderef>defaultURL</precoderef>;
};
dictionary <precodedfn prefix="alternate-oo">MediaKeyMessageEventInit</precodedfn> : <dom4ref name="eventinit">EventInit</dom4ref> {
Uint8Array <precoderef>message</precoderef>;
- DOMString? <precoderef>defaultUrl</precoderef>;
+ DOMString? <precoderef>defaultURL</precoderef>;
};</pre>
<p>Note that in the <coderef>MediaKeySession</coderef> interface, <coderef>sessionId</coderef> is guaranteed to be initialized only after the first <coderef>MediaKeyMessageEvent</coderef>.</p>
@@ -1772,7 +1773,11 @@
</thead>
<tbody>
<tr>
- <td>0.1</td>
+ <td><a href="http://dvcs.w3.org/hg/html-media/raw-file/eme-v0.1a/encrypted-media/encrypted-media.html">0.1a</a></td>
+ <td>Corrects minor mistakes in 0.1.</td>
+ </tr>
+ <tr>
+ <td><a href="http://dvcs.w3.org/hg/html-media/raw-file/eme-v0.1/encrypted-media/encrypted-media.html">0.1</a></td>
<td>Initial Proposal</td>
</tr>
</tbody>