W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2004

Comments on 2nd WD (part 2)

From: Glen Mazza <grm7793@yahoo.com>
Date: Tue, 21 Dec 2004 22:25:12 -0500
Message-ID: <41C8E918.60802@yahoo.com>
To: XSL Editors <xsl-editors@w3.org>

Editors:

More comments on Ch. 1 of the 2nd WD:

11.)  Section 1.2.1 -- 4th paragraph, just add "the" where indicated (we 
are referring to specific extensions in this section.):

There are several ways in which -->the<-- extensions were made.


12.)  Section 1.2.1 -- 5th paragraph, replace -->, are<-- to -->were<-- 
in this sentence to keep the tense consistent with the examples in the 
previous and succeeding paragraph:

"In other cases, common properties that are expressed in CSS2 as one 
property with multiple simultaneous values-->, are<-- split into several 
new properties to provide independent control over independent aspects 
of the property."


13.)  Section 1.2.1 -- 7th paragraph, change:

"Some of the formatting objects and many of the properties in XSL come 
from the CSS2 specification, -->ensuring<-- compatibility between the two."

to

"Some of the formatting objects and many of the properties in XSL come 
from the CSS2 specification, -->creating considerable<-- compatibility 
between the two."

(Statement is more accurate.)


14.)  Section 1.2.1 -- 8th paragraph, change:

"There are four classes of XSL properties that can be identified as:"

to

"XSL properties can be classified by their derivation from CSS2 as follows:"

(More semantically accurate, I think.)


15.)  Section 1.2.2. -- 1st paragraph, change:

"As mentioned above, XSL uses XSLT and XPath for tree construction and 
pattern selection, thus providing a high degree of control over 
-->how<-- portions of the source content -->are<-- presented, and what 
properties -->are<-- associated with those -->content<-- portions, even 
where mixed namespaces are involved."

to

"As mentioned above, XSL uses XSLT and XPath for tree construction and 
pattern selection, thus providing a high degree of control over 
-->which<-- portions of the source content -->are to be<-- presented, 
and what properties -->are to be<-- associated with those --><-- 
portions, even where mixed namespaces are involved."

(XSLT and XPath emphasize "which" data will be presented more than the 
"how" they will be presented, although admittedly XSLT is what generates 
the FO's.  Another problem with using "how" though is that the resulting 
sentence seems to imply that there are portions of the source content 
whose presentation can't be controlled by XSLT and XPath.)


16.)  Section 1.2.3 -- 1st paragraph, add -->"to be"<-- where indicated:

"There is a set of formatting objects in XSL to describe both the layout 
structure of a page or "frame" (how big is the body; are there multiple 
columns; are there headers, footers, or sidebars; how big are these) and 
the rules by which the XML source content is -->to be<-- placed into 
these "containers"."


17.)  Section 1.2.3 -- 2nd paragraph:  Replace -->page sequences<-- with 
-->page-sequence-masters<--, and remove
the sentence following this one from this paragraph (in brackets below):

These simple-page-masters can be used in -->page sequences<-- that 
specify in which order the various simple-page-masters shall be used. 
[The page sequence also specifies how styled content is to fill those 
pages.]

(Recommending removal of the second sentence here because we are no 
longer talking about page sequences in this paragraph, and so this 
sentence would be out of place here.)


18.)  Section 1.2.5, 2nd paragraph -- Change:

"In addition, the inline-progression-direction for a sequence of 
characters may be implicitly determined using bidirectional character 
types -->for those characters<-- from the Unicode Character Database 
[UNICODE Character Database] for those characters and the Unicode 
bidirectional (BIDI) algorithm [UNICODE UAX #9]."

to

"In addition -->to the "writing-mode" property<--, the 
inline-progression-direction for a sequence of characters may be 
implicitly determined -->by<-- using bidirectional character types 
--><-- from the Unicode Character Database [UNICODE Character Database] 
for those characters and the Unicode bidirectional (BIDI) algorithm 
[UNICODE UAX #9]."

*and* recommend moving this sentence to a new one-sentence paragraph, 
immediately below the current paragraph that it is in.


19.)  Section 1.2.5, 3rd paragraph -- Change:

"Besides the directions that are explicit in the name of the value of 
the "writing-mode" property, the writing-mode determines other 
directions needed by the formatter, such as the shift-direction (used 
for subscripts and superscripts), etc."

to

"--><--The writing-mode -->also<-- determines other directions needed by 
the formatter, such as the shift-direction (used for subscripts and 
superscripts), etc."

*and* recommend merging this sentence to the end of the second paragraph 
above, right after the "..which determines the direction in which blocks 
(and lines) are placed one after another." sentence.  (Assuming #18 is 
agreed to, and the sentence there is moved to its own paragraph.)


20.)  Section 1.2.6, 1st paragraph -- Change second -->built-in<-- with 
"inherent"  (avoids word repetition in the sentence.)

Because XML, unlike HTML, has no built-in semantics, there is no 
-->built-in<-- notion of a hypertext link.


Thanks,
Glen Mazza
Apache FOP Team
Received on Wednesday, 22 December 2004 03:20:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:48 UTC