Typo fixes, wording simplifications, defined error handling for lone …

…LIs, defined handling for value attribute better, added some TODO notes from Henri regarding content model rules

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

index

@@ -36,7 +36,7 @@
 
    <h1 id="web-applications">Web Applications 1.0</h1>
 
-   <h2 class="no-num no-toc" id="working">Working Draft &mdash; 8 March 2006</h2>
+   <h2 class="no-num no-toc" id="working">Working Draft &mdash; 10 March 2006</h2>
 
    <p>You can take part in this work. <a
     href="http://www.whatwg.org/mailing-list">Join the working group's
@@ -1521,7 +1521,7 @@ and suggestions on this to the list, btw).
    stating that it does not apply to the other format, as in "for HTML, ...
    (this does not apply to XHTML)".
 
-  <p>The readability, the term URI is used to refer to both ASCII URIs and
+  <p>For readability, the term URI is used to refer to both ASCII URIs and
    Unicode IRIs, as those terms are defined by <a
    href="#refsRFC3986">[RFC3986]</a> and <a href="#refsRFC3987">[RFC3987]</a>
    respectively. On the rare occasions where IRIs are not allowed but ASCII
@@ -1758,10 +1758,11 @@ and suggestions on this to the list, btw).
    <code>EventListener</code>, with the argument called <code>event</code>.
    Such attributes are added as non-capture event listeners of the type given
    by their name (without the leading <code>on</code> prefix). Only
-   attributes actually defined to exist by specifications implemented by the
-   UA (e.g. HTML, Web Forms 2, Web
+   attributes actually defined <!--to
+  exist--> by specifications
+   implemented by the UA (e.g. HTML, Web Forms 2, Web
    Apps<!-- XXX update this once the specs are merged-->) are actually
-   registered, however; for example if an author created an
+   registered, however. If, for example, an author created an
    <code>onfoo</code> attribute, it would not be fired for <code>foo</code>
    events.
 
@@ -2377,8 +2378,8 @@ and suggestions on this to the list, btw).
    title="WIP"><a href="#wip">[WIP]</a></span></h4>
 
   <p>User agents must support the following common attributes on all elements
-   in the HTML namespace (including elements that are not defined to exist by
-   this specification).
+   in the HTML namespace (including elements that are not defined
+   <!--to exist--> by this specification).
 
   <dl>
    <dt><dfn id="id" title="attr-id"><code>id</code></dfn>
@@ -4754,6 +4755,12 @@ To move the error from the markup to the rhyming.&lt;/p&gt;</pre>
   </dl>
 
   <p>The <code><a href="#li0">li</a></code> element represents a list item.
+   If its parent element is an <code><a href="#ol0">ol</a></code>, <code><a
+   href="#ul0">ul</a></code>, or <code><a href="#menu0">menu</a></code>
+   element, then the element is an item of the parent element's list, as
+   defined for those elements. Otherwise, the list item has no defined
+   list-related relationship to any other <code><a href="#li0">li</a></code>
+   element.
 
   <p>When the list item is the child of an <code><a href="#ol0">ol</a></code>
    or <code><a href="#ul0">ul</a></code> element, the content model of the
@@ -4797,9 +4804,9 @@ To move the error from the markup to the rhyming.&lt;/p&gt;</pre>
    number, it is treated as if the attribute was absent. The attribute has no
    default value.
 
-  <p>The <code><a href="#value">value</a></code> attribute is processed by
-   the parent <code><a href="#ol0">ol</a></code> element, if there is one. If
-   there is not, the attribute has no effect.
+  <p>The <code><a href="#value">value</a></code> attribute is processed
+   relative to the element's parent <code><a href="#ol0">ol</a></code>
+   element, if there is one. If there is not, the attribute has no effect.
 
   <p>The <dfn id="value0" title="dom-value"><code>value</code></dfn> DOM
    attribute must <span><a href="#reflect">reflect</a></span> the value of
@@ -23973,4 +23980,30 @@ prevent terminology clash with CSS.
    There are various cases (marked) where EOF handling is undefined
    Interaction with the "load" event is undefined
 
+
+hsivonen:
+> To make document conformance a more useful concept for the purpose of catching
+> author errors, I suggest that the following attributes be made required:
+> href and rel on link
+> href on base
+> name and content on meta (other than the encoding decl)
+> src on img
+> code, height and width on applet
+> name and value on param
+...
+> To allow user agents see whether the author provided the empty string as the
+> alternative text of whether the author just didn't care, I suggest that the
+> alt attribute on img be made optional.
+(i agree -ian)
+...
+> On the other hand, I have doubts about the requirement of significant
+> inline content. When the W3C said that paragraphs mustn't be empty,
+> various applications started emitting <p>&nbsp;</p>. If the WHAT WG says
+> that paragraphs must contend significant inline content, are the
+> developers of those applications suddenly going to decide not to allow
+> them to paragraphs to be saved or are they going to come up with an even
+> more crufty work-around to comply with the machine-checkable
+> requirements of the spec?
+(i agree, i think we should drop "significant inline content". -ian)
+
 -->

