Move conventions and conformance to appendices (#167)

Author: domenic

index.bs

@@ -290,119 +290,6 @@ have been written in prose.  In addition, precise language bindings
 for ECMAScript Edition 6 are given.
 
 
-<h3 id="conventions">Typographic conventions</h3>
-
-The following typographic conventions are used in this document:
-
-*   Defining instances of terms: <dfn id="dfn-example-term">example term</dfn>
-*   Links to terms defined in this document or elsewhere: [=example term=]
-*   Grammar terminals: <emu-t>sometoken</emu-t>
-*   Grammar non-terminals: <emu-nt>ExampleGrammarNonTerminal</emu-t>
-*   Grammar symbols: <emu-t class="symbol">identifier</emu-t>
-*   IDL and ECMAScript types: <code class="idl">ExampleType</code>
-*   Code snippets: <code>a = b + obj.f()</code>
-*   Unicode characters: <span class="char">U+0030 DIGIT ZERO ("0")</span>
-*   Extended attributes: [<code class="idl">ExampleExtendedAttribute</code>]
-*   Variable names in prose and algorithms: |exampleVariableName|.
-*   Algorithms use the [=conventions of the ECMAScript specification=],
-    including the ! and ? notation for unwrapping completion records.
-*   IDL informal syntax examples:
-    <pre highlight="webidl" class="syntax">
-        interface identifier {
-          <mark>/* interface_members... */</mark>
-        };
-    </pre>
-
-    (Specific parts of the syntax discussed in surrounding prose are <mark>highlighted</mark>.)
-*   IDL grammar snippets:
-    <pre class="grammar no-index">
-        ExampleGrammarNonTerminal :
-            OtherNonTerminal "sometoken"
-            other AnotherNonTerminal
-            ε  // nothing
-    </pre>
-*   Non-normative notes:
-
-    Note: This is a note.
-
-*   Non-normative examples:
-    <div class="example">
-        This is an example.
-    </div>
-*   Normative warnings:
-    <p class="advisement">
-        This is a warning.
-    </p>
-*   Code blocks:
-    <pre highlight="webidl">
-        // This is an IDL code block.
-        interface Example {
-          attribute long something;
-        };
-    </pre>
-    <pre highlight="js">
-        // This is an ECMAScript code block.
-        window.onload = function() { window.alert("loaded"); };
-    </pre>
-
-
-<h2 id="conformance">Conformance</h2>
-
-Everything in this specification is normative except for diagrams,
-examples, notes and sections marked as being informative.
-
-The keywords “must”,
-“must not”,
-“required”,
-“shall”,
-“shall not”,
-“should”,
-“should not”,
-“recommended”,
-“may” and
-“optional” in this document are to be
-interpreted as described in
-<cite><a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to
-Indicate Requirement Levels</a></cite>
-[[!RFC2119]].
-
-The following conformance classes are defined by this specification:
-
- :  <dfn id="dfn-conforming-set-of-idl-fragments" export>conforming set of IDL fragments</dfn>
- :: A set of [=IDL fragments=] is considered
-    to be a [=conforming set of IDL fragments=] if, taken together, they satisfy all of the
-    must-,
-    required- and shall-level
-    criteria in this specification that apply to IDL fragments.
- :  <dfn id="dfn-conforming-implementation" export>conforming implementation</dfn>
- :: A user agent is considered to be a
-    [=conforming implementation=]
-    relative to a [=conforming set of IDL fragments=] if it satisfies all of the must-,
-    required- and shall-level
-    criteria in this specification that apply to implementations for all language
-    bindings that the user agent supports.
- :  <dfn id="dfn-conforming-ecmascript-implementation" export>conforming ECMAScript implementation</dfn>
- :: A user agent is considered to be a
-    [=conforming ECMAScript implementation=]
-    relative to a [=conforming set of IDL fragments=] if it satisfies all of the must-,
-    required- and shall-level
-    criteria in this specification that apply to implementations for the ECMAScript
-    language binding.
-
-
-<h3 id="conformant-algorithms">Conformant Algorithms</h3>
-
-Requirements phrased in the imperative as part of algorithms (such as
-“strip any leading space characters” or “return false and abort these
-steps”) are to be interpreted with the meaning of the key word (“must”,
-“should”, “may”, etc) used in introducing the algorithm.
-
-Conformance requirements phrased as algorithms or specific steps can be
-implemented in any manner, so long as the end result is <dfn lt="processing equivalence" id="dfn-processing-equivalence">equivalent</dfn>. In
-particular, the algorithms defined in this specification are intended to
-be easy to understand and are not intended to be performant. Implementers
-are encouraged to optimize.
-
 
 <h2 id="idl">Interface definition language</h2>
 
@@ -13514,6 +13401,117 @@ defined in this specification — see
 [[#idl-extended-attributes]]
 for the syntaxes that are used by these extended attributes.
 
+
+<h2 id="conventions" class="no-num">Document conventions</h3>
+
+The following typographic conventions are used in this document:
+
+*   Defining instances of terms: <dfn id="dfn-example-term">example term</dfn>
+*   Links to terms defined in this document or elsewhere: [=example term=]
+*   Grammar terminals: <emu-t>sometoken</emu-t>
+*   Grammar non-terminals: <emu-nt>ExampleGrammarNonTerminal</emu-t>
+*   Grammar symbols: <emu-t class="symbol">identifier</emu-t>
+*   IDL and ECMAScript types: <code class="idl">ExampleType</code>
+*   Code snippets: <code>a = b + obj.f()</code>
+*   Unicode characters: <span class="char">U+0030 DIGIT ZERO ("0")</span>
+*   Extended attributes: [<code class="idl">ExampleExtendedAttribute</code>]
+*   Variable names in prose and algorithms: |exampleVariableName|.
+*   Algorithms use the [=conventions of the ECMAScript specification=],
+    including the ! and ? notation for unwrapping completion records.
+*   IDL informal syntax examples:
+    <pre highlight="webidl" class="syntax">
+        interface identifier {
+          <mark>/* interface_members... */</mark>
+        };
+    </pre>
+
+    (Specific parts of the syntax discussed in surrounding prose are <mark>highlighted</mark>.)
+*   IDL grammar snippets:
+    <pre class="grammar no-index">
+        ExampleGrammarNonTerminal :
+            OtherNonTerminal "sometoken"
+            other AnotherNonTerminal
+            ε  // nothing
+    </pre>
+*   Non-normative notes:
+
+    Note: This is a note.
+
+*   Non-normative examples:
+    <div class="example">
+        This is an example.
+    </div>
+*   Normative warnings:
+    <p class="advisement">
+        This is a warning.
+    </p>
+*   Code blocks:
+    <pre highlight="webidl">
+        // This is an IDL code block.
+        interface Example {
+          attribute long something;
+        };
+    </pre>
+    <pre highlight="js">
+        // This is an ECMAScript code block.
+        window.onload = function() { window.alert("loaded"); };
+    </pre>
+
+
+<h2 id="conformance" class="no-num" oldids="conformant-algorithms">Conformance</h2>
+
+Everything in this specification is normative except for diagrams,
+examples, notes and sections marked as being informative.
+
+The keywords “must”,
+“must not”,
+“required”,
+“shall”,
+“shall not”,
+“should”,
+“should not”,
+“recommended”,
+“may” and
+“optional” in this document are to be
+interpreted as described in
+<cite><a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to
+Indicate Requirement Levels</a></cite>
+[[!RFC2119]].
+
+Requirements phrased in the imperative as part of algorithms (such as
+“strip any leading space characters” or “return false and abort these
+steps”) are to be interpreted with the meaning of the key word (“must”,
+“should”, “may”, etc) used in introducing the algorithm.
+
+Conformance requirements phrased as algorithms or specific steps can be
+implemented in any manner, so long as the end result is <dfn lt="processing equivalence" id="dfn-processing-equivalence">equivalent</dfn>. In
+particular, the algorithms defined in this specification are intended to
+be easy to understand and are not intended to be performant. Implementers
+are encouraged to optimize.
+
+The following conformance classes are defined by this specification:
+
+ :  <dfn id="dfn-conforming-set-of-idl-fragments" export>conforming set of IDL fragments</dfn>
+ :: A set of [=IDL fragments=] is considered
+    to be a [=conforming set of IDL fragments=] if, taken together, they satisfy all of the
+    must-,
+    required- and shall-level
+    criteria in this specification that apply to IDL fragments.
+ :  <dfn id="dfn-conforming-implementation" export>conforming implementation</dfn>
+ :: A user agent is considered to be a
+    [=conforming implementation=]
+    relative to a [=conforming set of IDL fragments=] if it satisfies all of the must-,
+    required- and shall-level
+    criteria in this specification that apply to implementations for all language
+    bindings that the user agent supports.
+ :  <dfn id="dfn-conforming-ecmascript-implementation" export>conforming ECMAScript implementation</dfn>
+ :: A user agent is considered to be a
+    [=conforming ECMAScript implementation=]
+    relative to a [=conforming set of IDL fragments=] if it satisfies all of the must-,
+    required- and shall-level
+    criteria in this specification that apply to implementations for the ECMAScript
+    language binding.
+
 <script>
     // Grammar
     (function() {