Wed, 09 Dec 2009 22:38:19 +0000
Add conformance section, rename tokens in grammar to be mroe clear
css-style-attr/Overview.html | file | annotate | diff | comparison | revisions | |
css-style-attr/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css-style-attr/Overview.html Wed Dec 09 20:18:06 2009 +0000 1.2 +++ b/css-style-attr/Overview.html Wed Dec 09 22:38:19 2009 +0000 1.3 @@ -130,11 +130,15 @@ 1.4 1.5 <li><a href="#grammar"><span class=secno>3. </span>Grammar</a> 1.6 1.7 - <li><a href="#cascading"><span class=secno>4. </span>Cascading order</a> 1.8 + <li><a href="#cascading"><span class=secno>4. </span>Cascading</a> 1.9 1.10 - <li><a href="#ack"><span class=secno>5. </span>Acknowledgments</a> 1.11 + <li><a href="#interpret"><span class=secno>5. </span>Interpretation</a> 1.12 1.13 - <li><a href="#references"><span class=secno>6. </span>References </a> 1.14 + <li><a href="#conformance"><span class=secno>6. </span>Conformance</a> 1.15 + 1.16 + <li><a href="#ack"><span class=secno>7. </span>Acknowledgments</a> 1.17 + 1.18 + <li><a href="#references"><span class=secno>8. </span>References </a> 1.19 <ul class=toc> 1.20 <li class=no-num><a href="#normative-references">Normative 1.21 references</a> 1.22 @@ -180,10 +184,10 @@ 1.23 1.24 <pre> 1.25 inline-stylesheet 1.26 - : S* declaration-block 1.27 + : S* declaration-list 1.28 ; 1.29 1.30 -declaration-block 1.31 +declaration-list 1.32 : declaration [ ';' S* declaration ]* 1.33 ; 1.34 </pre> 1.35 @@ -193,7 +197,7 @@ 1.36 rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> for the definition of the 1.37 symbols not defined here. 1.38 1.39 - <h2 id=cascading><span class=secno>4. </span>Cascading order</h2> 1.40 + <h2 id=cascading><span class=secno>4. </span>Cascading</h2> 1.41 1.42 <p>The declarations in a style attribute apply to the element to which the 1.43 attribute belongs. CSS2.1 <a 1.44 @@ -201,12 +205,44 @@ 1.45 "style" attributes are cascaded together. <a href="#CSS21" 1.46 rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> 1.47 1.48 - <h2 id=ack><span class=secno>5. </span>Acknowledgments</h2> 1.49 + <h2 id=interpret><span class=secno>5. </span>Interpretation</h2> 1.50 + 1.51 + <p>Aside from the differences in cascading, the declarations in a style 1.52 + attribute must be interpreted exactly as if they were given in a style 1.53 + rule that selected the associated element in a CSS style sheet associated 1.54 + with the document. 1.55 + 1.56 + <h2 id=conformance><span class=secno>6. </span>Conformance</h2> 1.57 + 1.58 + <p>The conformance requirements are expressed with a combination of 1.59 + descriptive assertions and RFC 2119 terminology. The key words "MUST", 1.60 + "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", 1.61 + "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this 1.62 + document are to be interpreted as described in RFC 2119. However, for 1.63 + readability, these words do not appear in all uppercase letters in this 1.64 + specification. All of the text of this specification is normative except 1.65 + sections explicitly marked as non-normative, examples, and notes. <a 1.66 + href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a> 1.67 + 1.68 + <p>Examples in this specification are introduced with the words "for 1.69 + example" or are set apart from the normative text with 1.70 + <code>class="example"</code>, like this: 1.71 + 1.72 + <div class=example> 1.73 + <p>This is an example of an informative example.</p> 1.74 + </div> 1.75 + 1.76 + <p>Informative notes begin with the word "Note" and are set apart from the 1.77 + normative text with <code>class="note"</code>, like this: 1.78 + 1.79 + <p class=note>Note, this is an informative note. 1.80 + 1.81 + <h2 id=ack><span class=secno>7. </span>Acknowledgments</h2> 1.82 1.83 <p>Thanks to feedback from Daniel Glazman, Ian Hickson, Eric A. Meyer, 1.84 Björn Höhrmann. 1.85 1.86 - <h2 id=references><span class=secno>6. </span>References</h2> 1.87 + <h2 id=references><span class=secno>8. </span>References</h2> 1.88 1.89 <h3 class=no-num id=normative-references>Normative references</h3> 1.90 <!--begin-normative--> 1.91 @@ -225,6 +261,15 @@ 1.92 href="http://www.w3.org/TR/2009/CR-CSS2-20090908">http://www.w3.org/TR/2009/CR-CSS2-20090908</a> 1.93 </dd> 1.94 <!----> 1.95 + 1.96 + <dt id=RFC2119>[RFC2119] 1.97 + 1.98 + <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key 1.99 + words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet 1.100 + RFC 2119. URL: <a 1.101 + href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 1.102 + </dd> 1.103 + <!----> 1.104 </dl> 1.105 <!--end-normative--> 1.106
2.1 --- a/css-style-attr/Overview.src.html Wed Dec 09 20:18:06 2009 +0000 2.2 +++ b/css-style-attr/Overview.src.html Wed Dec 09 22:38:19 2009 +0000 2.3 @@ -82,10 +82,10 @@ 2.4 2.5 <pre> 2.6 inline-stylesheet 2.7 - : S* declaration-block 2.8 + : S* declaration-list 2.9 ; 2.10 2.11 -declaration-block 2.12 +declaration-list 2.13 : declaration [ ';' S* declaration ]* 2.14 ; 2.15 </pre> 2.16 @@ -94,12 +94,44 @@ 2.17 of the CSS2.1 specification</a> [[!CSS21]] for the definition of the symbols 2.18 not defined here. 2.19 2.20 -<h2 id="cascading">Cascading order</h2> 2.21 +<h2 id="cascading">Cascading</h2> 2.22 2.23 <p>The declarations in a style attribute apply to the element to which 2.24 the attribute belongs. CSS2.1 <a href="/TR/CSS21/cascade.html#specificity">defines</a> 2.25 how style sheets and "style" attributes are cascaded together. [[!CSS21]] 2.26 2.27 +<h2 id="interpret">Interpretation</h2> 2.28 + 2.29 +<p>Aside from the differences in cascading, the declarations in a style 2.30 +attribute must be interpreted exactly as if they were given in a style 2.31 +rule that selected the associated element in a CSS style sheet associated 2.32 +with the document. 2.33 + 2.34 +<h2 id="conformance">Conformance</h2> 2.35 + 2.36 +<p>The conformance requirements are expressed with a combination of 2.37 + descriptive assertions and RFC 2119 terminology. The key words "MUST", 2.38 + "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", 2.39 + "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this 2.40 + document are to be interpreted as described in RFC 2119. 2.41 + However, for readability, these words do not appear in all uppercase 2.42 + letters in this specification. All of the text of this specification is 2.43 + normative except sections explicitly marked as non-normative, examples, 2.44 + and notes. [[!RFC2119]]</p> 2.45 + 2.46 +<p>Examples in this specification are introduced with the words "for example" 2.47 + or are set apart from the normative text with <code>class="example"</code>, 2.48 + like this: 2.49 + 2.50 +<div class="example"> 2.51 + <p>This is an example of an informative example.</p> 2.52 +</div> 2.53 + 2.54 +<p>Informative notes begin with the word "Note" and are set apart from the 2.55 + normative text with <code>class="note"</code>, like this: 2.56 + 2.57 +<p class="note">Note, this is an informative note.</p> 2.58 + 2.59 <h2 id="ack">Acknowledgments</h2> 2.60 2.61 <p>Thanks to feedback from Daniel Glazman, Ian Hickson, Eric A. Meyer,