--- a/encrypted-media/encrypted-media-respec.html	Fri Oct 10 14:40:15 2014 -0700
+++ b/encrypted-media/encrypted-media-respec.html	Fri Oct 10 14:40:35 2014 -0700
@@ -119,9 +119,6 @@
     .domintro:before { display: table; margin: -1em -0.5em -0.5em auto; width: auto; content: 'This box is non-normative. Implementation requirements are given below this box.'; color: black; font-style: italic; border: solid 2px; background: white; padding: 0 0.25em; }
     </style>
     <style type="text/css">
-      div.nonnormative { color: green; margin: 2em 0 2em 0em; padding: 0.5em 1em; border: none; background: #DDFFDD; }
-      .nonnormative:before { display: table; margin: -1em -0.5em -0.5em auto; width: auto; content: 'This section is non-normative.'; color: black; font-style: italic; border: solid 2px; background: white; padding: 0 0.25em; }
-
       <!-- For inline non-normative text. -->
       .non-normative { font-style: italic; color: DarkSlateGrey; }
       .non-normative em { font-style: normal;}
@@ -159,9 +156,8 @@
     </section>
 
     <!-- TODO: Indent the contents of each <section>. --> 
-    <section id="introduction">
+    <section id="introduction" class="informative">
     <h2>Introduction</h2>
-    <non-normative-section/>
     <p>
       This proposal allows JavaScript to select content protection mechanisms, control license/key exchange, and implement custom license management algorithms.
       It supports a wide range of use cases without requiring client-side modifications in each user agent for each use case.
@@ -813,9 +809,8 @@
     </div>
     </section>
 
-    <section id="mediakeysession-events">
+    <section id="mediakeysession-events" class="informative">
     <h3>Event Summary</h3>
-    <non-normative-section/>
 
     <p>Note: In some implementations, <coderef>MediaKeySession</coderef> objects may not fire any events until the <coderef>MediaKeys</coderef> object is associated with a media element using <methodref>setMediaKeys</methodref>.</p>
 
@@ -1099,9 +1094,8 @@
     </div>
     </section>
 
-    <section id="htmlmediaelement-events">
+    <section id="htmlmediaelement-events" class="informative">
     <h3>Event Summary</h3>
-    <non-normative-section/>
 
     <table>
       <thead>
@@ -1294,9 +1288,8 @@
     </section>
     </section>
 
-    <section id="media-element-restictions">
+    <section id="media-element-restictions" class="informative">
     <h3>Media Element Restrictions</h3>
-    <non-normative-section/>
     <p>Media data processed by a CDM may not be available through Javascript APIs in the usual way (for example using the CanvasRenderingContext2D drawImage() method and the AudioContext MediaElementAudioSourceNode).
     This specification does not define conditions for such non-availability of media data, however, if media data is not available to Javascript APIs then these APIs may behave as if no media data was present at all.</p>
     <p>Where media rendering is not performed by the UA, for example in the case of a hardware protected media pipeline, then the full set of HTML rendering capabilities, for example CSS Transforms, may not be available. One likely restriction is that
@@ -1373,10 +1366,8 @@
       Applications may decode the contents of the ArrayBuffer 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"> -->
-    <section id="clear-key-request-format-example">
+    <section id="clear-key-request-format-example" class="informative">
     <h5>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">
 {
@@ -1418,10 +1409,8 @@
       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"> -->
-    <section id="clear-key-license-format-example">
+    <section id="clear-key-license-format-example" class="informative">
     <h5>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">
 {
@@ -1437,10 +1426,8 @@
     </section>
     </section>
 
-    <!-- Will be <section class="informative"> -->
-    <section id="using-base64url">
+    <section id="using-base64url" class="informative">
     <h4>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>
@@ -1449,9 +1436,8 @@
     </section>
 
 
-    <section id="security">
+    <section id="security" class="informative">
     <h2>Security Considerations</h2>
-    <div class="nonnormative">
 
     <p>User Agent and Key System implementations must consider <videoanchor name="media-data">media data</videoanchor>, <a href="#initialization-data">Initialization Data</a>, responses (i.e. data passed to <methodref>update</methodref>), licenses, key data, and all other data provided by the application as untrusted content and potential attack vectors.
     They must use appropriate safeguards to mitigate any associated threats and take care to safely parse, decrypt, etc. such data.
@@ -1478,9 +1464,8 @@
     </section>
 
 
-    <section id="privacy">
+    <section id="privacy" class="informative">
     <h2>Privacy Considerations</h2>
-    <div class="nonnormative">
 
     <p>The presence or use of Key Systems on a user's device raises a number of privacy issues, falling into two categories: (a) user-specific information that may be disclosed by the EME interface itself, or within messages from Key Systems and (b) user-specific information that may be persistently stored on the users device.</p>
     <p>User Agents should take responsibility for providing users with adequate control over their own privacy. Since User Agents may integrate with third party CDM implementations, CDM implementers must provide sufficient information and controls to user agent implementers to enable them to implement appropriate techniques to ensure users have control over their privacy, including but not limited to the techniques described below.</p>
@@ -1608,9 +1593,8 @@
     </div>
     </section>
 
-    <section id="examples">
+    <section id="examples" class="informative">
     <h2>Examples</h2>
-    <non-normative-sections/>
     <p>This section contains example solutions for various use cases using the proposed extensions.
     These are not the only solutions to these use cases.
     Video elements are used in the examples, but the same would apply to all <a href="#media-element">media element</a>s.

--- a/encrypted-media/spec-html.xsl	Fri Oct 10 14:40:15 2014 -0700
+++ b/encrypted-media/spec-html.xsl	Fri Oct 10 14:40:35 2014 -0700
@@ -120,12 +120,4 @@
     <a><xsl:attribute name="href">http://www.w3.org/TR/html5/infrastructure.html#cors-same-origin</xsl:attribute>CORS-same-origin</a>
   </xsl:template>
 
-  <xsl:template match="//non-normative-section">
-    <p><i>This section is non-normative.</i></p>
-  </xsl:template>
-
-  <xsl:template match="//non-normative-sections">
-    <p><i>This section and its subsections are non-normative.</i></p>
-  </xsl:template>
-
 </xsl:stylesheet>