[html5] r4028 - [e] (0) Other applicable specifications definition. Fixing http://www.w3.org/Bug [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Sep 28 19:41:24 PDT 2009
Author: ianh
Date: 2009-09-28 19:41:23 -0700 (Mon, 28 Sep 2009)
New Revision: 4028
Modified:
index
source
Log:
[e] (0) Other applicable specifications definition.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7659
Modified: index
===================================================================
--- index 2009-09-29 02:14:02 UTC (rev 4027)
+++ index 2009-09-29 02:41:23 UTC (rev 4028)
@@ -2295,14 +2295,14 @@
allowing only users of specific user agents to access the content in
question.</p>
- <p>If markup extensions are needed, they should be done using XML,
- with elements or attributes from custom namespaces. If DOM
- extensions are needed, the members should be prefixed by
- vendor-specific strings to prevent clashes with future versions of
- this specification. Extensions must be defined so that the use of
- extensions neither contradicts nor causes the non-conformance of
- functionality defined in the specification.</p> <!-- thanks to QA
- Framework -->
+ <p>If vendor-specific markup extensions are needed, they should be
+ done using XML, with elements or attributes from custom
+ namespaces. If such DOM extensions are needed, the members should be
+ prefixed by vendor-specific strings to prevent clashes with future
+ versions of this specification. Extensions must be defined so that
+ the use of extensions neither contradicts nor causes the
+ non-conformance of functionality defined in the specification.</p>
+ <!-- thanks to QA Framework -->
<div class=example>
@@ -2317,7 +2317,18 @@
</div>
- <p>User agents must treat elements and attributes that they do not
+ <hr><p>When vendor-neutral extensions to this specification are needed,
+ either this specification can be updated accordingly, or an
+ extension specification can be written that overrides the
+ requirements in this specification. When someone applying this
+ specification to their activities decides that they will recognise
+ the requirements of such an extension specification, it becomes an
+ <dfn id=other-applicable-specifications title="other applicable specifications">applicable
+ specification</dfn> for the purposes of conformance requirements in
+ this specification.</p>
+ <!-- http://www.w3.org/mid/17E341CD-E790-422C-9F9A-69347EE01CEB@iki.fi -->
+
+ <hr><p>User agents must treat elements and attributes that they do not
understand as semantically neutral; leaving them in the DOM (for DOM
processors), and styling them according to CSS (for CSS processors),
but not inferring any meaning from them.</p>
@@ -7385,9 +7396,8 @@
<p>Authors must not use elements, attributes, and attribute values
for purposes other than their appropriate intended semantic
purpose. Authors must not use elements, attributes, and attribute
- values that are not permitted by this specification or other
- applicable specifications.</p>
- <!-- http://www.w3.org/mid/17E341CD-E790-422C-9F9A-69347EE01CEB@iki.fi -->
+ values that are not permitted by this specification or <a href=#other-applicable-specifications>other
+ applicable specifications</a>.</p>
<div class=example>
<p>For example, the following document is non-conforming, despite
@@ -7617,7 +7627,7 @@
<p>The <code><a href=#htmlunknownelement>HTMLUnknownElement</a></code> interface must be used for
<a href=#html-elements>HTML elements</a> that are not defined by this
- specification (or other applicable specifications).</p>
+ specification (or <a href=#other-applicable-specifications>other applicable specifications</a>).</p>
</div>
@@ -64785,8 +64795,8 @@
given in the given token.</p>
<p>The interface appropriate for an element in the <a href=#html-namespace-0>HTML
- namespace</a> that is not defined in this specification (or other
- applicable specifications) is
+ namespace</a> that is not defined in this specification (or
+ <a href=#other-applicable-specifications>other applicable specifications</a>) is
<code><a href=#htmlunknownelement>HTMLUnknownElement</a></code>. Element in other namespaces whose
interface is not defined by that namespace's specification must use
the interface <code>Element</code>.</p>
Modified: source
===================================================================
--- source 2009-09-29 02:14:02 UTC (rev 4027)
+++ source 2009-09-29 02:41:23 UTC (rev 4028)
@@ -1336,14 +1336,14 @@
allowing only users of specific user agents to access the content in
question.</p>
- <p>If markup extensions are needed, they should be done using XML,
- with elements or attributes from custom namespaces. If DOM
- extensions are needed, the members should be prefixed by
- vendor-specific strings to prevent clashes with future versions of
- this specification. Extensions must be defined so that the use of
- extensions neither contradicts nor causes the non-conformance of
- functionality defined in the specification.</p> <!-- thanks to QA
- Framework -->
+ <p>If vendor-specific markup extensions are needed, they should be
+ done using XML, with elements or attributes from custom
+ namespaces. If such DOM extensions are needed, the members should be
+ prefixed by vendor-specific strings to prevent clashes with future
+ versions of this specification. Extensions must be defined so that
+ the use of extensions neither contradicts nor causes the
+ non-conformance of functionality defined in the specification.</p>
+ <!-- thanks to QA Framework -->
<div class="example">
@@ -1360,6 +1360,21 @@
</div>
+ <hr>
+
+ <p>When vendor-neutral extensions to this specification are needed,
+ either this specification can be updated accordingly, or an
+ extension specification can be written that overrides the
+ requirements in this specification. When someone applying this
+ specification to their activities decides that they will recognise
+ the requirements of such an extension specification, it becomes an
+ <dfn title="other applicable specifications">applicable
+ specification</dfn> for the purposes of conformance requirements in
+ this specification.</p>
+ <!-- http://www.w3.org/mid/17E341CD-E790-422C-9F9A-69347EE01CEB@iki.fi -->
+
+ <hr>
+
<p>User agents must treat elements and attributes that they do not
understand as semantically neutral; leaving them in the DOM (for DOM
processors), and styling them according to CSS (for CSS processors),
@@ -7447,9 +7462,8 @@
<p>Authors must not use elements, attributes, and attribute values
for purposes other than their appropriate intended semantic
purpose. Authors must not use elements, attributes, and attribute
- values that are not permitted by this specification or other
- applicable specifications.</p>
- <!-- http://www.w3.org/mid/17E341CD-E790-422C-9F9A-69347EE01CEB@iki.fi -->
+ values that are not permitted by this specification or <span>other
+ applicable specifications</span>.</p>
<div class="example">
<p>For example, the following document is non-conforming, despite
@@ -7679,7 +7693,7 @@
<p>The <code>HTMLUnknownElement</code> interface must be used for
<span>HTML elements</span> that are not defined by this
- specification (or other applicable specifications).</p>
+ specification (or <span>other applicable specifications</span>).</p>
</div>
@@ -79839,8 +79853,8 @@
given in the given token.</p>
<p>The interface appropriate for an element in the <span>HTML
- namespace</span> that is not defined in this specification (or other
- applicable specifications) is
+ namespace</span> that is not defined in this specification (or
+ <span>other applicable specifications</span>) is
<code>HTMLUnknownElement</code>. Element in other namespaces whose
interface is not defined by that namespace's specification must use
the interface <code>Element</code>.</p>
More information about the Commit-Watchers
mailing list