[EME] Fix typos in keyids page.
--- a/encrypted-media/keyids-format-respec.html Mon Jun 02 15:39:29 2014 -0700
+++ b/encrypted-media/keyids-format-respec.html Mon Jun 02 16:00:28 2014 -0700
@@ -14,7 +14,7 @@
shortName: "encrypted-media", <!-- The registry does not have its own short name. -->
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/cenc-format.html",
+ edDraftURI: "http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/keyids-format.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -69,12 +69,12 @@
</p>
<p>Unlike other similar specifications, this one does not document a stream format or behavior related to processing media data. This type and format are not used in the <a href="encrypted-media.html#algorithms-initdata-encountered">Initialization Data Encountered</a> algorithm.</p>
</section>
-
+
<section id="sotd">
<p>The Working Group maintains <a href="http://w3.org/brief/MjY5">a list of all bug reports that the editors have not yet tried to address</a>.</p>
<p>Implementors should be aware that this specification is not stable. <strong>Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways.</strong> Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should join the mailing list mentioned below and take part in the discussions.</p>
</section>
-
+
<section id="init-data">
<h2>Initialization Data Format</h2>
<p>The format is a JSON object containing the following member:</p>
@@ -82,13 +82,13 @@
<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 Encoding specification [[!encoding]].
- Applications may encode the JSON string using the <a def-id="interface-textencoder"></a> <a def-id="interface-textencoder"></a> [[!encoding]].
+ Applications may encode the JSON string using the <a def-id="interface-textencoder"></a> [[!encoding]].
</p>
-
+
<section class="informative">
<h2>Example</h2>
<p>The following example will generate a license request for two key IDs. (Line breaks are for readability only.)</p>
--- a/encrypted-media/keyids-format.html Mon Jun 02 15:39:29 2014 -0700
+++ b/encrypted-media/keyids-format.html Mon Jun 02 16:00:28 2014 -0700
@@ -201,17 +201,17 @@
</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-31T06:59:12.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-06-03T06:02:05.000Z" id="w3c-editor-s-draft-02-june-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2014-06-02">02 June 2014</time></h2>
<dl>
<dt>This version:</dt>
- <dd><a class="u-url" href="http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/cenc-format.html">http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/cenc-format.html</a></dd>
+ <dd><a class="u-url" href="http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/keyids-format.html">http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/keyids-format.html</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/encrypted-media/">http://www.w3.org/TR/encrypted-media/</a></dd>
<dt>Latest editor's draft:</dt>
- <dd><a href="http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/cenc-format.html">http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/cenc-format.html</a></dd>
+ <dd><a href="http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/keyids-format.html">http://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/keyids-format.html</a></dd>
@@ -331,9 +331,9 @@
</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#init-data" class="tocxref"><span class="secno">1. </span>Initialization Data Format</a><ul class="toc"><li class="tocline"><a href="#example" class="tocxref"><span class="secno">1.1 </span>Example</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">A.1 </span>Normative references</a></li></ul></li></ul></section>
-
+
-
+
<section id="init-data" typeof="bibo:Chapter" resource="#init-data" rel="bibo:Chapter">
<!--OddPage--><h2 aria-level="1" role="heading" id="h2_init-data"><span class="secno">1. </span>Initialization Data Format</h2>
<p>The format is a JSON object containing the following member:</p>
@@ -341,13 +341,13 @@
<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 Encoding specification [<cite><a class="bibref" href="#bib-encoding">encoding</a></cite>].
Applications may encode the JSON string using the <a href="http://www.w3.org/TR/encoding/#interface-textencoder">TextEncoder interface</a> [<cite><a class="bibref" href="#bib-encoding">encoding</a></cite>].
</p>
-
+
<section class="informative" id="example">
<h3 aria-level="2" role="heading" id="h3_example"><span class="secno">1.1 </span>Example</h3><p><em>This section is non-normative.</em></p>
<p>The following example will generate a license request for two key IDs. (Line breaks are for readability only.)</p>