Skip to content

Commit

Permalink
[e] (0) Fix the last field to match RFC 4395's requirements. Also, ad…
Browse files Browse the repository at this point in the history 
…d colons for consistency with other similar sections.

Affected topics: HTML, Security, Server-Sent Events

git-svn-id: http://svn.whatwg.org/webapps@6969 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Feb 6, 2012
1 parent 6c8b5f9 commit ca2e979
Show file tree
Hide file tree
Showing 3 changed files with 99 additions and 90 deletions.
63 changes: 33 additions & 30 deletions complete.html
View file
Expand Up @@ -77610,19 +77610,19 @@ <h5 id=last-event-id><span class=secno>10.2.9.2 </span><dfn title=http-last-even
<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-->

Expand Down Expand Up @@ -94308,63 +94308,63 @@ <h3 id=ping-from><span class=secno>16.8 </span><dfn title=http-ping-from><code>P
<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.
Expand All @@ -94374,12 +94374,15 @@ <h3 id=ping-from><span class=secno>16.8 </span><dfn title=http-ping-from><code>P
confidential project names.
</dd>
<!--REMOVE-TOPIC:Security-->
<dt>Contact</dt>
<dt>Contact:</dt>
<dd>Ian Hickson &lt;ian@hixie.ch&gt;</dd>
<dt>Author/Change controller</dt>
<dt>Author/Change controller:</dt>
<dd>Ian Hickson &lt;ian@hixie.ch&gt;</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>
Expand Down
63 changes: 33 additions & 30 deletions index
View file
Expand Up @@ -77610,19 +77610,19 @@ data:&nbsp;test
<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-->

Expand Down Expand Up @@ -94308,63 +94308,63 @@ if (s = prompt('What is your name?')) {
<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.
Expand All @@ -94374,12 +94374,15 @@ if (s = prompt('What is your name?')) {
confidential project names.
</dd>
<!--REMOVE-TOPIC:Security-->
<dt>Contact</dt>
<dt>Contact:</dt>
<dd>Ian Hickson &lt;ian@hixie.ch&gt;</dd>
<dt>Author/Change controller</dt>
<dt>Author/Change controller:</dt>
<dd>Ian Hickson &lt;ian@hixie.ch&gt;</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>
Expand Down
63 changes: 33 additions & 30 deletions source
View file
Expand Up @@ -89998,19 +89998,19 @@ data:&nbsp;test
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>

Expand Down Expand Up @@ -110086,19 +110086,19 @@ if (s = prompt('What is your name?')) {
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>

Expand All @@ -110110,19 +110110,19 @@ if (s = prompt('What is your name?')) {
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>

Expand All @@ -110136,26 +110136,26 @@ if (s = prompt('What is your name?')) {
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
Expand All @@ -110166,12 +110166,15 @@ if (s = prompt('What is your name?')) {
confidential project names.
</dd>
<!--REMOVE-TOPIC:Security-->
<dt>Contact</dt>
<dt>Contact:</dt>
<dd>Ian Hickson &lt;ian@hixie.ch></dd>
<dt>Author/Change controller</dt>
<dt>Author/Change controller:</dt>
<dd>Ian Hickson &lt;ian@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>


Expand Down

0 comments on commit ca2e979

Please sign in to comment.