[dbaron revision history] Bracket all issues. (date: 2003/07/15 21:29:47)

Author: dbaron

css3-syntax/Overview.src.html

@@ -186,8 +186,8 @@ <h2>CSS style sheet representation</h2>
 
 <p>This specification does not mandate which character encodings
 a user agent must support.
-<span class="issue">Should we require a certain minimal set, such as
-UTF-8 and UCS2?</span>
+<span class="issue">[Should we require a certain minimal set, such as
+UTF-8 and UCS2?]</span>
 </p>
 
 <p>Note that reliance on the @charset construct theoretically poses a
@@ -351,8 +351,8 @@ <h3 id="characters">Characters and case</h3>
 
 <h3 id="tokenization">Tokenization</h3>
 
-<p class="issue">This needs to be integrated with the selectors module.
-How should that be done?</p>
+<p class="issue">[This needs to be integrated with the selectors module.
+How should that be done?]</p>
 
 <p>All levels of CSS -- level 1, level 2, level 3, and any future levels
 -- use the same core syntax. This allows UAs to parse (though not
@@ -368,8 +368,8 @@ <h3 id="tokenization">Tokenization</h3>
 
 <p>The following productions are <em>parts</em> of tokens:</p>
 
-<p class="issue">We need something to allow signs on integers.  Do we need to
-go as far as css3-selectors?</p>
+<p class="issue">[We need something to allow signs on integers.  Do we need to
+go as far as css3-selectors?]</p>
 
 <table>
 <tr><td id="SUBTOK-ident">ident	<td>::=<td><code>'-'? <a href="#SUBTOK-nmstart">nmstart</a> <a href="#SUBTOK-nmchar">nmchar</a>*</code>
@@ -431,11 +431,11 @@ <h3 id="tokenization">Tokenization</h3>
 
 </p>
 
-<p class="issue">This isn't exactly right.  Since the string token can't
+<p class="issue">[This isn't exactly right.  Since the string token can't
 contain newlines that aren't escaped by backslashes, an untokenizable
 sequence can occur in the middle of a file.  Would it be better to
 change things so that unmatched quotation marks become single-character
-tokens and all character streams are tokenizable?</p>
+tokens and all character streams are tokenizable?]</p>
 
 <h3>Grammar</h3>
 
@@ -457,7 +457,7 @@ <h4>Principles of CSS error handling</h4>
 
 <p>The handling of style sheets that do not parse according to the
 forward-compatible core syntax is not defined by this specification.
-<span class="issue">Should it be?</span>
+<span class="issue">[Should it be?]</span>
 </p>
 
 <p>Certain productions within the grammar are <dfn>error handling
@@ -467,28 +467,28 @@ <h4>Principles of CSS error handling</h4>
 represented as <code>prod</code>, then the backup production is
 represented as <code>FAIL(prod)</code>.</p>
 
-<p class="issue">The grammar given in <a
+<p class="issue">[The grammar given in <a
 href="http://www.w3.org/TR/1998/REC-CSS2-19980512/grammar.html">Appendix D</a>
 of CSS2 still needs to be incorporated into this specification.  The editor
 hopes that it can be done by unifying it with the forward-compatible grammar
 into a single grammar that describes both the rules for forward-compatible
 parsing and the syntax of what is currently possible in CSS, but that may not
 be possible.  However, hopefully it will be possible to do this by
 describing the general grammar in terms of the concepts described in the
-previous paragraph.</p>
+previous paragraph.]</p>
 
 <p>Excluding the transformation of a production into its backup
-production, this grammar is LL(1).  <span class="issue">We should
+production, this grammar is LL(1).  <span class="issue">[We should
 explain briefly what this means, except that it's probably not true.
-It's probably just LALR(1).</span>
+It's probably just LALR(1).]</span>
 </p>
 
 <p>The portion of a CSS style sheet that is to be used is the largest
 initial stream of the tokens resulting from the <a
 href="#tokenization">tokenization process</a> that can be parsed
 according to the grammar presented in this chapter.  (For example, if a
-brace opening a declaration block <span class="issue">(link-ify
-this)</span> is not present, the declaration block
+brace opening a declaration block <span class="issue">[link-ify
+this]</span> is not present, the declaration block
 must be ignored since the closing brace is required to satisfy this
 grammar.)</p>
 
@@ -523,14 +523,14 @@ <h4>Style sheets</h4>
 </PRE>
 
 <div class="issue">
-The definitions of these productions should be spread below into the
+[The definitions of these productions should be spread below into the
 prose describing what they mean.  Furthermore, they should be combined
 with the Appendix D grammar from CSS2, perhaps using notation like:
 <table>
 <tr><td>ruleset</td><td>::=</td><td>...</td></tr>
 <tr><td>FAIL(ruleset)</td><td>::=</td><td>...</td></tr>
 </table>
-</div>
+]</div>
 
 <p><a name="comment">COMMENT</a> tokens do not occur
 in the grammar (to keep it readable), but any number of these tokens
@@ -829,9 +829,9 @@ <h3 id="comments" class="index-def" title="comments">Comments</h3>
 
 <h2 id="error-handling">Rules for handling parsing errors or unsupported features</h2>
 
-<p class="issue">Hopefully (assuming it can be formalized within the
+<p class="issue">[Hopefully (assuming it can be formalized within the
 rules above) this section will not need so much detail and can be folded
-into the previous section.</p>
+into the previous section.]</p>
 
 <p>In some cases, user agents must ignore part of an illegal style
 sheet. This specification defines <span class="index-def"
@@ -890,9 +890,9 @@ <h2 id="error-handling">Rules for handling parsing errors or unsupported feature
 <p>A user agent conforming to a future CSS specification may accept one or
 more of the other rules as well.</p>
 
-<p class="issue">A general comment on how to handle negative numbers
+<p class="issue">[A general comment on how to handle negative numbers
 when disallowed might be useful.  Is it handled by truncation or is it a
-parser error?</p>
+parser error?]</p>
 
 <LI><strong>Invalid at-keywords.</strong> User agents must <span
 class="index-inst" title="ignore"><a href="#ignore">ignore</a></span> an
@@ -1188,8 +1188,8 @@ <h3 id="associating-author">Author style sheets</h3>
 
 <p>This section is informative.</p>
 
-<p class="issue">Add informative references to [[HTML40]],
-[[CSSSTYLEATTR]] and xml-stylesheet [[XMLSTYLE]].</p>
+<p class="issue">[Add informative references to [[HTML40]],
+[[CSSSTYLEATTR]] and xml-stylesheet [[XMLSTYLE]].]</p>
 
 <h3 id="at-import">Style sheets including other style sheets: 
 the <code>@import</code> rule</h3>
@@ -1468,12 +1468,13 @@ <h3>Definitions</h3>
 
 <h3 id="conf-UA">User agent conformance</h3>
 
-<p class="issue">Note rules for user style sheet conformance, Author style sheet disabling,
-etc.</p>
-<p class="issue">Mention rules for handling parsing errors, especially</p>
+<p class="issue">[Note rules for user style sheet conformance, Author
+style sheet disabling, etc.]</p>
+
+<p class="issue">[Mention rules for handling parsing errors, especially.]</p>
 
-<p class="issue">Rewrite the text below (from CSS2) in light of
-modularization.</p>
+<p class="issue">[Rewrite the text below (from CSS2) in light of
+modularization.]</p>
 
 <P>This section defines <span class="index-def"
 title="conformance">conformance</span> with the CSS&nbsp;2.1
@@ -1584,7 +1585,7 @@ <h3 id="conf-AT">Authoring tool conformance</h3>
 display the application of a style sheet to a document, they are required
 to meet the <a href="#conf-UA">user agent conformance</a> rules.</p>
 
-<p class="issue">(informative reference to canonicalization proposal?)</p>
+<p class="issue">[informative reference to canonicalization proposal?]</p>
 
 
 <h2 id="property-defs">Format of property definitions in other modules</h2>
@@ -1707,10 +1708,10 @@ <h3 id="property-def-value">Value</h3>
     <EM>Value:</EM> &lt;uri&gt; || &lt;color&gt;<BR>
 </BLOCKQUOTE>
 
-<p class="issue">We need a more formal grammar for parsing of
-properties.  Refer to section on keywords (they can't be quoted).</p>
+<p class="issue">[We need a more formal grammar for parsing of
+properties.  Refer to section on keywords (they can't be quoted).]</p>
 
-<p class="issue">Need to cite values & units module here.</p>
+<p class="issue">[Need to cite values & units module here.]</p>
 
 <h4><code>initial</code> and <code>inherit</code> values</h4>
 
@@ -1756,9 +1757,9 @@ <h3 id="property-def-computed">Computed value</h3>
 [[CSS3CASCADE]].  (It is needed both for inheritance and for the
 definitions of some DOM properties.)</p>
 
-<p class="issue">What is the computed value for elements to which the
+<p class="issue">[What is the computed value for elements to which the
 property does not apply?  Do some existing inherited properties rely on
-inheritance through elements to which the property doesn't apply?</p>
+inheritance through elements to which the property doesn't apply?]</p>
 
 <h3 id="property-def-percent">Percentage values</h3>
 
@@ -1768,8 +1769,8 @@ <h3 id="property-def-percent">Percentage values</h3>
 
 <h3 id="media-groups">Media groups</h3>
 
-<p class="issue">Some of this needs to be relaxed to deal with
-profiles.</p>
+<p class="issue">[Some of this needs to be relaxed to deal with
+profiles.]</p>
 
 <p>This part indicates the media groups for which the property must be
 implemented by a conforming user agent.
@@ -1907,9 +1908,9 @@ <h3>Shorthand properties</h3>
 
 <h2>Appendix: Second grammar</h2>
 
-<p class="issue">This grammar was the Appendix D grammar of CSS2,
+<p class="issue">[This grammar was the Appendix D grammar of CSS2,
 augmented by the additions from the @namespace draft.  It needs to be
-incorporated into the above normative text in some way.</p>
+incorporated into the above normative text in some way.]</p>
 
 <p>The grammar below defines the syntax of CSS2. It is in some sense,
 however, a superset of CSS2 as this specification imposes additional
@@ -1935,10 +1936,10 @@ <h3>Grammar</h3>
 consumption and some shorthand notation beyond Yacc (see [[YACC]]) is
 used:</p>
 
-<p class="issue">It's probably not LL(1), but rather just LALR(1).</p>
+<p class="issue">[It's probably not LL(1), but rather just LALR(1).]</p>
 
-<p class="issue">This needs a lot more revisions to reflect all the
-additions in CSS3.</p>
+<p class="issue">[This needs a lot more revisions to reflect all the
+additions in CSS3.]</p>
 
 <ul>
 <li><strong>*</strong>: 0 or more
@@ -2168,10 +2169,10 @@ <h2 class="no-num">Changes from CSS2</h2>
   grammar should be handled (by saying that parsing uses the parseable
   initial sequence of tokens)</li>
 
-  <li><span class="issue">(to be done)</span> described handling of unmatched quotation marks (by saying that
+  <li><span class="issue">[to be done]</span> described handling of unmatched quotation marks (by saying that
   tokenization uses the tokenizable initial sequence of characters)</li>
 
-  <li><span class="issue">(to be done)</span> formalized the error handling rules by combining the
+  <li><span class="issue">[to be done]</span> formalized the error handling rules by combining the
   forward-compatible grammar in chapter 4 with the CSS2 grammar in
   Appendix D.</li>