[html5] r5923 - [giow] (0) Make an explicit conformance class for people who implement the rende [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-03-01 15:18:23 -0800 (Tue, 01 Mar 2011)
New Revision: 5923

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Make an explicit conformance class for people who implement the rendering section.

Modified: complete.html
===================================================================
--- complete.html	2011-03-01 22:57:14 UTC (rev 5922)
+++ complete.html	2011-03-01 23:18:23 UTC (rev 5923)
@@ -3053,6 +3053,21 @@
 
    </dd>
 
+   <dt id=renderingUA>Visual user agents that support the suggested default rendering</dt>
+
+   <dd>
+
+    <p>User agents, whether interactive or not, may be designated
+    (possibly as a user option) as supporting the suggested default
+    rendering defined by this specification.</p>
+
+    <p>User agents that are designated as supporting the suggested
+    default rendering must implement the rules in <a href=#rendering>the rendering section</a> that that section
+    defines as the behavior that user agents are <em>expected</em> to
+    implement.</p>
+
+   </dd>
+
    <dt><dfn id=non-scripted>User agents with no scripting support</dfn></dt>
 
    <dd>
@@ -3072,6 +3087,7 @@
 
    </dd>
 
+
    <dt>Conformance checkers</dt>
 
    <dd id=conformance-checkers>
@@ -3128,6 +3144,7 @@
     </div>
    </dd>
 
+
    <dt>Data mining tools</dt>
 
    <dd id=data-mining>
@@ -3143,6 +3160,7 @@
 
    </dd>
 
+
    <dt id=editors>Authoring tools and markup generators</dt>
 
    <dd>
@@ -85675,7 +85693,11 @@
   by the documents' authors. So as to avoid confusion regarding the
   normativity of this section, RFC2119 terms have not been used.
   Instead, the term "expected" is used to indicate behavior that will
-  lead to this experience.</i></p>
+  lead to this experience. For the purposes of conformance for user
+  agents designated as <a href=#renderingUA>supporting the suggested
+  default rendering</a>, the term "expected" in this section has the
+  same conformance implications as the RFC2119-defined term
+  "must".</i></p>
 
 
   <h3 id=introduction-12><span class=secno>14.1 </span>Introduction</h3>

Modified: index
===================================================================
--- index	2011-03-01 22:57:14 UTC (rev 5922)
+++ index	2011-03-01 23:18:23 UTC (rev 5923)
@@ -3033,6 +3033,21 @@
 
    </dd>
 
+   <dt id=renderingUA>Visual user agents that support the suggested default rendering</dt>
+
+   <dd>
+
+    <p>User agents, whether interactive or not, may be designated
+    (possibly as a user option) as supporting the suggested default
+    rendering defined by this specification.</p>
+
+    <p>User agents that are designated as supporting the suggested
+    default rendering must implement the rules in <a href=#rendering>the rendering section</a> that that section
+    defines as the behavior that user agents are <em>expected</em> to
+    implement.</p>
+
+   </dd>
+
    <dt><dfn id=non-scripted>User agents with no scripting support</dfn></dt>
 
    <dd>
@@ -3052,6 +3067,7 @@
 
    </dd>
 
+
    <dt>Conformance checkers</dt>
 
    <dd id=conformance-checkers>
@@ -3108,6 +3124,7 @@
     </div>
    </dd>
 
+
    <dt>Data mining tools</dt>
 
    <dd id=data-mining>
@@ -3123,6 +3140,7 @@
 
    </dd>
 
+
    <dt id=editors>Authoring tools and markup generators</dt>
 
    <dd>
@@ -81646,7 +81664,11 @@
   by the documents' authors. So as to avoid confusion regarding the
   normativity of this section, RFC2119 terms have not been used.
   Instead, the term "expected" is used to indicate behavior that will
-  lead to this experience.</i></p>
+  lead to this experience. For the purposes of conformance for user
+  agents designated as <a href=#renderingUA>supporting the suggested
+  default rendering</a>, the term "expected" in this section has the
+  same conformance implications as the RFC2119-defined term
+  "must".</i></p>
 
 
   <h3 id=introduction-10><span class=secno>12.1 </span>Introduction</h3>

Modified: source
===================================================================
--- source	2011-03-01 22:57:14 UTC (rev 5922)
+++ source	2011-03-01 23:18:23 UTC (rev 5923)
@@ -1945,6 +1945,22 @@
 
    </dd>
 
+   <dt id="renderingUA">Visual user agents that support the suggested default rendering</dt>
+
+   <dd>
+
+    <p>User agents, whether interactive or not, may be designated
+    (possibly as a user option) as supporting the suggested default
+    rendering defined by this specification.</p>
+
+    <p>User agents that are designated as supporting the suggested
+    default rendering must implement the rules in <a
+    href="#rendering">the rendering section</a> that that section
+    defines as the behavior that user agents are <em>expected</em> to
+    implement.</p>
+
+   </dd>
+
    <dt><dfn id="non-scripted">User agents with no scripting support</dfn></dt>
 
    <dd>
@@ -1964,6 +1980,7 @@
 
    </dd>
 
+
    <dt>Conformance checkers</dt>
 
    <dd id="conformance-checkers">
@@ -2030,6 +2047,7 @@
     </div>
    </dd>
 
+
    <dt>Data mining tools</dt>
 
    <dd id="data-mining">
@@ -2046,6 +2064,7 @@
 
    </dd>
 
+
    <dt id="editors">Authoring tools and markup generators</dt>
 
    <dd>
@@ -96969,7 +96988,11 @@
   by the documents' authors. So as to avoid confusion regarding the
   normativity of this section, RFC2119 terms have not been used.
   Instead, the term "expected" is used to indicate behavior that will
-  lead to this experience.</i></p>
+  lead to this experience. For the purposes of conformance for user
+  agents designated as <a href="#renderingUA">supporting the suggested
+  default rendering</a>, the term "expected" in this section has the
+  same conformance implications as the RFC2119-defined term
+  "must".</i></p>
 
 
   <h3>Introduction</h3>