Mercurial > drafts / changeset

     1.1 --- a/matrix/ChangeLog	Sun Mar 10 19:35:27 2013 -0700
     1.2 +++ b/matrix/ChangeLog	Sun Mar 10 21:31:31 2013 -0700
     1.3 @@ -1,3 +1,6 @@
     1.4 +2013-03-11  Dirk Schulze  <dschulze@adobe.com>
     1.5 +	Add Conformance section.
     1.6 +
     1.7  2013-03-10  Dirk Schulze  <dschulze@adobe.com>
     1.8  	Remove issues for 3D arguments on rotateFromVectorBy and rotateFromVector.
     1.9  

     2.1 --- a/matrix/index.html	Sun Mar 10 19:35:27 2013 -0700
     2.2 +++ b/matrix/index.html	Sun Mar 10 21:31:31 2013 -0700
     2.3 @@ -933,6 +933,137 @@
     2.4        <h2>Interface summary</h2>
     2.5      </section>
     2.6  
     2.7 +    <section class='appedix'>
     2.8 +      <h2>Conformance</h2>
     2.9 +
    2.10 +      <section>
    2.11 +        <h3 id="conventions">
    2.12 +        Document conventions</h3>
    2.13 +
    2.14 +        <p>Conformance requirements are expressed with a combination of
    2.15 +        descriptive assertions and RFC 2119 terminology. The key words “MUST”,
    2.16 +        “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
    2.17 +        “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
    2.18 +        document are to be interpreted as described in RFC 2119.
    2.19 +        However, for readability, these words do not appear in all uppercase
    2.20 +        letters in this specification.
    2.21 +
    2.22 +        <p>All of the text of this specification is normative except sections
    2.23 +        explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
    2.24 +
    2.25 +        <p>Examples in this specification are introduced with the words “for example”
    2.26 +        or are set apart from the normative text with <code>class="example"</code>,
    2.27 +        like this:
    2.28 +
    2.29 +        <div class="example">
    2.30 +          <p>This is an example of an informative example.</p>
    2.31 +        </div>
    2.32 +
    2.33 +        <p>Informative notes begin with the word “Note” and are set apart from the
    2.34 +        normative text with <code>class="note"</code>, like this:
    2.35 +
    2.36 +        <p class="note">Note, this is an informative note.</p>
    2.37 +      </section>
    2.38 +
    2.39 +      <section>
    2.40 +        <h3 id="conformance-classes">
    2.41 +        Conformance classes</h3>
    2.42 +
    2.43 +        <p>Conformance to CSS Masking
    2.44 +        is defined for three conformance classes:
    2.45 +        <dl>
    2.46 +          <dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
    2.47 +            <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
    2.48 +            style sheet</a>.
    2.49 +          <dt><dfn>renderer</dfn></dt>
    2.50 +            <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
    2.51 +            that interprets the semantics of a style sheet and renders
    2.52 +            documents that use them.
    2.53 +          <dt><dfn id="authoring-tool">authoring tool</dfn></dt>
    2.54 +            <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
    2.55 +            that writes a style sheet.
    2.56 +        </dl>
    2.57 +
    2.58 +        <p>A style sheet is conformant to CSS Masking
    2.59 +        if all of its statements that use syntax defined in this module are valid
    2.60 +        according to the generic CSS grammar and the individual grammars of each
    2.61 +        feature defined in this module.
    2.62 +
    2.63 +        <p>A renderer is conformant to CSS Masking
    2.64 +        if, in addition to interpreting the style sheet as defined by the
    2.65 +        appropriate specifications, it supports all the features defined
    2.66 +        by CSS Masking by parsing them correctly
    2.67 +        and rendering the document accordingly. However, the inability of a
    2.68 +        UA to correctly render a document due to limitations of the device
    2.69 +        does not make the UA non-conformant. (For example, a UA is not
    2.70 +        required to render color on a monochrome monitor.)
    2.71 +
    2.72 +        <p>An authoring tool is conformant to CSS Masking
    2.73 +        if it writes style sheets that are syntactically correct according to the
    2.74 +        generic CSS grammar and the individual grammars of each feature in
    2.75 +        this module, and meet all other conformance requirements of style sheets
    2.76 +        as described in this module.
    2.77 +      </section>
    2.78 +
    2.79 +      <section>
    2.80 +        <h3 id="partial">
    2.81 +        Partial implementations</h3>
    2.82 +
    2.83 +        <p>So that authors can exploit the forward-compatible parsing rules to
    2.84 +        assign fallback values, CSS renderers <strong>must</strong>
    2.85 +        treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
    2.86 +        as appropriate</a>) any at-rules, properties, property values, keywords,
    2.87 +        and other syntactic constructs for which they have no usable level of
    2.88 +        support. In particular, user agents <strong>must not</strong> selectively
    2.89 +        ignore unsupported component values and honor supported values in a single
    2.90 +        multi-value property declaration: if any value is considered invalid
    2.91 +        (as unsupported values must be), CSS requires that the entire declaration
    2.92 +        be ignored.</p>
    2.93 +      </section>
    2.94 +
    2.95 +      <section>
    2.96 +        <h3 id="experimental">
    2.97 +        Experimental implementations</h3>
    2.98 +
    2.99 +        <p>To avoid clashes with future CSS features, the CSS2.1 specification
   2.100 +        reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
   2.101 +        syntax</a> for proprietary and experimental extensions to CSS.
   2.102 +
   2.103 +        <p>Prior to a specification reaching the Candidate Recommendation stage
   2.104 +        in the W3C process, all implementations of a CSS feature are considered
   2.105 +        experimental. The CSS Working Group recommends that implementations
   2.106 +        use a vendor-prefixed syntax for such features, including those in
   2.107 +        W3C Working Drafts. This avoids incompatibilities with future changes
   2.108 +        in the draft.
   2.109 +        </p>
   2.110 +      </section>
   2.111 +
   2.112 +      <section>
   2.113 +        <h3 id="testing">
   2.114 +        Non-experimental implementations</h3>
   2.115 +
   2.116 +        <p>Once a specification reaches the Candidate Recommendation stage,
   2.117 +        non-experimental implementations are possible, and implementors should
   2.118 +        release an unprefixed implementation of any CR-level feature they
   2.119 +        can demonstrate to be correctly implemented according to spec.
   2.120 +
   2.121 +        <p>To establish and maintain the interoperability of CSS across
   2.122 +        implementations, the CSS Working Group requests that non-experimental
   2.123 +        CSS renderers submit an implementation report (and, if necessary, the
   2.124 +        testcases used for that implementation report) to the W3C before
   2.125 +        releasing an unprefixed implementation of any CSS features. Testcases
   2.126 +        submitted to W3C are subject to review and correction by the CSS
   2.127 +        Working Group.
   2.128 +
   2.129 +        <p>Further information on submitting testcases and implementation reports
   2.130 +        can be found from on the CSS Working Group's website at
   2.131 +        <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
   2.132 +        Questions should be directed to the
   2.133 +        <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
   2.134 +        mailing list.
   2.135 +      </section>
   2.136 +    </section>
   2.137 +
   2.138      <section class='appendix'>
   2.139        <h2>Acknowledgments</h2>
   2.140        <p>