mike: refined part of Abstract to indicate htmlr is not intended only to complement the HTML5 spec, but also other HTML WG deliverables. (bug 10083)

mike: refined part of Abstract to indicate htmlr is not intended only to
complement the HTML5 spec, but also other HTML WG deliverables. (bug
10083)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10083

http://dev.w3.org/cvsweb/html5/markup/spec.html?r1=1.234&r2=1.235&f=h

===================================================================
RCS file: /sources/public/html5/markup/Overview.html,v
retrieving revision 1.429
retrieving revision 1.430
diff -u -d -r1.429 -r1.430
--- Overview.html 7 Jul 2010 01:11:47 -0000 1.429
+++ Overview.html 7 Jul 2010 08:04:56 -0000 1.430
@@ -44,7 +44,9 @@
       criteria defined in the
       <a href="http://dev.w3.org/html5/spec/">HTML5: A vocabulary and associated APIs for HTML and XHTML</a>
       specification
-      <a href="references.html#refsHTML5">[HTML5]</a>.
+      <a href="references.html#refsHTML5">[HTML5]</a>,
+      as well as information in other deliverables published by
+      the HTML Working Group.
       By design, this reference does not describe related APIs in detail,
       nor attempt to explain how implementations that are
       consumers of HTML content are meant to process documents

Index: spec.html
===================================================================
RCS file: /sources/public/html5/markup/spec.html,v
retrieving revision 1.234
retrieving revision 1.235
diff -u -d -r1.234 -r1.235
--- spec.html 7 Jul 2010 01:11:51 -0000 1.234
+++ spec.html 7 Jul 2010 08:04:57 -0000 1.235
@@ -43,7 +43,9 @@
       criteria defined in the
       <a href="http://dev.w3.org/html5/spec/">HTML5: A vocabulary and associated APIs for HTML and XHTML</a>
       specification
-      <a href="references.html#refsHTML5">[HTML5]</a>.
+      <a href="references.html#refsHTML5">[HTML5]</a>,
+      as well as information in other deliverables published by
+      the HTML Working Group.
       By design, this reference does not describe related APIs in detail,
       nor attempt to explain how implementations that are
       consumers of HTML content are meant to process documents

Received on Wednesday, 7 July 2010 08:05:48 UTC