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

hixie: fax: is apparently no longer in season. (whatwg r4777)

From: poot <cvsmail@w3.org>
Date: Thu, 18 Feb 2010 14:02:27 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100218050227.EDE712BBF1@toro.w3.mag.keio.ac.jp>
hixie: fax: is apparently no longer in season. (whatwg r4777)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3824&r2=1.3825&f=h
http://html5.org/tools/web-apps-tracker?from=4776&to=4777

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3824
retrieving revision 1.3825
diff -u -d -r1.3824 -r1.3825
--- Overview.html	18 Feb 2010 03:30:08 -0000	1.3824
+++ Overview.html	18 Feb 2010 05:02:09 -0000	1.3825
@@ -46410,17 +46410,18 @@
 
   </dl></div><h4 id="custom-handlers"><span class="secno">6.4.2 </span>Custom scheme and content handlers</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><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.<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>
+  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.<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>
 
    <dd>
@@ -46462,7 +46463,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
@@ -67958,11 +67959,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>
@@ -68014,6 +68010,15 @@
    <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>
+
    <dt id="refsRFC2483">[RFC2483]</dt>
    <dd><cite><a href="http://www.ietf.org/rfc/rfc2483.txt">URI Resolution
    Services Necessary for URN Resolution</a></cite>, M. Mealling, R. Daniel.
@@ -68027,10 +68032,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>
@@ -68082,6 +68083,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,
Received on Thursday, 18 February 2010 05:03:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:17 GMT