comments on WD-css3-values-20010713


2. Introduction:

  6. special cases (e.g. "color: #F00" and "font-size: Helvetica") 

  Must be "font-family: Helvetica" and should be
  "font-family: Helvetica, sans-serif"

3.1. Keywords:

  ... Keywords are never quoted.

  I suggest: Keywords must not be quoted.

3.3.1. Lengths:

  When specified for the root of the document tree (e.g., "HTML" in
  HTML), 'em' and 'ex' refer to the property's initial value.

We recently discussed this on Is this an error or why
did the CSS WG decide to break with the common XML terminology? I
strongly suggest: "... for the root element of the document ..."

  Absolute lengthunits are only useful when the physical properties of
  the output medium are known. The absolute units are: 

Missing white-space.

3.4. Strings:

  Strings can either be written with double quotes or with single
  quotes. Double quotes cannot occur inside double quotes, unless
  escaped (as '\"' or as '\22'). Analogously for single quotes
  ("\'" or "\27").

  I suggest adding a comment that escapes refer to ISO/IEC 10646:2000
  code points

  A string cannot directly contain a newline. To include a newline in a
  string, use the escape "\A" (hexadecimal A is the line feed character
  in Unicode, but represents the generic notion of "newline" in CSS).
  See the 'content' property for an example. 

  I suggest adding "... line feed character in Unicode (U+000A), ..."

3.5.2. URIs:

  URLs(Uniform Resource Locators, see [RFC1738] and [RFC1808]) provide
  the address of a resource on the Web. An expected new way of
  identifying resources is called URN(Uniform Resource Name). Together
  they are called URIs(Uniform Resource Identifiers, see [URI]). This
  specification uses the term URI. 

  There are missing white-spaces. I don't like the discussion here, it
should be just URI and a reference to RFC 2396. In order to be
consistent with XML, RFC 2732 should be referenced, too. I suggest
adding a note on escaping URIs with invalid charcters as in HTML 4.01
section B.2.1 and XML 1.0 section 4.2.2.

3.6.1. Font families:

  [Font families are like strings, except one may drop the quotes around

  It should say that generic font family names aren't strings but
keywords and must not be quoted.

3.6.2. Colors:

  This section is completly misplaced, there is a CSS Level 3 Color
Module that defines everything in this section. E.g.

  The list of keyword color names is: aqua, black, blue, fuchsia, gray,
  green, lime, maroon, navy, olive, purple, red, silver, teal, white,
  and yellow.

  This is according to the current draft of the color module wrong.

As for all CSS Level 3 modules, I'd like to see XHTML be used,
especially in the Text, i.e.

  h1 { font-family: serif }

instead of

  H1 { font-family: serif }

I consider this part of W3Cs role "... to promote its widespread

best regards,
Björn Höhrmann { }
am Badedeich 7 } Telefon: +49(0)4667/981028 {
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 }

Received on Saturday, 14 July 2001 03:54:57 UTC