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

1.1 WD Comments on region-name and flow-name properties

From: Glen Mazza <grm7793@yahoo.com>
Date: Sun, 29 Aug 2004 18:49:22 -0400
Message-ID: <41325D72.6010604@yahoo.com>
To: XSL Editors <xsl-editors@w3.org>


A few comments on the region-name and flow-name properties in the 1.1 WD:

1.)  In Section 7.25.17, "region-name" property [1]:

A search on the 1.1 WD is showing that "xsl-before-float-separator" and 
"xsl-footnote-separator" are defined only for the flow-name property, 
not the region-name as listed here.  Recommend to remove these two 
values and their definitions from region-name, and place them in the 
flow-name property description instead.

2.)  (minor edit) In Section 7.25.17, "region-name" property:

For the definitions of the xsl-region-xxxx values, switch from "...for 
use as default name..." to "...for use as the default name...".

3.)  In Section 7.25.5, "flow-name" property [2]:

a) For the sentence: "If the name is empty or if a name-conflict is 
encountered, an error shall be reported."

It may be good to also define here (if it hasn't been defined explicitly 
elsewhere--I didn't see it) what happens if no region on the simple page 
master has the flow-name specified.

I think, in this case, that would *not* be an error, but that the flow's 
content would just not be generated.  I believe this is the case because 
the region-name definition states that we can define different names for 
the same region on the odd and even pages of 
fo-repeatable-page-master-alternatives (e.g., to have different static 
headers depending on whether we're on an odd or even page.)

b) The sentence "Defines the name of the flow" seems too vague, perhaps 
it should be switched to something like "Designates the region that this 
flow's content should be assigned to."

4.)  In Section, "Flows and Flow Mapping" [3], make sure to 
update the paragraph below because we now do have an fo:flow-map 
formatting object in 1.1:

"In version 1.0 of this Recommendation, the flow-map is implicit. [...]  
In future versions of XSL, the flow-map is expected to become an 
explicit formatting object."

Glen Mazza
Apache FOP Team

[1] http://www.w3.org/TR/2003/WD-xsl11-20031217/#region-name
[2] http://www.w3.org/TR/2003/WD-xsl11-20031217/#flow-name
[1] http://www.w3.org/TR/2003/WD-xsl11-20031217/#fafm
Received on Sunday, 29 August 2004 22:44:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:24 UTC