W3C home > Mailing lists > Public > www-style@w3.org > February 2002

Comments for Selectors 20011113

From: Susan Lesch <lesch@w3.org>
Date: Sun, 3 Feb 2002 02:50:48 -0800
Message-Id: <p05100304b882c3fa497d@[192.168.123.158]>
To: www-style@w3.org
Belated congratulations on your Selectors Candidate Recommendation [1].
It is fun to read! Below, minor editorial comments use the convention
substitute this for that: s/that/this/

Please consider renaming this "CSS Selectors" or "CSS3 Selectors." That
would make the subject clear in W3C communication and beyond.

In the embedded style sheet, s/.code/code/

Settle on one way to represent -th. Maybe <em>n</em>th globally.

In the status section, s/last call review/Last Call review/

In 1, "the" Clamart meeting can only mean something if you were
there. You could say "its meeting in Clamart, France" or skip it.

In 1, "For instance, behaviors or tree transformations." is an
incomplete sentence. You could say "...syntax, for instance...."

In 2:
   E:nth-last-child(n)	an E element, the n-th child of its parent,
   counting from the last one
could be more specific:
   E:nth-last-child(n)	an E element, the n-th child of its parent,
   counting from the last child
also:
   E:nth-last-of-type(n)	an E element, the n-th sibling of its type,
   counting from the last one
could be:
   E:nth-last-of-type(n)	an E element, the n-th sibling of its type,
   counting from the last sibling

In 6.2.1, "is defined in the General Syntax module" needs a link or an
explanation if that document is unavailable publicly. Same for
"Generated Content/Markers CSS3 Module" in 7.4, and "described in
another CSS3 Module 'Cascade and Inheritance'" in 9.

Somewhere before 6.3.1 examples, explain when values need to be quoted.

In 6.3.2, end the three sentences beginning with "The following..."
with periods or colons so they match.

In 6.3.3:
     Namespaces in the XML recommendation
two changes:
     Namespaces in XML Recommendation

In 6.4, for the first occurrence, spell out "UA (user agent)."

In 6.4, I imagine you will remember to change the SVG link to
http://www.w3.org/TR/2001/REC-SVG-20010904/styling.html#ClassAttribute .
Also you could address XHTML in this section, maybe as an example.

In 6.6.3, (arguably) "human language" could be "natural language."

In 6.6.4, mark the HTML4 link "[HTML4]" for people who print or
otherwise have no access to the link.

In 6.4, for the first occurrence, spell out "DOM (Document Object
Model)" and give a reference.

"For example, this allows in CSS to alternate the position of floated
images:" could read "For example, this CSS alternates the position of
floated images:".

In 6.6.5, s/colours/colors/

In 6.6.5, "from a DOM point of view" might need a reference.

In 6.6.7, one occurrence of ":not" in the Note can be marked up <code>.

For 7.2, _The Economist_ capitalizes its "The."

In 7.3, the first paragraph needs an ending period.

In 8, could you describe the relationship between CSS1 and CSS2
contextual selectors and CSS3 combinators?

In 9, s/a HTML style attribute/an HTML style attribute/

In 10.1, maybe explain what LL(1) and LL(2) mean, and link like [YACC]
if there is a good reference.

In 11, s/web/Web/ (twice)

In 12, s/Non normative/Non-normative/

In 13, you have a case for using "must" in the RFC 2119 sense. Make
that RFC a reference, and preface this section with:
     The key word "MUST" is to be interpreted as described in [RFC2119].

In 13, s/non interactive/non-interactive/

In 13, this sentence has a lot of negatives:
   The inability of a user agent to implement part of this
   specification due to the limitations of a particular device (e.g.,
   non interactive user agents will probably not implement dynamic
   pseudo-classes because they make no sense without interactivity)
   does not imply non-conformance.
It could read something like:
   Conformance is independent of the ability or inability of a user
   agent to implement part of this specification due to the
   capabilities of a particular device. (E.g., only interactive user
   agents will probably implement dynamic pseudo-classes because they
   only make sense with interactivity.)

In 15, s/the W3C Working Group on Cascading Style Sheets and
Formatting Properties/the W3C Working Group on Cascading Style Sheets/
(I think.)

In 15, Duerst comes after Diaz, and Tecot comes after Sorenson.

In 16, make the reference titles the link; the URI should be plain
text. (See the last paragraph in section 9.5 of
http://www.w3.org/2001/06/manual/#References .)

In 16, s/Ragget/Raggett/

In 16, Ion and Minor are MathML editors.


[1] http://www.w3.org/TR/2001/CR-css3-selectors-20011113/

Best wishes for your project,
-- 
Susan Lesch           http://www.w3.org/People/Lesch/
mailto:lesch@w3.org               tel:+1.858.483.4819
World Wide Web Consortium (W3C)    http://www.w3.org/
Received on Sunday, 3 February 2002 05:50:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:13 GMT