W3C home > Mailing lists > Public > xsl-editors@w3.org > July to September 2001

Comments for PR-xsl-20010828

From: Susan Lesch <lesch@w3.org>
Date: Tue, 18 Sep 2001 00:13:38 -0700
Message-Id: <p05100308b7cca32c69e2@[192.168.123.102]>
To: xsl-editor@w3.org
These are mainly minor editorial comments for your XSL Proposed
Recommendation [1] to use as you see fit.

3000+ occurrences of 'class=""' in the markup could be cut.

Globally, "User Agent" -> user agent

Globally and in particular in 7.15.7 "linefeed-treatment", make line feed
two words; (see http://www.unicode.org/charts/PDF/U0000.pdf). Maybe this
property should be named line-feed-treatment. Also, in 7.15.8,
ignore-if-before-linefeed -> ignore-if-before-line-feed, etc.

In the introduction to slice 7, you could give an explanation for the
use of border styles (something like this):
   Properties derived from CSS2 properties have thin black borders,
   and properties copied from CSS2 have wider black borders.

Below, a section number is followed by a quote and then a suggestion.

Status
W3C membership
W3C Membership

1.
The Introduction contains a 71-word sentence. It could break at the
semicolon.

2.1
   Re: "The Tree Construction is described in "XSL Transformations"
   [XSLT]."
"Tree Construction" doesn't appear there. Maybe you want lowercase
"construction."

   Re: "The provisions in "XSL Transformations" form an integral part
   of this Recommendation and are considered normative."
Again, "provisions" doesn't appear there. Maybe you want to say, "the
entire <cite>XSL Transformations (XSLT) Version 1.0</cite> [XSLT]
Recommendation is normative for XSL 1.0" (or something similar).

4.1
hoow
how

4.3.1 has a 68-word sentence. Does this work in its place?
  "Otherwise, follow these rules when there are two or more
   space-specifiers all of the same highest precedence and the same
   (largest) optimum: The resolved space-specifier of the last
   space-specifier in the sequence is derived from these spaces by
   taking their common optimum value as its optimum. The greatest of
   their minimum values is its minimum. The least of their maximum
   values is its  maximum. All other space-specifiers are suppressed."

6.4.13
If the fo:flow flow is assigned
does this mean "If the fo:flow is assigned"? I'm not sure.

6.5.1
style sheet
stylesheet

Why does 6.5.1.1.1 follow 6.5.1.1 when there is no 6.5.1.1.2? I'd omit
6.5.1.1.1 and make that whole section 6.5.1.1 (as you do in 6.11.1.1).

6.5.3
Unicode bidi algorithm
Unicode BIDI algorithm

6.6.2
Unicode-bidi algorithm
Unicode BIDI algorithm

(I think most of those were fixed since CR, thank you.)

6.6.3
Unicode Tag Characters
Unicode tag characters
(see http://www.unicode.org/unicode/reports/tr27/#tag)

The four URIs in 7.4.1 could be links to References.

In slice 7, I'd make em lowercase rather than EM. This will match "em" in
http://www.w3.org/TR/2001/PR-xsl-20010828/slice5.html#relative.lengths

7.16.7
u+3000
U+3000

7.17.3
user-agent
user agent

7.27
bi-directional characters types
bi-directional character types

In Appendix D, make CSS2 a normative reference. Most of slice 7 is
copied from it. Unicode Technical Report #20 is used normatively in the
discussion of tag characters and could also be normative.


[1] http://www.w3.org/TR/2001/PR-xsl-20010828/

Best wishes for your project,
-- 
Susan Lesch - mailto:lesch@w3.org  tel:+1.858.483.4819
World Wide Web Consortium (W3C) - http://www.w3.org
Received on Tuesday, 18 September 2001 03:13:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:52 GMT