[html5] r2883 - [e] (0) Integrate the specs together a bit more, fix some legacy issues.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-03-20 01:52:31 -0700 (Fri, 20 Mar 2009)
New Revision: 2883

Modified:
   source
Log:
[e] (0) Integrate the specs together a bit more, fix some legacy issues.

Modified: source
===================================================================
--- source	2009-03-20 08:36:31 UTC (rev 2882)
+++ source	2009-03-20 08:52:31 UTC (rev 2883)
@@ -58199,101 +58199,9 @@
   <p><a href="http://www.whatwg.org/demos/workers/crypto/page.html">View this example online</a>.</p>
 
 
+  <!--BOILERPLATE middle-w3c-api-intro-->
 
-  <h4>Conformance requirements</h4>
 
-  <p>All diagrams, examples, and notes in this specification are
-  non-normative, as are all sections explicitly marked non-normative.
-  Everything else in this specification is normative.</p>
-
-  <p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
-  NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
-  "OPTIONAL" in the normative parts of this document are to be
-  interpreted as described in RFC2119. For readability, these words do
-  not appear in all uppercase letters in this specification. <a
-  href="#refsRFC2119">[RFC2119]</a></p>
-
-  <p>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.</p>
-
-  <p>Some conformance requirements are phrased as requirements on
-  attributes, methods or objects. Such requirements are to be
-  interpreted as requirements on user agents.</p>
-
-  <p>Conformance requirements phrased as algorithms or specific steps
-  may be implemented in any manner, so long as the end result is
-  equivalent. (In particular, the algorithms defined in this
-  specification are intended to be easy to follow, and not intended to
-  be performant.)</p>
-
-  <p>The only conformance class defined by this specification is user
-  agents.</p>
-
-  <p>User agents may impose implementation-specific limits on
-  otherwise unconstrained inputs, e.g. to prevent denial of service
-  attacks, to guard against running out of memory, or to work around
-  platform-specific limitations.</p>
-
-
-  <h5>Dependencies</h5>
-
-  <p>This specification relies on several other underlying
-  specifications.</p>
-
-  <dl>
-
-   <dt>HTML5</dt>
-
-   <dd>
-
-    <p>Many fundamental concepts from HTML5 are used by this
-    specification. <a href="#refsHTML5">[HTML5]</a></p>
-
-   </dd>
-
-   <dt>ECMAScript</dt>
-
-   <dd>
-
-    <p>This specification is intended to be used with JavaScript as
-    the scripting language. <a href="#refsJS">[JS]</a></p>
-
-   </dd>
-
-   <dt>WebIDL</dt>
-
-   <dd>
-
-    <p>The IDL blocks in this specification use the semantics of the
-    WebIDL specification. <a href="#refsWebIDL">[WebIDL]</a></p>
-
-   </dd>
-
-  </dl>
-
-
-  <h4>Terminology</h4>
-
-  <p>The construction "a <code title="">Foo</code> object", where
-  <code title="">Foo</code> is actually an interface, is sometimes
-  used instead of the more accurate "an object implementing the
-  interface <code title="">Foo</code>".</p>
-
-  <p>The term DOM is used to refer to the API set made available to
-  scripts in Web applications, and does not necessarily imply the
-  existence of an actual <code>Document</code> object or of any other
-  <code>Node</code> objects as defined in the DOM Core
-  specifications. <a href="#refsDOM3CORE">[DOM3CORE]</a></p>
-
-  <p>A DOM attribute is said to be <em>getting</em> when its value is
-  being retrieved (e.g. by author script), and is said to be
-  <em>setting</em> when a new value is assigned to it.</p>
-
-
-
   <h3>Infrastructure</h3>
 
   <p>There are two kinds of workers; dedicated workers, and shared
@@ -59157,7 +59065,7 @@
        attribute represents an <span>absolute URL</span> that is not
        exactly equal to the resulting <span>absolute URL</span>, then
        throw a <code>URL_MISMATCH_ERR</code> exception and abort all
-       these steps. <span class="big-issue">code 21</span></p></li>
+       these steps. <span class="XXX">code 21</span></p></li>
 
        <li><p>Associate <var title="">worker</var> with <var
        title="">worker global scope</var>.</p></li>
@@ -59260,7 +59168,7 @@
   interface provides the <code title="">setTimeout()</code> method and
   its friends.)</p>
 
-  <p class="big-issue">Need to define a sync database API.</p>
+  <p class="XXX">Need to define a sync database API.</p>
 
   <!-- XXX ApplicationCache -->