[html5] r1157 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2008-01-14 16:08:25 -0800 (Mon, 14 Jan 2008)
New Revision: 1157

Modified:
   index
   source
Log:
[e] (0) s/Macromedia/Adobe/, remove some text I thought I'd already removed (discouraging XHTML use)

Modified: index
===================================================================
--- index	2008-01-14 05:45:25 UTC (rev 1156)
+++ index	2008-01-15 00:08:25 UTC (rev 1157)
@@ -1747,14 +1747,14 @@
    document editing software, etc.
 
   <p>For sophisticated cross-platform applications, there already exist
-   several proprietary solutions (such as Mozilla's XUL and Macromedia's
-   Flash). These solutions are evolving faster than any standards process
-   could follow, and the requirements are evolving even faster. These systems
-   are also significantly more complicated to specify, and are orders of
-   magnitude more difficult to achieve interoperability with, than the
-   solutions described in this document. Platform-specific solutions for such
-   sophisticated applications (for example the MacOS X Core APIs) are even
-   further ahead.
+   several proprietary solutions (such as Mozilla's XUL, Adobe's Flash, or
+   Microsoft's Silverlight). These solutions are evolving faster than any
+   standards process could follow, and the requirements are evolving even
+   faster. These systems are also significantly more complicated to specify,
+   and are orders of magnitude more difficult to achieve interoperability
+   with, than the solutions described in this document. Platform-specific
+   solutions for such sophisticated applications (for example the MacOS X
+   Core APIs) are even further ahead.
 
   <h4 id=relationship><span class=secno>1.1.1. </span>Relationship to HTML
    4.01, XHTML 1.1, DOM2 HTML</h4>
@@ -2447,10 +2447,10 @@
   <p>The second concrete syntax uses XML, and is known as "XHTML5". When a
    document is transmitted with an XML MIME type, such as <code
    title="">application/xhtml+xml</code>, then it is processed by an XML
-   processor by Web browsers, and treated as an "XHTML5" document. Generally
-   speaking, authors are discouraged from trying to use XML on the Web,
-   because XML has much stricter syntax rules than the "HTML5" variant
-   described above, and is relatively newer and therefore less mature.
+   processor by Web browsers, and treated as an "XHTML5" document. Authors
+   are reminded that the processing for XML and HTML differs; in particular,
+   even minor syntax errors will prevent an XML document from being rendered
+   fully, whereas they would be ignored in the "HTML5" syntax.
 
   <p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
    represent the same content. For example, namespaces cannot be represented

Modified: source
===================================================================
--- source	2008-01-14 05:45:25 UTC (rev 1156)
+++ source	2008-01-15 00:08:25 UTC (rev 1157)
@@ -75,13 +75,13 @@
   software), document editing software, etc.</p>
 
   <p>For sophisticated cross-platform applications, there already
-  exist several proprietary solutions (such as Mozilla's XUL and
-  Macromedia's Flash). These solutions are evolving faster than any
-  standards process could follow, and the requirements are evolving
-  even faster. These systems are also significantly more complicated
-  to specify, and are orders of magnitude more difficult to achieve
-  interoperability with, than the solutions described in this
-  document. Platform-specific solutions for such sophisticated
+  exist several proprietary solutions (such as Mozilla's XUL, Adobe's
+  Flash, or Microsoft's Silverlight). These solutions are evolving
+  faster than any standards process could follow, and the requirements
+  are evolving even faster. These systems are also significantly more
+  complicated to specify, and are orders of magnitude more difficult
+  to achieve interoperability with, than the solutions described in
+  this document. Platform-specific solutions for such sophisticated
   applications (for example the MacOS X Core APIs) are even further
   ahead.</p>
 
@@ -849,10 +849,10 @@
   "XHTML5". When a document is transmitted with an XML MIME type, such
   as <code title="">application/xhtml+xml</code>, then it is processed
   by an XML processor by Web browsers, and treated as an "XHTML5"
-  document. Generally speaking, authors are discouraged from trying to
-  use XML on the Web, because XML has much stricter syntax rules than
-  the "HTML5" variant described above, and is relatively newer and
-  therefore less mature.</p>
+  document. Authors are reminded that the processing for XML and HTML
+  differs; in particular, even minor syntax errors will prevent an XML
+  document from being rendered fully, whereas they would be ignored in
+  the "HTML5" syntax.</p>
 
   <p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
   represent the same content. For example, namespaces cannot be