[e] (0) clarification by request

git-svn-id: http://svn.whatwg.org/webapps@5982 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 8 April 2011</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 11 April 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
         specification marked with the following punctuation: --><!--!--><!-- These are issues that are known to the editor but cannot be
         currently fixed because they were introduced by Sam Ruby
         acting as chairman of the W3C HTML Working Group as part of
-        the HTML Working Group Decision Process. In theory we could
-        fork the WHATWG copy of the spec, but doing so would introduce
+        the HTML Working Group Decision Process. (Maciej wants it to
+        be known he also accepts responsibility for this decision, as
+        he was supposed to review it.) In theory we could fork the
+        WHATWG copy of the spec, but doing so would introduce
         normative differences between the W3C and WHATWG specs and
         these issues are not worth the hassle that this would cause.
         We'll probably be able to fix them some day, but for now we

index

 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 8 April 2011</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 11 April 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
         specification marked with the following punctuation: --><!--!--><!-- These are issues that are known to the editor but cannot be
         currently fixed because they were introduced by Sam Ruby
         acting as chairman of the W3C HTML Working Group as part of
-        the HTML Working Group Decision Process. In theory we could
-        fork the WHATWG copy of the spec, but doing so would introduce
+        the HTML Working Group Decision Process. (Maciej wants it to
+        be known he also accepts responsibility for this decision, as
+        he was supposed to review it.) In theory we could fork the
+        WHATWG copy of the spec, but doing so would introduce
         normative differences between the W3C and WHATWG specs and
         these issues are not worth the hassle that this would cause.
         We'll probably be able to fix them some day, but for now we

source

@@ -36,8 +36,10 @@
    <!-- These are issues that are known to the editor but cannot be
         currently fixed because they were introduced by Sam Ruby
         acting as chairman of the W3C HTML Working Group as part of
-        the HTML Working Group Decision Process. In theory we could
-        fork the WHATWG copy of the spec, but doing so would introduce
+        the HTML Working Group Decision Process. (Maciej wants it to
+        be known he also accepts responsibility for this decision, as
+        he was supposed to review it.) In theory we could fork the
+        WHATWG copy of the spec, but doing so would introduce
         normative differences between the W3C and WHATWG specs and
         these issues are not worth the hassle that this would cause.
         We'll probably be able to fix them some day, but for now we