Permalink
Browse files

[e] (0) Make a 'complete' spec of all the bits that WHATWG has worked…

… on.

git-svn-id: http://svn.whatwg.org/webapps@4099 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent b7a9d94 commit c77c835a0b93797b4ffda7035104d0744af06668 @Hixie Hixie committed Oct 9, 2009
Showing with 86,076 additions and 35 deletions.
  1. +85,977 −0 complete.html
  2. BIN images/abstract.png
  3. +4 −0 index
  4. +92 −34 source
  5. +3 −1 vocabs-index
View
85,977 complete.html
85,977 additions, 0 deletions not shown because the diff is too large. Please use a local Git client to view these changes.
View
BIN images/abstract.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
4 index
@@ -75787,6 +75787,9 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<dt id=refsCOOKIES>[COOKIES]</dt>
<!--
+ <dd><cite><a href="http://www.ietf.org/rfc/rfc2109.txt">HTTP State
+ Management Mechanism</a></cite>, D. Kristol, L. Montulli. IETF,
+ February 1997.</dd>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2965.txt">HTTP State Management
Mechanism</a></cite>, D. Kristol, L. Montulli. IETF, October 2000.</dd>
-->
@@ -76797,6 +76800,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<p>Thanks to the many sources that provided inspiration for the
examples used in the specification.</p>
+
<p>Thanks also to the Microsoft blogging community for some ideas,
to the attendees of the W3C Workshop on Web Applications and
Compound Documents for inspiration, to the #mrt crew, the #mrt.no
View
126 source
@@ -1,3 +1,4 @@
+<!--START complete-->
<!--START html5-->
<h3 class="no-num no-toc">Stability</h3>
@@ -50127,21 +50128,22 @@ document.body.appendChild(outer);</pre>
<h3>Microdata vocabularies</h3>
-<!--START vocabs-->
+<!--START vocabs--><!--END complete-->
<h3 class="no-num no-toc">Table of contents</h3>
<!--toc-->
<hr>
<h4>Introduction</h4>
- <p>This specification defines microdata vocabularies. <a
- href="#refsHTML5">[HTML5]</a></p>
+ <p>This specification defines microdata vocabularies.
+ <a href="#refsHTML5">[HTML5]</a></p>
+<!--START complete-->
<h4>vCard</h4>
-<!--END vocabs-->
+<!--END vocabs--><!--END complete-->
<!--START vCard-->
<h4 class="no-num no-toc">Table of contents</h4>
@@ -50153,7 +50155,7 @@ document.body.appendChild(outer);</pre>
<p>This section defines a microdata vocabulary. <a
href="#refsHTML5">[HTML5]</a></p>
-<!--START vocabs-->
+<!--START vocabs--><!--START complete-->
<p>An item with the <span>item type</span> <dfn
title="md-vcard"><code>http://microformats.org/profile/hcard</code></dfn>
@@ -52396,7 +52398,7 @@ END:VCARD</pre>
<h4>vEvent</h4>
<!--END vocabs-->
-<!--START vEvent-->
+<!--START vEvent--><!--END complete-->
<h4 class="no-num no-toc">Table of contents</h4>
<!--toc-->
@@ -52407,7 +52409,7 @@ END:VCARD</pre>
<p>This section defines a microdata vocabulary. <a
href="#refsHTML5">[HTML5]</a></p>
-<!--START vocabs-->
+<!--START vocabs--><!--START complete-->
<p>An item with the <span>item type</span> <dfn
title="md-vevent"><code>http://microformats.org/profile/hcalendar#vevent</code></dfn>
@@ -53367,7 +53369,7 @@ END:VCARD</pre>
<h4>Licensing works</h4>
-<!--END vocabs-->
+<!--END vocabs--><!--END complete-->
<!--START work-->
<h4 class="no-num no-toc">Table of contents</h4>
@@ -53379,7 +53381,7 @@ END:VCARD</pre>
<p>This section defines a microdata vocabulary. <a
href="#refsHTML5">[HTML5]</a></p>
-<!--START vocabs-->
+<!--START vocabs--><!--START complete-->
<p>An item with the <span>item type</span> <dfn
title="md-work"><code>http://n.whatwg.org/work</code></dfn>
@@ -63285,9 +63287,10 @@ NETWORK:
<p>Each site has its own separate storage area.</p>
-
+<!--END complete-->
<!--BOILERPLATE middle-w3c-api-intro-->
<!--BOILERPLATE middle-w3c-js-disclaimer-->
+<!--START complete-->
<h4 id="storage">The API</h4>
@@ -63775,9 +63778,10 @@ prepareDatabase(function(db) {
});
}</pre>
-
+<!--END complete-->
<!--BOILERPLATE middle-w3c-api-intro-->
<!--BOILERPLATE middle-w3c-js-disclaimer-->
+<!--START complete-->
<h4 id="sql">The API</h4>
@@ -71285,10 +71289,10 @@ v2 (well, really v0):
<p><a href="http://www.whatwg.org/demos/workers/crypto/page.html">View this example online</a>.</p>
-
+<!--END complete-->
<!--BOILERPLATE middle-w3c-api-intro-->
<!--BOILERPLATE middle-w3c-js-disclaimer-->
-
+<!--START complete-->
<h3>Infrastructure</h3>
@@ -71458,8 +71462,8 @@ interface <dfn>SharedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span> {
host</span>. The <span>run a worker</span> algorithm takes care of
associating the worker with an <span>application cache</span>.</p>
- <p class="note">The <dfn
- title="dom-SharedWorkerGlobalScope-applicationCache"><code>applicationCache</code></dfn>
+ <p class="note">The <code
+ title="dom-SharedWorkerGlobalScope-applicationCache">applicationCache</code>
attribute returns the <code>ApplicationCache</code> object for the
worker.</p><!-- normative conf criteria is in the appcache section
-->
@@ -72878,9 +72882,9 @@ data: has two lines.
data: This is the third message.</pre>
-
+<!--END complete-->
<!--BOILERPLATE middle-w3c-api-intro-->
-
+<!--START complete-->
<h4>The <code>EventSource</code> interface</h4>
@@ -73551,7 +73555,7 @@ data:&nbsp;test</pre>
<h4>IANA considerations</h4>
- <h3><dfn><code>text/event-stream</code></dfn></h3>
+ <h5><dfn><code>text/event-stream</code></dfn></h5>
<p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p>
@@ -73634,7 +73638,7 @@ data:&nbsp;test</pre>
<code>text/event-stream</code> resources.</p>
- <h3><dfn title="http-last-event-id"><code>Last-Event-ID</code></dfn></h3>
+ <h5><dfn title="http-last-event-id"><code>Last-Event-ID</code></dfn></h5>
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a
@@ -73676,9 +73680,9 @@ data:&nbsp;test</pre>
implement an IRC client without proxying messages through a custom
server.</p>
-
+<!--END complete-->
<!--BOILERPLATE middle-w3c-api-intro-->
-
+<!--START complete-->
<h4>The <code>WebSocket</code> interface</h4>
@@ -73972,7 +73976,11 @@ interface <dfn>WebSocket</dfn> {
traffic in both directions. This is what the Web Socket protocol
provides. Combined with the Web Socket API, it provides an
alternative to HTTP polling for two-way communication from a Web
- page to a remote server. <a href="#refsWSAPI">[WSAPI]</a></p>
+ page to a remote server.
+ <!--END complete-->
+ <a href="#refsWSAPI">[WSAPI]</a>
+ <!--START complete-->
+ </p>
<p>The same technique can be used for a variety of Web applications:
games, stock tickers, multiuser applications with simultaneous
@@ -74127,7 +74135,7 @@ Frame type byte &lt;-------------------------------------.
-
+<!--END complete-->
<!--BOILERPLATE middle-ietf-conformance-->
@@ -74145,6 +74153,7 @@ Frame type byte &lt;-------------------------------------.
handling behaviors will be applied when the string is parsed. <a
href="#refsHTML5">[HTML5]</a></p>
+<!--START complete-->
<h5>Web Socket URLs</h5>
@@ -74470,10 +74479,16 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
<var title="">host</var>, port <var title="">port</var>, with <var
title="">resource name</var> as the path (and possibly query
parameters), then HTTP headers that would be appropriate for that
- information should be sent at this point. <a
- href="#refsRFC2616">[RFC2616]</a> <a
- href="#refsRFC2109">[RFC2109]</a> <a
- href="#refsRFC2965">[RFC2965]</a></p>
+ information should be sent at this point.
+<!--END complete-->
+ <a href="#refsRFC2616">[RFC2616]</a>
+ <a href="#refsRFC2109">[RFC2109]</a>
+ <a href="#refsRFC2965">[RFC2965]</a>
+<!--START complete--><!--END websocket-protocol-->
+ <a href="#refsHTTP">[HTTP]</a>
+ <a href="#refsCOOKIES">[COOKIES]</a>
+<!--START websocket-protocol-->
+ </p>
<p>Each header must be on a line of its own (each ending with a CR
LF sequence). For the purposes of this step, each header must not
@@ -74807,7 +74822,7 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
<dt>If the entry's name is "<code
- title="http-setcookie2">set-cookie</code>" or "<code
+ title="http-setcookie">set-cookie</code>" or "<code
title="http-setcookie2">set-cookie2</code>" or another
cookie-related header name</dt>
@@ -74817,9 +74832,14 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
(and possibly query parameters) <var title="">resource
name</var>, and the scheme <code title="">http</code> if <var
title="">secure</var> is false and <code title="">https</code> if
- <var title="">secure</var> is true. <a
- href="#refsRFC2109">[RFC2109]</a> <a
- href="#refsRFC2965">[RFC2965]</a></p></dd>
+ <var title="">secure</var> is true.
+<!--END complete-->
+ <a href="#refsRFC2109">[RFC2109]</a>
+ <a href="#refsRFC2965">[RFC2965]</a>
+<!--START complete--><!--END websocket-protocol-->
+ <a href="#refsCOOKIES">[COOKIES]</a>
+<!--START websocket-protocol-->
+ </p></dd>
<dt>Any other name</dt>
@@ -74906,7 +74926,13 @@ multi-origin semantics described in [ORIGIN] applying. (http-origin)
header in HTTP, and then close the connection (if the server has
not already done so) and jump back to the step labeled
<i>connect</i>, including the relevant authentication headers in
- the new request. <a href="#refsRFC2616">[RFC2616]</a></p></dd>
+ the new request.
+<!--END complete-->
+ <a href="#refsRFC2616">[RFC2616]</a>
+<!--START complete--><!--END websocket-protocol-->
+ <a href="#refsHTTP">[HTTP]</a>
+<!--START websocket-protocol-->
+ </p></dd>
<dt>Any other name</dt>
@@ -75364,7 +75390,14 @@ multi-origin semantics described in [ORIGIN] applying. (http-origin)
<dt>URI scheme syntax.</dt>
<dd>
- <p>In ABNF terms using the terminals from the URI specifications: <a href="#refsRFC5234">[RFC5234]</a> <a href="#refsRFC3986">[RFC3986]</a></p>
+ <p>In ABNF terms using the terminals from the URI specifications:
+<!--END complete-->
+ <a href="#refsRFC5234">[RFC5234]</a>
+<!--START complete--><!--END websocket-protocol-->
+ <a href="#refsABNF">[ABNF]</a>
+<!--START websocket-protocol-->
+ <a href="#refsRFC3986">[RFC3986]</a>
+ </p>
<pre>"ws" ":" hier-part [ "?" query ]</pre>
<p>The path and query components form the resource name sent to
the server to identify the kind of service desired. Other
@@ -75432,7 +75465,13 @@ multi-origin semantics described in [ORIGIN] applying. (http-origin)
<dt>URI scheme syntax.</dt>
<dd>
- <p>In ABNF terms using the terminals from the URI specifications: <a href="#refsRFC5234">[RFC5234]</a> <a href="#refsRFC3986">[RFC3986]</a></p>
+ <p>In ABNF terms using the terminals from the URI specifications:
+<!--END complete-->
+ <a href="#refsRFC5234">[RFC5234]</a>
+<!--START complete--><!--END websocket-protocol-->
+ <a href="#refsABNF">[ABNF]</a>
+<!--START websocket-protocol-->
+ <a href="#refsRFC3986">[RFC3986]</a></p>
<pre>"wss" ":" hier-part [ "?" query ]</pre>
<p>The path and query components form the resource name sent to
the server to identify the kind of service desired. Other
@@ -93391,6 +93430,9 @@ interface <span>HTMLDocument</span> {
<dt id="refsCOOKIES">[COOKIES]</dt>
<!--
+ <dd><cite><a href="http://www.ietf.org/rfc/rfc2109.txt">HTTP State
+ Management Mechanism</a></cite>, D. Kristol, L. Montulli. IETF,
+ February 1997.</dd>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2965.txt">HTTP State Management
Mechanism</a></cite>, D. Kristol, L. Montulli. IETF, October 2000.</dd>
-->
@@ -93785,6 +93827,11 @@ interface <span>HTMLDocument</span> {
and Base64 Data Encodings</a></cite>, S. Josefsson. IETF, July
2003.</dd>
+ <dt id="refsRFC3629">[RFC3629]</dt>
+ <dd><cite><a href="http://www.ietf.org/rfc/rfc3629.txt">UTF-8, a
+ transformation format of ISO 10646</a></cite>, F. Yergeau. IETF,
+ November 2003.</dd>
+
<dt id="refsRFC3864">[RFC3864]</dt>
<dd><cite><a
href="http://www.ietf.org/rfc/rfc3864.txt">Registration Procedures
@@ -94524,6 +94571,16 @@ interface <span>HTMLDocument</span> {
<p>Thanks to the many sources that provided inspiration for the
examples used in the specification.</p>
+ <!--END html5-->
+
+ <div itemscope itemtype="http://n.whatwg.org/work">
+ <p>The abstract is based on <a itemprop="work" href="http://www.flickr.com/photos/wonderlane/2986252088/">a photo</a>
+ by <a itemprop="http://creativecommons.org/ns#attributionURL" href="http://www.flickr.com/photos/wonderlane/">Wonderlane</a>.
+ (<a itemprop="license" href="http://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>)
+ </div>
+
+ <!--START html5-->
+
<p>Thanks also to the Microsoft blogging community for some ideas,
to the attendees of the W3C Workshop on Web Applications and
Compound Documents for inspiration, to the #mrt crew, the #mrt.no
@@ -94688,3 +94745,4 @@ Consistency in editorial style:
</body>
</html>
<!--END html5-->
+<!--END complete-->
View
4 vocabs-index
@@ -121,7 +121,9 @@
<!--end-toc-->
<hr><h2 id="introduction"><span class="secno">1 </span>Introduction</h2>
- <p>This specification defines microdata vocabularies. <a href="#refsHTML5">[HTML5]</a></p>
+ <p>This specification defines microdata vocabularies.
+ <a href="#refsHTML5">[HTML5]</a></p>
+
<h2 id="vcard"><span class="secno">2 </span>vCard</h2>

0 comments on commit c77c835

Please sign in to comment.