source

@@ -605,7 +605,7 @@ and suggestions on this to the list, btw).
   out by explicitly stating that it does not apply to the other
   format, as in "for HTML, ... (this does not apply to XHTML)".</p>
 
-  <p>The readability, the term URI is used to refer to both ASCII URIs
+  <p>For readability, the term URI is used to refer to both ASCII URIs
   and Unicode IRIs, as those terms are defined by <a
   href="#refsRFC3986">[RFC3986]</a> and <a
   href="#refsRFC3987">[RFC3987]</a> respectively. On the rare
@@ -846,11 +846,11 @@ and suggestions on this to the list, btw).
   implementing <code>EventListener</code>, with the argument called
   <code>event</code>. Such attributes are added as non-capture event
   listeners of the type given by their name (without the leading
-  <code>on</code> prefix). Only attributes actually defined to exist
-  by specifications implemented by the UA (e.g. HTML, Web Forms 2, Web
-  Apps<!-- XXX update this once the specs are merged-->) are actually
-  registered, however; for example if an author created an
-  <code>onfoo</code> attribute, it would not be fired for
+  <code>on</code> prefix). Only attributes actually defined <!--to
+  exist--> by specifications implemented by the UA (e.g. HTML, Web
+  Forms 2, Web Apps<!-- XXX update this once the specs are merged-->)
+  are actually registered, however. If, for example, an author created
+  an <code>onfoo</code> attribute, it would not be fired for
   <code>foo</code> events.</p>
 
   <p id="scopeResolution">The scope chain for ECMAScript executed in
@@ -1459,7 +1459,7 @@ and suggestions on this to the list, btw).
 
   <p>User agents must support the following common attributes on all
   elements in the HTML namespace (including elements that are not
-  defined to exist by this specification).</p>
+  defined <!--to exist--> by this specification).</p>
 
   <dl>
 
@@ -3503,7 +3503,12 @@ To move the error from the markup to the rhyming.&lt;/p&gt;</pre>
    </dd>
   </dl>
 
-  <p>The <code>li</code> element represents a list item.</p>
+  <p>The <code>li</code> element represents a list item. If its parent
+  element is an <code>ol</code>, <code>ul</code>, or <code>menu</code>
+  element, then the element is an item of the parent element's list,
+  as defined for those elements. Otherwise, the list item has no
+  defined list-related relationship to any other <code>li</code>
+  element.</p>
 
   <p>When the list item is the child of an <code>ol</code> or
   <code>ul</code> element, the content model of the item depends on
@@ -3544,9 +3549,9 @@ To move the error from the markup to the rhyming.&lt;/p&gt;</pre>
   number, it is treated as if the attribute was absent. The attribute
   has no default value.</p>
 
-  <p>The <code>value</code> attribute is processed by the parent
-  <code>ol</code> element, if there is one. If there is not, the
-  attribute has no effect.</p>
+  <p>The <code>value</code> attribute is processed relative to the
+  element's parent <code>ol</code> element, if there is one. If there
+  is not, the attribute has no effect.</p>
 
   <p>The <dfn title="dom-value"><code>value</code></dfn> DOM attribute
   must <span>reflect</span> the value of the <code>value</code>
@@ -20988,6 +20993,32 @@ prevent terminology clash with CSS.
    There are various cases (marked) where EOF handling is undefined
    Interaction with the "load" event is undefined
 
+
+hsivonen:
+> To make document conformance a more useful concept for the purpose of catching
+> author errors, I suggest that the following attributes be made required:
+> href and rel on link
+> href on base
+> name and content on meta (other than the encoding decl)
+> src on img
+> code, height and width on applet
+> name and value on param
+...
+> To allow user agents see whether the author provided the empty string as the
+> alternative text of whether the author just didn't care, I suggest that the
+> alt attribute on img be made optional.
+(i agree -ian)
+...
+> On the other hand, I have doubts about the requirement of significant
+> inline content. When the W3C said that paragraphs mustn't be empty,
+> various applications started emitting <p>&nbsp;</p>. If the WHAT WG says
+> that paragraphs must contend significant inline content, are the
+> developers of those applications suddenly going to decide not to allow
+> them to paragraphs to be saved or are they going to come up with an even
+> more crufty work-around to comply with the machine-checkable
+> requirements of the spec?
+(i agree, i think we should drop "significant inline content". -ian)
+
 -->