[html5] r4777 - [e] (0) fax: is apparently no longer in season. Fixing http://www.w3.org/Bugs/Pu [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Feb 17 21:02:06 PST 2010
Author: ianh
Date: 2010-02-17 21:02:04 -0800 (Wed, 17 Feb 2010)
New Revision: 4777
Modified:
complete.html
index
source
Log:
[e] (0) fax: is apparently no longer in season.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8855
Modified: complete.html
===================================================================
--- complete.html 2010-02-18 03:30:03 UTC (rev 4776)
+++ complete.html 2010-02-18 05:02:04 UTC (rev 4777)
@@ -59605,17 +59605,18 @@
<p>The <dfn id=dom-navigator-registerprotocolhandler title=dom-navigator-registerProtocolHandler><code>registerProtocolHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
- for particular schemes. For example, an online fax service could
- register itself as a handler of the <code>fax:</code> scheme (<a href=#refsRFC2806>[RFC2806]</a>), so that if the user clicks on
- such a link, he is given the opportunity to use that Web
+ for particular schemes. For example, an online telephone messaging
+ service could register itself as a handler of the <code>sms:</code>
+ scheme (<a href=#refsRFC5724>[RFC5724]</a>), so that if the user
+ clicks on such a link, he is given the opportunity to use that Web
site. Analogously, the <dfn id=dom-navigator-registercontenthandler title=dom-navigator-registerContentHandler><code>registerContentHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
for content in a particular <a href=#mime-type>MIME type</a>. For example, the
- same online fax service could register itself as a handler for
- <code>image/g3fax</code> files (<a href=#refsRFC1494>[RFC1494]</a>), so that if the user has no
- native application capable of handling G3 Facsimile byte streams,
- his Web browser can instead suggest he use that site to view the
- image.</p>
+ same online telephone messaging service could register itself as a
+ handler for <code>text/directory</code> files (<a href=#refsRFC2425>[RFC2425]</a>), so that if the user has no
+ native application capable of handling vCards (<a href=#refsRFC2426>[RFC2426]</a>), his Web browser can instead
+ suggest he use that site to view contact information stored on
+ vCards that he opens.</p>
<dl class=domintro><dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerProtocolHandler><a href=#dom-navigator-registerprotocolhandler>registerProtocolHandler</a></code>(<var title="">scheme</var>, <var title="">url</var>, <var title="">title</var>)</dt>
<dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerContentHandler><a href=#dom-navigator-registercontenthandler>registerContentHandler</a></code>(<var title="">mimeType</var>, <var title="">url</var>, <var title="">title</var>)</dt>
@@ -59659,7 +59660,7 @@
<dd>
- <p>A scheme, such as <code>ftp</code> or <code>fax</code>. The
+ <p>A scheme, such as <code>ftp</code> or <code>sms</code>. The
scheme must be compared in an <a href=#ascii-case-insensitive>ASCII case-insensitive</a>
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
@@ -88499,11 +88500,6 @@
Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der
Poel. IETF.</dd>
- <dt id=refsRFC1494>[RFC1494]</dt>
- <dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc1494.txt>Equivalences between
- 1988 X.400 and RFC-822 Message Bodies</a></cite>, H. Alvestrand,
- S. Thompson. IETF.</dd>
-
<dt id=refsRFC1554>[RFC1554]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc1554.txt>ISO-2022-JP-2:
Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF.</dd>
@@ -88559,6 +88555,11 @@
<dd><cite><a href=http://www.ietf.org/rfc/rfc2388.txt>Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>
+ <dt id=refsRFC2425>[RFC2425]</dt>
+ <dd><cite><a href=http://www.ietf.org/rfc/rfc2425.txt>A MIME
+ Content-Type for Directory Information</a></cite>, T. Howes,
+ M. Smith, F. Dawson. IETF.</dd>
+
<dt id=refsRFC2426>[RFC2426]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2426.txt>vCard MIME Directory
Profile</a></cite>, F. Dawson, T. Howes. IETF.</dd>
@@ -88581,10 +88582,6 @@
<dd><cite><a href=http://www.ietf.org/rfc/rfc2646.txt>The Text/Plain Format
Parameter</a></cite>, R. Gellens. IETF.</dd>
- <dt id=refsRFC2806>[RFC2806]</dt>
- <dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc2806.txt>URLs for Telephone
- Calls</a></cite>, A. Vaha-Sipila. IETF.</dd>
-
<dt id=refsRFC3023>[RFC3023]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc3023.txt>XML Media
Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF.</dd>
@@ -88649,6 +88646,11 @@
<dd><cite><a href=http://www.ietf.org/rfc/rfc5322.txt>Internet Message
Format</a></cite>, P. Resnick. IETF.</dd>
+ <dt id=refsRFC5724>[RFC5724]</dt>
+ <dd><cite><a href=http://www.ietf.org/rfc/rfc5724.txt>URI Scheme
+ for Global System for Mobile Communications (GSM) Short Message
+ Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>
+
<dt id=refsSCSU>[SCSU]</dt>
<dd>(Non-normative) <cite><a href=http://www.unicode.org/reports/tr6/>UTR #6: A Standard
Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
Modified: index
===================================================================
--- index 2010-02-18 03:30:03 UTC (rev 4776)
+++ index 2010-02-18 05:02:04 UTC (rev 4777)
@@ -59527,17 +59527,18 @@
<p>The <dfn id=dom-navigator-registerprotocolhandler title=dom-navigator-registerProtocolHandler><code>registerProtocolHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
- for particular schemes. For example, an online fax service could
- register itself as a handler of the <code>fax:</code> scheme (<a href=#refsRFC2806>[RFC2806]</a>), so that if the user clicks on
- such a link, he is given the opportunity to use that Web
+ for particular schemes. For example, an online telephone messaging
+ service could register itself as a handler of the <code>sms:</code>
+ scheme (<a href=#refsRFC5724>[RFC5724]</a>), so that if the user
+ clicks on such a link, he is given the opportunity to use that Web
site. Analogously, the <dfn id=dom-navigator-registercontenthandler title=dom-navigator-registerContentHandler><code>registerContentHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
for content in a particular <a href=#mime-type>MIME type</a>. For example, the
- same online fax service could register itself as a handler for
- <code>image/g3fax</code> files (<a href=#refsRFC1494>[RFC1494]</a>), so that if the user has no
- native application capable of handling G3 Facsimile byte streams,
- his Web browser can instead suggest he use that site to view the
- image.</p>
+ same online telephone messaging service could register itself as a
+ handler for <code>text/directory</code> files (<a href=#refsRFC2425>[RFC2425]</a>), so that if the user has no
+ native application capable of handling vCards (<a href=#refsRFC2426>[RFC2426]</a>), his Web browser can instead
+ suggest he use that site to view contact information stored on
+ vCards that he opens.</p>
<dl class=domintro><dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerProtocolHandler><a href=#dom-navigator-registerprotocolhandler>registerProtocolHandler</a></code>(<var title="">scheme</var>, <var title="">url</var>, <var title="">title</var>)</dt>
<dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerContentHandler><a href=#dom-navigator-registercontenthandler>registerContentHandler</a></code>(<var title="">mimeType</var>, <var title="">url</var>, <var title="">title</var>)</dt>
@@ -59581,7 +59582,7 @@
<dd>
- <p>A scheme, such as <code>ftp</code> or <code>fax</code>. The
+ <p>A scheme, such as <code>ftp</code> or <code>sms</code>. The
scheme must be compared in an <a href=#ascii-case-insensitive>ASCII case-insensitive</a>
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
@@ -82957,11 +82958,6 @@
Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der
Poel. IETF.</dd>
- <dt id=refsRFC1494>[RFC1494]</dt>
- <dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc1494.txt>Equivalences between
- 1988 X.400 and RFC-822 Message Bodies</a></cite>, H. Alvestrand,
- S. Thompson. IETF.</dd>
-
<dt id=refsRFC1554>[RFC1554]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc1554.txt>ISO-2022-JP-2:
Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF.</dd>
@@ -83013,6 +83009,11 @@
<dd><cite><a href=http://www.ietf.org/rfc/rfc2388.txt>Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>
+ <dt id=refsRFC2425>[RFC2425]</dt>
+ <dd><cite><a href=http://www.ietf.org/rfc/rfc2425.txt>A MIME
+ Content-Type for Directory Information</a></cite>, T. Howes,
+ M. Smith, F. Dawson. IETF.</dd>
+
<dt id=refsRFC2426>[RFC2426]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2426.txt>vCard MIME Directory
Profile</a></cite>, F. Dawson, T. Howes. IETF.</dd>
@@ -83035,10 +83036,6 @@
<dd><cite><a href=http://www.ietf.org/rfc/rfc2646.txt>The Text/Plain Format
Parameter</a></cite>, R. Gellens. IETF.</dd>
- <dt id=refsRFC2806>[RFC2806]</dt>
- <dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc2806.txt>URLs for Telephone
- Calls</a></cite>, A. Vaha-Sipila. IETF.</dd>
-
<dt id=refsRFC3023>[RFC3023]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc3023.txt>XML Media
Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF.</dd>
@@ -83094,6 +83091,11 @@
<dd><cite><a href=http://www.ietf.org/rfc/rfc5322.txt>Internet Message
Format</a></cite>, P. Resnick. IETF.</dd>
+ <dt id=refsRFC5724>[RFC5724]</dt>
+ <dd><cite><a href=http://www.ietf.org/rfc/rfc5724.txt>URI Scheme
+ for Global System for Mobile Communications (GSM) Short Message
+ Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>
+
<dt id=refsSCSU>[SCSU]</dt>
<dd>(Non-normative) <cite><a href=http://www.unicode.org/reports/tr6/>UTR #6: A Standard
Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
Modified: source
===================================================================
--- source 2010-02-18 03:30:03 UTC (rev 4776)
+++ source 2010-02-18 05:02:04 UTC (rev 4777)
@@ -67360,20 +67360,21 @@
<p>The <dfn
title="dom-navigator-registerProtocolHandler"><code>registerProtocolHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
- for particular schemes. For example, an online fax service could
- register itself as a handler of the <code>fax:</code> scheme (<a
- href="#refsRFC2806">[RFC2806]</a>), so that if the user clicks on
- such a link, he is given the opportunity to use that Web
+ for particular schemes. For example, an online telephone messaging
+ service could register itself as a handler of the <code>sms:</code>
+ scheme (<a href="#refsRFC5724">[RFC5724]</a>), so that if the user
+ clicks on such a link, he is given the opportunity to use that Web
site. Analogously, the <dfn
title="dom-navigator-registerContentHandler"><code>registerContentHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
for content in a particular <span>MIME type</span>. For example, the
- same online fax service could register itself as a handler for
- <code>image/g3fax</code> files (<a
- href="#refsRFC1494">[RFC1494]</a>), so that if the user has no
- native application capable of handling G3 Facsimile byte streams,
- his Web browser can instead suggest he use that site to view the
- image.</p>
+ same online telephone messaging service could register itself as a
+ handler for <code>text/directory</code> files (<a
+ href="#refsRFC2425">[RFC2425]</a>), so that if the user has no
+ native application capable of handling vCards (<a
+ href="#refsRFC2426">[RFC2426]</a>), his Web browser can instead
+ suggest he use that site to view contact information stored on
+ vCards that he opens.</p>
<dl class="domintro">
@@ -67424,7 +67425,7 @@
<dd>
- <p>A scheme, such as <code>ftp</code> or <code>fax</code>. The
+ <p>A scheme, such as <code>ftp</code> or <code>sms</code>. The
scheme must be compared in an <span>ASCII case-insensitive</span>
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
@@ -99109,6 +99110,11 @@
<dd><cite><a href="http://www.ietf.org/rfc/rfc2388.txt">Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>
+ <dt id="refsRFC2425">[RFC2425]</dt>
+ <dd><cite><a href="http://www.ietf.org/rfc/rfc2425.txt">A MIME
+ Content-Type for Directory Information</a></cite>, T. Howes,
+ M. Smith, F. Dawson. IETF.</dd>
+
<dt id="refsRFC2426">[RFC2426]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2426.txt">vCard MIME Directory
Profile</a></cite>, F. Dawson, T. Howes. IETF.</dd>
@@ -99202,6 +99208,11 @@
<dd><cite><a href="http://www.ietf.org/rfc/rfc5322.txt">Internet Message
Format</a></cite>, P. Resnick. IETF.</dd>
+ <dt id="refsRFC5724">[RFC5724]</dt>
+ <dd><cite><a href="http://www.ietf.org/rfc/rfc5724.txt">URI Scheme
+ for Global System for Mobile Communications (GSM) Short Message
+ Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>
+
<dt id="refsSCSU">[SCSU]</dt>
<dd>(Non-normative) <cite><a
href="http://www.unicode.org/reports/tr6/">UTR #6: A Standard
More information about the Commit-Watchers
mailing list