[html5] r6969 - [e] (0) Fix the last field to match RFC 4395's requirements. Also, add colons fo [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Feb 6 15:48:27 PST 2012
Author: ianh
Date: 2012-02-06 15:48:25 -0800 (Mon, 06 Feb 2012)
New Revision: 6969
Modified:
complete.html
index
source
Log:
[e] (0) Fix the last field to match RFC 4395's requirements. Also, add colons for consistency with other similar sections.
Affected topics: HTML, Security, Server-Sent Events
Modified: complete.html
===================================================================
--- complete.html 2012-02-06 23:41:50 UTC (rev 6968)
+++ complete.html 2012-02-06 23:48:25 UTC (rev 6969)
@@ -77610,19 +77610,19 @@
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href=#refsRFC3864>[RFC3864]</a></p>
- <dl><dt>Header field name</dt>
+ <dl><dt>Header field name:</dt>
<dd>Last-Event-ID</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl></div><!--data-component-->
@@ -94308,63 +94308,63 @@
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href=#refsRFC3864>[RFC3864]</a></p>
- <dl><dt>Header field name</dt>
+ <dl><dt>Header field name:</dt>
<dd>Ping-From</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl><h3 id=ping-to><span class=secno>16.9 </span><dfn title=http-ping-to><code>Ping-To</code></dfn></h3>
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href=#refsRFC3864>[RFC3864]</a></p>
- <dl><dt>Header field name</dt>
+ <dl><dt>Header field name:</dt>
<dd>Ping-To</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl><!--PING--><h3 id=web+-scheme-prefix><span class=secno>16.10 </span><dfn title=scheme-web><code>web+</code> scheme prefix</dfn></h3>
<p>This section describes a convention for use with the IANA URI
scheme registry. It does not itself register a specific scheme. <a href=#refsRFC4395>[RFC4395]</a></p>
- <dl><dt>URI scheme name</dt>
+ <dl><dt>URI scheme name:</dt>
<dd>
Schemes starting with the four characters "<code title="">web+</code>" followed by one or more letters in the range
<code title="">a</code>-<code title="">z</code>.
</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>permanent</dd>
- <dt>URI scheme syntax</dt>
+ <dt>URI scheme syntax:</dt>
<dd>Scheme-specific.</dd>
- <dt>URI scheme semantics</dt>
+ <dt>URI scheme semantics:</dt>
<dd>Scheme-specific.</dd>
- <dt>Encoding considerations</dt>
+ <dt>Encoding considerations:</dt>
<dd>All "<code title="">web+</code>" schemes should use UTF-8 encodings were relevant.</dd>
- <dt>Applications/protocols that use this URI scheme name</dt>
+ <dt>Applications/protocols that use this URI scheme name:</dt>
<dd>Scheme-specific.</dd>
- <dt>Interoperability considerations</dt>
+ <dt>Interoperability considerations:</dt>
<dd>The scheme is expected to be used in the context of Web applications.</dd>
<!--ADD-TOPIC:Security-->
- <dt>Security considerations</dt>
+ <dt>Security considerations:</dt>
<dd>
Any Web page is able to register a handler for all "<code title="">web+</code>" schemes. As such, these schemes must not be
used for features intended to be core platform features (e.g.
@@ -94374,12 +94374,15 @@
confidential project names.
</dd>
<!--REMOVE-TOPIC:Security-->
- <dt>Contact</dt>
+ <dt>Contact:</dt>
<dd>Ian Hickson <ian at hixie.ch></dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>Ian Hickson <ian at hixie.ch></dd>
- <dt>References</dt>
- <dd>W3C</dd>
+ <dt>References:</dt>
+ <dd>
+ <cite>Custom scheme and content handlers</cite>, HTML Living Standard:
+ <a href=#custom-handlers>http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers</a>
+ </dd>
</dl><h2 class=no-num id=index>Index</h2>
<div class=impl>
Modified: index
===================================================================
--- index 2012-02-06 23:41:50 UTC (rev 6968)
+++ index 2012-02-06 23:48:25 UTC (rev 6969)
@@ -77610,19 +77610,19 @@
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href=#refsRFC3864>[RFC3864]</a></p>
- <dl><dt>Header field name</dt>
+ <dl><dt>Header field name:</dt>
<dd>Last-Event-ID</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl></div><!--data-component-->
@@ -94308,63 +94308,63 @@
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href=#refsRFC3864>[RFC3864]</a></p>
- <dl><dt>Header field name</dt>
+ <dl><dt>Header field name:</dt>
<dd>Ping-From</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl><h3 id=ping-to><span class=secno>16.9 </span><dfn title=http-ping-to><code>Ping-To</code></dfn></h3>
<p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href=#refsRFC3864>[RFC3864]</a></p>
- <dl><dt>Header field name</dt>
+ <dl><dt>Header field name:</dt>
<dd>Ping-To</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl><!--PING--><h3 id=web+-scheme-prefix><span class=secno>16.10 </span><dfn title=scheme-web><code>web+</code> scheme prefix</dfn></h3>
<p>This section describes a convention for use with the IANA URI
scheme registry. It does not itself register a specific scheme. <a href=#refsRFC4395>[RFC4395]</a></p>
- <dl><dt>URI scheme name</dt>
+ <dl><dt>URI scheme name:</dt>
<dd>
Schemes starting with the four characters "<code title="">web+</code>" followed by one or more letters in the range
<code title="">a</code>-<code title="">z</code>.
</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>permanent</dd>
- <dt>URI scheme syntax</dt>
+ <dt>URI scheme syntax:</dt>
<dd>Scheme-specific.</dd>
- <dt>URI scheme semantics</dt>
+ <dt>URI scheme semantics:</dt>
<dd>Scheme-specific.</dd>
- <dt>Encoding considerations</dt>
+ <dt>Encoding considerations:</dt>
<dd>All "<code title="">web+</code>" schemes should use UTF-8 encodings were relevant.</dd>
- <dt>Applications/protocols that use this URI scheme name</dt>
+ <dt>Applications/protocols that use this URI scheme name:</dt>
<dd>Scheme-specific.</dd>
- <dt>Interoperability considerations</dt>
+ <dt>Interoperability considerations:</dt>
<dd>The scheme is expected to be used in the context of Web applications.</dd>
<!--ADD-TOPIC:Security-->
- <dt>Security considerations</dt>
+ <dt>Security considerations:</dt>
<dd>
Any Web page is able to register a handler for all "<code title="">web+</code>" schemes. As such, these schemes must not be
used for features intended to be core platform features (e.g.
@@ -94374,12 +94374,15 @@
confidential project names.
</dd>
<!--REMOVE-TOPIC:Security-->
- <dt>Contact</dt>
+ <dt>Contact:</dt>
<dd>Ian Hickson <ian at hixie.ch></dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>Ian Hickson <ian at hixie.ch></dd>
- <dt>References</dt>
- <dd>W3C</dd>
+ <dt>References:</dt>
+ <dd>
+ <cite>Custom scheme and content handlers</cite>, HTML Living Standard:
+ <a href=#custom-handlers>http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers</a>
+ </dd>
</dl><h2 class=no-num id=index>Index</h2>
<div class=impl>
Modified: source
===================================================================
--- source 2012-02-06 23:41:50 UTC (rev 6968)
+++ source 2012-02-06 23:48:25 UTC (rev 6969)
@@ -89998,19 +89998,19 @@
href="#refsRFC3864">[RFC3864]</a></p>
<dl>
- <dt>Header field name</dt>
+ <dt>Header field name:</dt>
<dd>Last-Event-ID</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl>
@@ -110086,19 +110086,19 @@
href="#refsRFC3864">[RFC3864]</a></p>
<dl>
- <dt>Header field name</dt>
+ <dt>Header field name:</dt>
<dd>Ping-From</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl>
@@ -110110,19 +110110,19 @@
href="#refsRFC3864">[RFC3864]</a></p>
<dl>
- <dt>Header field name</dt>
+ <dt>Header field name:</dt>
<dd>Ping-To</dd>
- <dt>Applicable protocol</dt>
+ <dt>Applicable protocol:</dt>
<dd>http</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>standard</dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>W3C</dd>
- <dt>Specification document(s)</dt>
+ <dt>Specification document(s):</dt>
<dd>
This document is the relevant specification.
</dd>
- <dt>Related information</dt>
+ <dt>Related information:</dt>
<dd>None.</dd>
</dl>
@@ -110136,26 +110136,26 @@
href="#refsRFC4395">[RFC4395]</a></p>
<dl>
- <dt>URI scheme name</dt>
+ <dt>URI scheme name:</dt>
<dd>
Schemes starting with the four characters "<code
title="">web+</code>" followed by one or more letters in the range
<code title="">a</code>-<code title="">z</code>.
</dd>
- <dt>Status</dt>
+ <dt>Status:</dt>
<dd>permanent</dd>
- <dt>URI scheme syntax</dt>
+ <dt>URI scheme syntax:</dt>
<dd>Scheme-specific.</dd>
- <dt>URI scheme semantics</dt>
+ <dt>URI scheme semantics:</dt>
<dd>Scheme-specific.</dd>
- <dt>Encoding considerations</dt>
+ <dt>Encoding considerations:</dt>
<dd>All "<code title="">web+</code>" schemes should use UTF-8 encodings were relevant.</dd>
- <dt>Applications/protocols that use this URI scheme name</dt>
+ <dt>Applications/protocols that use this URI scheme name:</dt>
<dd>Scheme-specific.</dd>
- <dt>Interoperability considerations</dt>
+ <dt>Interoperability considerations:</dt>
<dd>The scheme is expected to be used in the context of Web applications.</dd>
<!--ADD-TOPIC:Security-->
- <dt>Security considerations</dt>
+ <dt>Security considerations:</dt>
<dd>
Any Web page is able to register a handler for all "<code
title="">web+</code>" schemes. As such, these schemes must not be
@@ -110166,12 +110166,15 @@
confidential project names.
</dd>
<!--REMOVE-TOPIC:Security-->
- <dt>Contact</dt>
+ <dt>Contact:</dt>
<dd>Ian Hickson <ian at hixie.ch></dd>
- <dt>Author/Change controller</dt>
+ <dt>Author/Change controller:</dt>
<dd>Ian Hickson <ian at hixie.ch></dd>
- <dt>References</dt>
- <dd>W3C</dd>
+ <dt>References:</dt>
+ <dd>
+ <cite>Custom scheme and content handlers</cite>, HTML Living Standard:
+ <a href="#custom-handlers">http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers</a>
+ </dd>
</dl>
More information about the Commit-Watchers
mailing list