Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
response to dbaron's comments entitled 'WA1: Conformance requirements'
git-svn-id: http://svn.whatwg.org/webapps@5 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Mar 7, 2006
1 parent 1031712 commit 89a273d
Show file tree
Hide file tree
Showing 2 changed files with 75 additions and 9 deletions.
42 changes: 37 additions & 5 deletions index
Expand Up @@ -36,7 +36,7 @@

<h1 id="web-applications">Web Applications 1.0</h1>

<h2 class="no-num no-toc" id="working">Working Draft &mdash; 3 March 2006</h2>
<h2 class="no-num no-toc" id="working">Working Draft &mdash; 7 March 2006</h2>

<p>You can take part in this work. <a
href="http://www.whatwg.org/mailing-list">Join the working group's
Expand Down Expand Up @@ -69,7 +69,7 @@
<dd>Ian Hickson, Google, ian@hixie.ch
</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
Expand Down Expand Up @@ -1289,8 +1289,7 @@
<!-- 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).
(relevant to implementors) and documents (relevant to authors).

<p>Conformance requirements phrased as requirements on elements,
attributes, methods or objects are conformance requirements on user
Expand Down Expand Up @@ -1420,7 +1419,36 @@
<dd>
<p>Authoring tools and markup generators must generate conforming
documents. Conformance criteria that apply to authors also apply to
authoring tools, where appropriate.
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).

-->

</dl>

<p>Conformance requirements phrased as algorithms or specific steps may be
Expand Down Expand Up @@ -1521,6 +1549,10 @@
<dt><code title="">html</code>

<dd><code>http://www.w3.org/1999/xhtml</code>

<dt><code title="">svg</code>

<dd><code>http://www.w3.org/2000/svg</code>
</dl>

<p>For simplicity, terms such as <em>shown</em>, <em>displayed</em>, and
Expand Down
42 changes: 38 additions & 4 deletions source
Expand Up @@ -44,7 +44,7 @@
<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>
Expand Down Expand Up @@ -353,8 +353,8 @@
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
Expand Down Expand Up @@ -495,7 +495,39 @@

<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>

Expand Down Expand Up @@ -600,6 +632,8 @@
<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>,
Expand Down

0 comments on commit 89a273d

Please sign in to comment.