W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2012

hixie: Fix the last field to match RFC 4395's requirements. Also, add colons for consistency with other similar sections. (whatwg r6969)

From: poot <cvsmail@w3.org>
Date: Mon, 06 Feb 2012 18:50:21 -0500
To: public-html-diffs@w3.org
Message-Id: <E1RuYKD-0002Ue-Px@jay.w3.org>
hixie: Fix the last field to match RFC 4395's requirements. Also, add
colons for consistency with other similar sections. (whatwg r6969)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5563&r2=1.5564&f=h
http://html5.org/tools/web-apps-tracker?from=6968&to=6969

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5563
retrieving revision 1.5564
diff -u -d -r1.5563 -r1.5564
--- Overview.html	6 Feb 2012 23:41:57 -0000	1.5563
+++ Overview.html	6 Feb 2012 23:48:31 -0000	1.5564
@@ -70794,25 +70794,25 @@
    <dd>W3C</dd>
   </dl><p>Fragment identifiers have no meaning with
   <code><a href="#text-cache-manifest">text/cache-manifest</a></code> resources.<h3 id="web-scheme-prefix"><span class="secno">12.6 </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><dl><dt>URI scheme name</dt>
+  scheme registry. It does not itself register a specific scheme. <a href="#refsRFC4395">[RFC4395]</a><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>
 
-   <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.
@@ -70822,12 +70822,15 @@
     confidential project names.
    </dd>
 
-   <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">
 
   <p>The following sections only cover conforming elements and features.</p>
Received on Monday, 6 February 2012 23:52:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 February 2012 23:52:26 GMT