<h2>Conformance</h2>

Author: dirkschulze

css3-transforms/ChangeLog

@@ -1,3 +1,6 @@
+2013-03-11  Dirk Schulze  <dschulze@adobe.com>
+    Add conformance section.
+
 2012-11-13 dschulze@adobe.com
     Add defintions for keywords on 'transform-origin' and 'perspective-origin'.
 

css3-transforms/Overview.html

@@ -12,11 +12,11 @@
    rel=dcterms.rights>
   <meta content="CSS Transforms" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2013-02-05 name=dcterms.issued>
+  <meta content=2013-03-12 name=dcterms.issued>
   <meta content="http://dev.w3.org/csswg/css3-transforms/"
    name=dcterms.creator>
   <meta content=W3C name=dcterms.publisher>
-  <meta content="http://www.w3.org/TR/2013/ED-css3-transforms-20130205/"
+  <meta content="http://dev.w3.org/csswg/css3-transforms/"
    name=dcterms.identifier>
   <link href="../default.css" rel=stylesheet type="text/css">
   <script defer=defer
@@ -37,15 +37,14 @@
 
    <h1>CSS Transforms</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 5 February
-    2013</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 12 March 2013</h2>
 
    <dl>
     <dt>This version:
 
     <dd> <a
-     href="http://www.w3.org/TR/2013/ED-css3-transforms-20130205/">http://dev.w3.org/csswg/css3-transforms/</a>
-     <!--http://www.w3.org/TR/2013/WD-css3-transforms-20130205/-->
+     href="http://dev.w3.org/csswg/css3-transforms/">http://dev.w3.org/csswg/css3-transforms/</a>
+     <!--http://www.w3.org/TR/2013/WD-css3-transforms-20130312/-->
 
     <dt>Latest version:
 
@@ -324,7 +323,9 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
    <li><a href="#mathematical-description"><span class=secno>21. </span>
     Mathematical Description of Transform Functions </a>
 
-   <li><a href="#references"><span class=secno>22. </span>References</a>
+   <li><a href="#conformance"><span class=secno>22. </span>Conformance</a>
+
+   <li><a href="#references"><span class=secno>23. </span>References</a>
     <ul class=toc>
      <li class=no-num><a href="#normative-references">Normative
       references</a>
@@ -3373,7 +3374,127 @@ <h2 id=mathematical-description><span class=secno>21. </span> Mathematical
     height=106 src=perspective.png width=143>
   </ul>
 
