HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
5response to dbaron's comments entitled 'WA1: Conformance requirements'2006-03-07 01:34
@@ -37,21 +37,21 @@
     <dd><a href="http://www.whatwg.org/specs/web-apps/current-work/">http://www.whatwg.org/specs/web-apps/current-work/</a></dd>
     <dt>Latest version:</dt>
     <dd><a href="http://www.whatwg.org/specs/web-apps/current-work/">http://www.whatwg.org/specs/web-apps/current-work/</a></dd>
     <dt>Previous versions:</dt>
     <dd><a href="http://www.whatwg.org/specs/web-apps/2006-01-01/">http://www.whatwg.org/specs/web-apps/2006-01-01/</a><!-- (<a href="diff-2006-01-01">diffs</a>)--></dd>
     <dd><a href="http://www.whatwg.org/specs/web-apps/2005-09-01/">http://www.whatwg.org/specs/web-apps/2005-09-01/</a><!-- (<a href="diff-2005-09-01">diffs</a>)--></dd>
     <dd>Version history from 2006-03-01 available via Subversion at: <a href="http://svn.whatwg.org/">http://svn.whatwg.org/</a></dd>
     <dt>Editor:</dt>
     <dd>Ian Hickson, Google, ian@hixie.ch</dd>
    </dl>
-   <p class="copyright">&copy; Copyright 2004, 2005 Apple Computer, Inc.,
+   <p class="copyright">&copy; Copyright 2004-2006 Apple Computer, Inc.,
    Mozilla Foundation, and Opera Software ASA.</p>
    <p class="copyright">You are granted a license to use, reproduce
    and create derivative works of this document.</p>
   </div>
 
   <hr>
 
   <h2 class="no-num no-toc" id="abstract">Abstract</h2>
 
   <p>This specification introduces features to HTML and the DOM that
@@ -346,22 +346,22 @@
   Everything else in this specification is normative.</p>
 
   <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
   in the normative parts of this document are to be interpreted as
   described in <a href="#refsRFC2119">[RFC2119]</a>. For readability,
   these words do not appear in all uppercase letters in this
   specification.</p> <!-- XXX but they should be marked up -->
 
   <p>This specification describes the conformance criteria for user
-  agents (implementations and their implementors) and documents (and
-  their authors).</p>
+  agents (relevant to implementors) and documents (relevant to
+  authors).</p>
 
   <p>Conformance requirements phrased as requirements on elements,
   attributes, methods or objects are conformance requirements on user
   agents.</p>
 
   <p>User agents fall into several (overlapping) categories with
   different conformance requirements.</p>
 
   <dl>
 
@@ -488,21 +488,53 @@
     headings">document outlines</span> but increases the nesting level
     for each paragraph and does not increase the nesting level for
     each section would not be conforming.</p>
 
    </dd>
 
    <dt id="editors">Authoring tools and markup generators</dt>
 
    <dd><p>Authoring tools and markup generators must generate
    conforming documents. Conformance criteria that apply to authors
-   also apply to authoring tools, where appropriate.</p></dd>
+   also apply to authoring tools, where appropriate.</p>
+
+   <p class="big-issue">This needs expanding (see source).</p>
+
+<!--
+> The requirement that authoring tools must generate conforming documents
+> should probably also make the distinction between the three types of
+> conformance requirements made in the section on conformance tools.  I
+> would say that authoring tools must generate documents that conform to
+> the first two requirements and should encourage their users to generate
+> documents that conform to the third.  I'd also allow an exception for
+> preservation of nonconformant content across editing operations, since
+> in editors often should not change content unrelated to what is being
+> edited.
+
+I've noted this in the markup for now. I need to take a much closer look
+at the conformance requirements for editors; in particular I've been
+talking to a number of people who implement HTML editors and their
+unanimous feedback is that it is unrealistic to prevent them from
+including presentational markup, because the state of the art in UI does
+not yet have a way of conveying "semantics" in a comprehensive way.
+
+Thus the conformance criteria for editors will probably be changed to
+allow them to include <font> markup while still defining such documents to
+be non-conformant HTML5 documents.
+
+Or something. Like I said, this needs thought (feel free to mail ideas
+and suggestions on this to the list, btw).
+
+-->
+
+
+   </dd>
 
   </dl>
 
   <p>Conformance requirements phrased as algorithms or specific steps
   may be implemented in any manner, so long as the end result is
   equivalent. (In particular, the algorithms defined in this
   specification are intended to be easy to follow, and not intended to
   be performant.)</p>
 
   <p class="note">There is no implied relationship between document
@@ -593,20 +625,22 @@
   <code><var title="">prefix</var>:<var title="">localName</var></code>, as in
   <code>xml:id</code> or <code>svg:rect</code>, it refers to a name
   with the local name <var title="">localName</var> and the namespace given by
   the prefix, as defined by the following table:</p>
 
   <dl>
    <dt><code title="">xml</code></dt>
    <dd><code>http://www.w3.org/XML/1998/namespace</code></dd>
    <dt><code title="">html</code></dt>
    <dd><code>http://www.w3.org/1999/xhtml</code></dd>
+   <dt><code title="">svg</code></dt>
+   <dd><code>http://www.w3.org/2000/svg</code></dd>
   </dl>
 
   <p>For simplicity, terms such as <em>shown</em>, <em>displayed</em>,
   and <em>visible</em> might sometimes be used when referring to the
   way a document is rendered to the user. These terms are not meant to
   imply a visual medium; they must be considered to apply to other
   media in equivalent ways.</p>
 
   <p>This specification uses the term <em>HTML documents</em> to
   generally refer to any use of HTML, ranging from short static

|