Skip to content

Commit

Permalink
[e] (0) explain what a conforming document is
Browse files Browse the repository at this point in the history 
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9178

git-svn-id: http://svn.whatwg.org/webapps@4932 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Apr 1, 2010
1 parent 1302a09 commit 6996947
Show file tree
Hide file tree
Showing 3 changed files with 69 additions and 27 deletions.
32 changes: 23 additions & 9 deletions complete.html
View file
Expand Up @@ -2767,12 +2767,19 @@ <h3 id=conformance-requirements><span class=secno>2.2 </span>Conformance require
documents<span class=impl> (relevant to authors and authoring tool
implementors)</span>.</p>

<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.</p>
<p><dfn id=conforming-documents>Conforming documents</dfn> are those that comply with all
the conformance criteria for documents. For readability, some of
these conformance requirements are phrased as conformance
requirements on authors; such requirements are implicitly
requirements on documents: by definition, all documents are assumed
to have had an author. (In some cases, that author may itself be a
user agent &mdash; such user agents are subject to additional rules,
as explained below.)</p>

<p class=example>For example, if a requirement states that
"authors must not use the <code title="">foobar</code> element", it
would imply that documents are not allowed to contain elements named
<code title="">foobar</code>.</p>

<div class=impl>

Expand Down Expand Up @@ -2934,9 +2941,9 @@ <h3 id=conformance-requirements><span class=secno>2.2 </span>Conformance require

<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>
<p>Authoring tools and markup generators must generate
<a href=#conforming-documents>conforming documents</a>. Conformance criteria that apply
to authors also apply to authoring tools, where appropriate.</p>

<p>Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
Expand Down Expand Up @@ -3018,6 +3025,13 @@ <h3 id=conformance-requirements><span class=secno>2.2 </span>Conformance require



<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.</p>

<p>For compatibility with existing content and prior specifications,
this specification describes two authoring formats: one based on XML
(referred to as <a href=#the-xhtml-syntax>the XHTML syntax</a>), and one using a <a href=#writing>custom format</a> inspired by SGML (referred to as
Expand Down
32 changes: 23 additions & 9 deletions index
View file
Expand Up @@ -2665,12 +2665,19 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
documents<span class=impl> (relevant to authors and authoring tool
implementors)</span>.</p>

<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.</p>
<p><dfn id=conforming-documents>Conforming documents</dfn> are those that comply with all
the conformance criteria for documents. For readability, some of
these conformance requirements are phrased as conformance
requirements on authors; such requirements are implicitly
requirements on documents: by definition, all documents are assumed
to have had an author. (In some cases, that author may itself be a
user agent &mdash; such user agents are subject to additional rules,
as explained below.)</p>

<p class=example>For example, if a requirement states that
"authors must not use the <code title="">foobar</code> element", it
would imply that documents are not allowed to contain elements named
<code title="">foobar</code>.</p>

<div class=impl>

Expand Down Expand Up @@ -2832,9 +2839,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

<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>
<p>Authoring tools and markup generators must generate
<a href=#conforming-documents>conforming documents</a>. Conformance criteria that apply
to authors also apply to authoring tools, where appropriate.</p>

<p>Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
Expand Down Expand Up @@ -2916,6 +2923,13 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d



<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.</p>

<p>For compatibility with existing content and prior specifications,
this specification describes two authoring formats: one based on XML
(referred to as <a href=#the-xhtml-syntax>the XHTML syntax</a>), and one using a <a href=#writing>custom format</a> inspired by SGML (referred to as
Expand Down
32 changes: 23 additions & 9 deletions source
View file
Expand Up @@ -1643,12 +1643,19 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
documents<span class="impl"> (relevant to authors and authoring tool
implementors)</span>.</p>

<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.</p>
<p><dfn>Conforming documents</dfn> are those that comply with all
the conformance criteria for documents. For readability, some of
these conformance requirements are phrased as conformance
requirements on authors; such requirements are implicitly
requirements on documents: by definition, all documents are assumed
to have had an author. (In some cases, that author may itself be a
user agent &mdash; such user agents are subject to additional rules,
as explained below.)</p>

<p class="example">For example, if a requirement states that
"authors must not use the <code title="">foobar</code> element", it
would imply that documents are not allowed to contain elements named
<code title="">foobar</code>.</p>

<div class="impl">

Expand Down Expand Up @@ -1825,9 +1832,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

<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>
<p>Authoring tools and markup generators must generate
<span>conforming documents</span>. Conformance criteria that apply
to authors also apply to authoring tools, where appropriate.</p>

<p>Authoring tools are exempt from the strict requirements of
using elements only for their specified purpose, but only to the
Expand Down Expand Up @@ -1914,6 +1921,13 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

<!--END microdata-->

<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
requirements. User agents are not free to handle non-conformant
documents as they please; the processing model described in this
specification applies to implementations regardless of the
conformity of the input documents.</p>

<p>For compatibility with existing content and prior specifications,
this specification describes two authoring formats: one based on XML
(referred to as <span>the XHTML syntax</span>), and one using a <a
Expand Down

0 comments on commit 6996947

Please sign in to comment.