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

html5/html4-differences Overview.html,1.63,1.64 Overview.src.html,1.42,1.43

From: Anne van Kesteren via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 15 Apr 2009 21:56:30 +0000
To: public-html-commits@w3.org
Message-Id: <E1LuD5q-0007WX-Qs@lionel-hutz.w3.org>
Update of /sources/public/html5/html4-differences
In directory hutz:/tmp/cvs-serv28883

Modified Files:
	Overview.html Overview.src.html 
Log Message:
editorial comments from markp and zcorpan; ta\!

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- Overview.html	15 Apr 2009 17:46:34 -0000	1.63
+++ Overview.html	15 Apr 2009 21:56:28 -0000	1.64
@@ -227,8 +227,8 @@
    contemporary HTML implementations and deployed content. The draft:
 
   <ol>
-   <li>Defines a single language called HTML&nbsp;5 which can be written in a
-    "custom" HTML syntax and in XML syntax.
+   <li>Defines a single language called HTML&nbsp;5 which can be written in
+    HTML syntax and in XML syntax.
 
    <li>Defines detailed processing models to foster interoperable
     implementations.
@@ -353,11 +353,11 @@
 
   <h2 id=syntax><span class=secno>2 </span>Syntax</h2>
 
-  <p>The HTML&nbsp;5 language has a "custom" HTML syntax that is compatible
-   with HTML&nbsp;4 and XHTML&nbsp;1 documents published on the Web, but is
-   not compatible with the more esoteric SGML features of HTML&nbsp;4, such
-   as the NET syntax (i.e. <code>&lt;em/content/</code>). Documents using the
-   HTML syntax must be served with the <code>text/html</code> media type.
+  <p>HTML&nbsp;5 defines an HTML syntax that is compatible with HTML&nbsp;4
+   and XHTML&nbsp;1 documents published on the Web, but is not compatible
+   with the more esoteric SGML features of HTML&nbsp;4, such as the NET
+   syntax (i.e. <code>&lt;em/content/</code>). Documents using the HTML
+   syntax must be served with the <code>text/html</code> media type.
 
   <p>HTML&nbsp;5 also defines detailed parsing rules (including "error
    handling") for this syntax which are largely compatible with popular
@@ -417,8 +417,8 @@
     although that syntax is still allowed.
   </ul>
 
-  <p>For the XML syntax authors have to use the rules as set forth in the XML
-   specifications to set the character encoding.
+  <p>For the XML syntax, authors have to use the rules as set forth in the
+   XML specifications to set the character encoding.
 
   <h3 id=doctype><span class=secno>2.2 </span>The <code
    title="">DOCTYPE</code></h3>
@@ -461,8 +461,8 @@
   <p>There are a few other syntax changes worthy of mentioning:
 
   <ul>
-   <li>HTML now has native support for IRIs. In HTML&nbsp;4 this was only
-    handled as error handling.
+   <li>HTML now has native support for IRIs, though they can only be fully
+    used if the document encoding is UTF-8 or UTF-16.
 
    <li>The <code>lang</code> attribute takes the empty string in addition to
     a valid language identifier, just like <code>xml:lang</code> does in XML.
@@ -568,7 +568,7 @@
 
    <li>
     <p><code>datagrid</code> represents an interactive representation of a
-     tree list or tabular data.
+     tree, list or tabular data.
 
    <li>
     <p><code>details</code> represents additional information or controls
@@ -587,7 +587,7 @@
 &lt;/datalist></code></pre>
 
    <li>
-    <p><code>keygen</code> representa control for key pair generation.
+    <p><code>keygen</code> represents control for key pair generation.
    </li>
    <!--
       <li><p><code>eventsource</code> is used to set up a
@@ -656,23 +656,24 @@
 
    <li>
     <p>The <code>a</code> and <code>area</code> elements have a new attribute
-     called <code>ping</code> that specifies a space separated list of URIs
+     called <code>ping</code> that specifies a space-separated list of URLs
      which have to be pinged when the hyperlink is followed. Currently user
      tracking is mostly done through redirects. This attribute allows the
      user agent to inform users which URLs are going to be pinged as well as
      giving privacy-conscious users a way to turn it off.
 
    <li>
-    <p>The <code>area</code> element, for consistency, now has the
-     <code>hreflang</code> and <code>rel</code> attributes.
+    <p>The <code>area</code> element, for consistency with the <code>a</code>
+     and <code>link</code> elements, now also has the <code>hreflang</code>
+     and <code>rel</code> attributes.
 
    <li>
     <p>The <code>base</code> element can now have a <code>target</code>
      attribute as well, mainly for consistency with the <code>a</code>
-     element (it is also widely supported). Also, the <code>target</code>
-     attribute for the <code>a</code> and <code>area</code> elements is no
-     longer deprecated, as it is useful in Web applications, e.g. in
-     conjunction with <code>iframe</code>.
+     element. (This is already widely supported.) Also, the
+     <code>target</code> attribute for the <code>a</code> and
+     <code>area</code> elements is no longer deprecated, as it is useful in
+     Web applications, e.g. in conjunction with <code>iframe</code>.
 
    <li>
     <p>The <code>value</code> attribute for the <code>li</code> element is no
@@ -849,8 +850,8 @@
      for the underlying platform user interface.
 
    <li>
-    <p>The <code>menu</code> element is redefined to be useful for actual
-     menus.
+    <p>The <code>menu</code> element is redefined to be useful for toolbars
+     and context menus.
 
    <li>
     <p>The <code>small</code> element now represents small print (for side
@@ -1169,8 +1170,8 @@
   <ul>
    <li>A new global attribute called <code>spellcheck</code> has been added.
 
-   <li>Defined that <code>this</code> in the global object returns a
-    <code>WindowProxy</code> object rather than the <code>Window</code>
+   <li>Defined that ECMAScript <code>this</code> in the global object returns
+    a <code>WindowProxy</code> object rather than the <code>Window</code>
     object.
 
    <li>The <code>value</code> DOM attribute for <code>input</code> elements
@@ -1182,7 +1183,7 @@
    <li>The <code>drawImage()</code> method of the 2D drawing API can now take
     a <code>video</code> element as well.
 
-   <li>The way media elements load resources has been clarified.
+   <li>The way media elements load resources has been changed.
 
    <li><code>document.domain</code> is now IPv6-compatible.
 
@@ -1214,10 +1215,10 @@
     <code>formtarget</code>.
 
    <li>A "storage mutex" concept has been added to deal with separate pages
-    trying to change the <code>document.cookie</code> and
-    <code>localStorage</code> object at the same time. The
-    <code>Navigator</code> gained a <code>getStorageUpdates()</code> method
-    to allow it to be explicitly released.
+    trying to change a storage object (<code>document.cookie</code> and
+    <code>localStorage</code>) at the same time. The <code>Navigator</code>
+    gained a <code>getStorageUpdates()</code> method to allow it to be
+    explicitly released.
 
    <li>A syntax for SVG similar to MathML is now defined so that SVG can be
     included in <code>text/html</code> resources.
@@ -1553,7 +1554,7 @@
     been clarified.
 
    <li><code>postMessage()</code> API changed. Only the origin of the message
-    is exposed, no longer the URI. It also requires a second argument that
+    is exposed, no longer the URL. It also requires a second argument that
     indicates the origin of the target document.
 
    <li>Drag and drop API has got clarification. The <code>dataTransfer</code>
@@ -1633,11 +1634,12 @@
 
   <p>The editor would like to thank Ben Millard, Cameron McCormack, Charles
    McCathieNevile, Dan Connolly, David H&aring;s&auml;ther, Frank Ellermann,
-   Henri Sivonen, James Graham, J&uuml;rgen Jeka, Maciej Stachowiak, Martijn
-   Wargers, Martyn Haigh, Masataka Yakura, Michael Smith, Olivier Gendrin,
-   &Oslash;istein E. Andersen, Philip Taylor and Simon Pieters for their
-   contributions to this document as well as to all the people who have
-   contributed to HTML&nbsp;5 over the years for improving the Web!
+   Henri Sivonen, James Graham, J&uuml;rgen Jeka, Maciej Stachowiak, Mark
+   Pilgrim, Martijn Wargers, Martyn Haigh, Masataka Yakura, Michael Smith,
+   Olivier Gendrin, &Oslash;istein E. Andersen, Philip Taylor and Simon
+   Pieters for their contributions to this document as well as to all the
+   people who have contributed to HTML&nbsp;5 over the years for improving
+   the Web!
 
   <h2 class=no-num id=references>References</h2>
 

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.src.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- Overview.src.html	15 Apr 2009 17:46:34 -0000	1.42
+++ Overview.src.html	15 Apr 2009 21:56:28 -0000	1.43
@@ -137,7 +137,7 @@
 
     <ol>
       <li>Defines a single language called HTML&nbsp;5 which can be written
-      in a "custom" HTML syntax and in XML syntax.</li>
+      in HTML syntax and in XML syntax.</li>
       <li>Defines detailed processing models to foster interoperable
       implementations.</li>
       <li>Improves markup for documents.</li>
@@ -269,7 +269,7 @@
 
     <h2 id="syntax">Syntax</h2>
 
-    <p>The HTML&nbsp;5 language has a "custom" HTML syntax that is
+    <p>HTML&nbsp;5 defines an HTML syntax that is
     compatible with HTML&nbsp;4 and XHTML&nbsp;1 documents published on the
     Web, but is not compatible with the more esoteric SGML features of
     HTML&nbsp;4, such as the NET syntax (i.e. <code>&lt;em/content/</code>).
@@ -336,7 +336,7 @@
       although that syntax is still allowed.</li>
     </ul>
 
-    <p>For the XML syntax authors have to use the rules as set forth in the
+    <p>For the XML syntax, authors have to use the rules as set forth in the
     XML specifications to set the character encoding.</p>
 
     <h3 id="doctype">The <code title="">DOCTYPE</code></h3>
@@ -381,8 +381,8 @@
     <p>There are a few other syntax changes worthy of mentioning:</p>
     
     <ul>
-     <li>HTML now has native support for IRIs. In HTML&nbsp;4 this was only
-     handled as error handling.</li>
+     <li>HTML now has native support for IRIs, though they can only be fully
+     used if the document encoding is UTF-8 or UTF-16.</li>
 
      <li>The <code>lang</code> attribute takes the empty string in addition
      to a valid language identifier, just like <code>xml:lang</code> does in
@@ -476,15 +476,15 @@
       downloading or when performing a series of expensive operations.</p></li>
 
       <li><p><code>time</code> represents a date and/or time.</p></li>
-      
+
       <li><p><code>canvas</code> is used for rendering dynamic bitmap graphics
       on the fly, such as graphs or games.</p></li>
-      
+
       <li><p><code>command</code> represents a command the user can
       invoke.</p></li>
-      
-      <li><p><code>datagrid</code> represents an interactive representation of a
-      tree list or tabular data.</p></li>
+
+      <li><p><code>datagrid</code> represents an interactive representation
+      of a tree, list or tabular data.</p></li>
       
       <li><p><code>details</code> represents additional information or controls
       which the user can obtain on demand.</p></li>
@@ -502,7 +502,7 @@
 &lt;/datalist></code></pre>
       </li>
       
-      <li><p><code>keygen</code> representa control for key pair
+      <li><p><code>keygen</code> represents control for key pair
       generation.</p></li>
 
       <!--
@@ -568,18 +568,19 @@
       element. It is purely advisory.
     
       <li><p>The <code>a</code> and <code>area</code> elements have a new
-      attribute called <code>ping</code> that specifies a space separated list
-      of URIs which have to be pinged when the hyperlink is followed. Currently
+      attribute called <code>ping</code> that specifies a space-separated list
+      of URLs which have to be pinged when the hyperlink is followed. Currently
       user tracking is mostly done through redirects. This attribute allows the
       user agent to inform users which URLs are going to be pinged as well as
       giving privacy-conscious users a way to turn it off.
 
-      <li><p>The <code>area</code> element, for consistency, now has the
+      <li><p>The <code>area</code> element, for consistency with the
+      <code>a</code> and <code>link</code> elements, now also has the
       <code>hreflang</code> and <code>rel</code> attributes.
       
       <li><p>The <code>base</code> element can now have a <code>target</code>
       attribute as well, mainly for consistency with the
-      <code>a</code> element (it is also widely supported). Also, the
+      <code>a</code> element. (This is already widely supported.) Also, the
       <code>target</code> attribute for the <code>a</code> and
       <code>area</code> elements is no longer deprecated, as it is useful in
       Web applications, e.g. in conjunction with <code>iframe</code>.
@@ -741,7 +742,7 @@
       for the underlying platform user interface.</p></li>
 
       <li><p>The <code>menu</code> element is redefined to be useful for
-      actual menus.</p></li>
+      toolbars and context menus.</p></li>
 
       <li><p>The <code>small</code> element now represents small print (for
       side comments and legal print).</p></li>
@@ -1062,16 +1063,16 @@
     <ul>
      <li>A new global attribute called <code>spellcheck</code> has been
      added.</li>
-     <li>Defined that <code>this</code> in the global object returns a
-     <code>WindowProxy</code> object rather than the <code>Window</code>
-     object.</li>
+     <li>Defined that ECMAScript <code>this</code> in the global object
+     returns a <code>WindowProxy</code> object rather than the
+     <code>Window</code> object.</li>
      <li>The <code>value</code> DOM attribute for <code>input</code>
      elements in the File Upload state is now defined.</li>
      <li>Definition of <code>designMode</code> was changed to be more in
      line with legacy implementations.</li>
      <li>The <code>drawImage()</code> method of the 2D drawing API can now
      take a <code>video</code> element as well.</li>
-     <li>The way media elements load resources has been clarified.</li>
+     <li>The way media elements load resources has been changed.</li>
      <li><code>document.domain</code> is now IPv6-compatible.</li>
      <li>The <code>video</code> element gained an <code>autobuffer</code>
      boolean attribute that serves as a hint.</li>
@@ -1095,8 +1096,8 @@
      <code>formmethod</code>, <code>formnovalidate</code>, and
      <code>formtarget</code>.</li>
      <li>A "storage mutex" concept has been added to deal with separate
-     pages trying to change the <code>document.cookie</code> and
-     <code>localStorage</code> object at the same time. The
+     pages trying to change a storage object (<code>document.cookie</code>
+     and <code>localStorage</code>) at the same time. The
      <code>Navigator</code> gained a <code>getStorageUpdates()</code> method
      to allow it to be explicitly released.</li>
      <li>A syntax for SVG similar to MathML is now defined so that SVG can
@@ -1344,7 +1345,7 @@
      policy and renamed to <code>localStorage</code>. Related event
      dispatching has been clarified.
      <li><code>postMessage()</code> API changed. Only the origin of the
-     message is exposed, no longer the URI. It also requires a second
+     message is exposed, no longer the URL. It also requires a second
      argument that indicates the origin of the target document.
      <li>Drag and drop API has got clarification. The
      <code>dataTransfer</code> object now has a <code>types</code>
@@ -1414,6 +1415,7 @@
     James Graham,
     J&uuml;rgen Jeka,
     Maciej Stachowiak,
+    Mark Pilgrim,
     Martijn Wargers,
     Martyn Haigh,
     Masataka Yakura,
Received on Wednesday, 15 April 2009 21:56:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 April 2009 21:56:43 GMT