-  <h2 id=references><span class=secno>22. </span>References</h2>
+  <h2 id=conformance><span class=secno>22. </span>Conformance</h2>
+  <!--begin-conformance-->
+
+  <h3 class=no-ref id=conventions> Document conventions</h3>
+
+  <p>Conformance requirements are expressed with a combination of descriptive
+   assertions and RFC 2119 terminology. 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 RFC
+   2119. However, for readability, these words do not appear in all uppercase
+   letters in this specification.
+
+  <p>All of the text of this specification is normative except sections
+   explicitly marked as non-normative, examples, and notes. <a
+   href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>
+
+  <p>Examples in this specification are introduced with the words “for
+   example” or are set apart from the normative text with
+   <code>class="example"</code>, like this:
+
+  <div class=example>
+   <p>This is an example of an informative example.
+  </div>
+
+  <p>Informative notes begin with the word “Note” and are set apart from
+   the normative text with <code>class="note"</code>, like this:
+
+  <p class=note>Note, this is an informative note.
+
+  <h3 class=no-ref id=conformance-classes> Conformance classes</h3>
+
+  <p>Conformance to this is defined for three conformance classes:
+
+  <dl>
+   <dt><dfn id=style-sheet title="style sheet!!as conformance class">style
+    sheet</dfn>
+
+   <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
+    style sheet</a>.
+
+   <dt><dfn id=renderer>renderer</dfn>
+
+   <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+    that interprets the semantics of a style sheet and renders documents that
+    use them.
+
+   <dt><dfn id=authoring-tool>authoring tool</dfn>
+
+   <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+    that writes a style sheet.
+  </dl>
+
+  <p>A style sheet is conformant to this specification if all of its
+   statements that use syntax defined in this module are valid according to
+   the generic CSS grammar and the individual grammars of each feature
+   defined in this module.
+
+  <p>A renderer is conformant to this specification if, in addition to
+   interpreting the style sheet as defined by the appropriate specifications,
+   it supports all the features defined by this specification by parsing them
+   correctly and rendering the document accordingly. However, the inability
+   of a UA to correctly render a document due to limitations of the device
+   does not make the UA non-conformant. (For example, a UA is not required to
+   render color on a monochrome monitor.)
+
+  <p>An authoring tool is conformant to this specification if it writes style
+   sheets that are syntactically correct according to the generic CSS grammar
+   and the individual grammars of each feature in this module, and meet all
+   other conformance requirements of style sheets as described in this
+   module.
+
+  <h3 class=no-ref id=partial> Partial implementations</h3>
+
+  <p>So that authors can exploit the forward-compatible parsing rules to
+   assign fallback values, CSS renderers <strong>must</strong> treat as
+   invalid (and <a
+   href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as
+   appropriate</a>) any at-rules, properties, property values, keywords, and
+   other syntactic constructs for which they have no usable level of support.
+   In particular, user agents <strong>must not</strong> selectively ignore
+   unsupported component values and honor supported values in a single
+   multi-value property declaration: if any value is considered invalid (as
+   unsupported values must be), CSS requires that the entire declaration be
+   ignored.
+
+  <h3 class=no-ref id=experimental> Experimental implementations</h3>
+
+  <p>To avoid clashes with future CSS features, the CSS 2.1 specification
+   reserves a <a
+   href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
+   syntax</a> for proprietary and experimental extensions to CSS.
+
+  <p>Prior to a specification reaching the Candidate Recommendation stage in
+   the W3C process, all implementations of a CSS feature are considered
+   experimental. The CSS Working Group recommends that implementations use a
+   vendor-prefixed syntax for such features, including those in W3C Working
+   Drafts. This avoids incompatibilities with future changes in the draft.
+
+  <h3 class=no-ref id=testing> Non-experimental implementations</h3>
+
+  <p>Once a specification reaches the Candidate Recommendation stage,
+   non-experimental implementations are possible, and implementors should
+   release an unprefixed implementation of any CR-level feature they can
+   demonstrate to be correctly implemented according to spec.
+
+  <p>To establish and maintain the interoperability of CSS across
+   implementations, the CSS Working Group requests that non-experimental CSS
+   renderers submit an implementation report (and, if necessary, the
+   testcases used for that implementation report) to the W3C before releasing
+   an unprefixed implementation of any CSS features. Testcases submitted to
+   W3C are subject to review and correction by the CSS Working Group.
+
+  <p>Further information on submitting testcases and implementation reports
+   can be found from on the CSS Working Group's website at <a
+   href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
+   Questions should be directed to the <a
+   href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
+   mailing list. <!--end-conformance-->
+
+  <h2 id=references><span class=secno>23. </span>References</h2>
 
   <h3 class=no-num id=normative-references>Normative references</h3>
   <!--begin-normative-->
@@ -3403,6 +3524,15 @@ <h3 class=no-num id=normative-references>Normative references</h3>
    </dd>
    <!---->
 
+   <dt id=RFC2119>[RFC2119]
+
+   <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key
+    words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet
+    RFC 2119. URL: <a
+    href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+   </dd>
+   <!---->
+
    <dt id=SVG11>[SVG11]
 
    <dd>Erik Dahlström; et al. <a
@@ -3566,6 +3696,9 @@ <h2 class=no-num id=index>Index</h2>
     href="#accumulated-3d-transformation-matrix"
     title="section 4."><strong>4.</strong></a>
 
+   <li>authoring tool, <a href="#authoring-tool"
+    title="section 22."><strong>22.</strong></a>
+
    <li>backface-visibility, <a href="#backface-visibility"
     title="section 12."><strong>12.</strong></a>
 
@@ -3624,6 +3757,9 @@ <h2 class=no-num id=index>Index</h2>
    <li>perspective-origin, <a href="#perspective-origin"
     title="section 11."><strong>11.</strong></a>
 
+   <li>renderer, <a href="#renderer"
+    title="section 22."><strong>22.</strong></a>
+
    <li>‘<code class=css>right</code>’
     <ul>
      <li>‘<a href="#perspective-origin"><code
@@ -3635,6 +3771,12 @@ <h2 class=no-num id=index>Index</h2>
       title="section 8."><strong>8.</strong></a>
     </ul>
 
+   <li>style sheet
+    <ul>
+     <li>as conformance class, <a href="#style-sheet"
+      title="section 22."><strong>22.</strong></a>
+    </ul>
+
    <li>‘<code class=css>top</code>’
     <ul>
      <li>‘<a href="#perspective-origin"><code

css3-transforms/Transforms.src.html

@@ -3240,6 +3240,8 @@ <h2 id="mathematical-description">
                 </li>
               </ul>
 
+        <h2>Conformance</h2>
+        <!--conformance-->
 
         <h2>References</h2>