W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2009

html5/spec Overview.html,1.2115,1.2116

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 01 Apr 2009 18:21:52 +0000
To: public-html-commits@w3.org
Message-Id: <E1Lp54S-0004FX-BO@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv16321

Modified Files:
	Overview.html 
Log Message:
Visit the confessional. (credit: sb) (bug 6684) (whatwg r2953)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2115
retrieving revision 1.2116
diff -u -d -r1.2115 -r1.2116
--- Overview.html	1 Apr 2009 01:54:50 -0000	1.2115
+++ Overview.html	1 Apr 2009 18:21:49 -0000	1.2116
@@ -1688,6 +1688,19 @@
 
    </dd>
 
+   <dt>ECMAScript</dt>
+
+   <dd>
+
+    <p>Some parts of the language described by this specification only
+    support ECMAScript as the underlying scripting language. <a href=#references>[ECMAScript]</a></p>
+
+    <p class=note>The MIME type used to refer to ECMAScript in this
+    specification is <code title="">text/javascript</code>. This is a
+    willful violation of RFC 4329. <a href=#references>[RFC4329]</a></p>
+
+   </dd>
+
    <dt id=mq>Media Queries</dt>
 
    <dd>
@@ -3820,7 +3833,8 @@
   manner distinct from the precise technical meaning it is given in
   RFC 3986. Readers familiar with that RFC will find it easier to read
   <em>this</em> specification if they pretend the term "URL" as used
-  herein is really called something else altogether.</p>
+  herein is really called something else altogether. This is a willful
+  violation of RFC 3986. <a href=#references>RFC3986</a></p>
 
   </div><div class=impl>
 
@@ -3946,7 +3960,10 @@
 
   </ol><!-- XXX we might want to define "server-based naming authority",
   it's not clear RFC3986 does a good job of defining that anymore
-  (earlier URI specs did) --></div><div class=impl>
+  (earlier URI specs did) --><p class=note>These parsing rules are a willful violation of RFC
+  3986 and RFC 3987 to handle legacy content. <a href=#references>RFC3986</a> <a href=#references>RFC3987</a></p>
+
+  </div><div class=impl>
 
   <h4 id=resolving-urls><span class=secno>2.5.3 </span>Resolving URLs</h4>
 
@@ -57181,6 +57198,7 @@
   Shanti Rao,
   Shaun Inman,
   Shiki Okasaka,
+  Sierk Bornemann,
   Sigbj&oslash;rn Vik,
   Silvia Pfeiffer,
   Simon Montagu,
Received on Wednesday, 1 April 2009 18:22:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 April 2009 18:22:01 GMT