- From: Paul Grosso <pgrosso@arbortext.com>
- Date: Fri, 16 Jan 2004 10:11:10 -0600
- To: "Peter B. West" <pbwest@powerup.com.au>
- Cc: "Mazza, Glen R., ,CPMS" <glen.mazza@cpms.osd.mil>, "'xsl-editors@w3.org'" <xsl-editors@w3.org>
At 08:56 2004 01 16 +1000, Peter B. West wrote: >Paul Grosso wrote: >>At 19:36 2004 01 14 -0500, Mazza, Glen R., ,CPMS wrote: >> >>>Hello, I'm Glen Mazza of Electronic Data Systems and of the XML Apache FOP >>>Project. >> >>Thanks for your input. The XSL FO subgroup will be considering all >>comments in the formulation of our next draft. >>I've got some comments just from myself (not the group) embedded below. >... >>There is nothing non-conformant about an XSL FO tree that >>has any property on any FO, but if a non-inheritable property >>appears on an FO to which it doesn't apply, it will have no >>effect--since "applying (to an FO)" is equivalent to "having an effect (for that FO)". The reason it makes sense to put >>an inheritable property on an FO to which it doesn't apply >>is that such a property may be applicable to a descendant >>FO which will inherit the value. > >Paul, > >What about from-parent() & from-nearest-specified-value() ? I thought of this before I gave my previous answer, but I was concentrating on "applying", and these functions don't change "applying to", so I think my answer stands. But you are effectively asking the following question: If one has a non-inheritable property on an FO to which that property does not apply, and a descendant FO to which that property does apply references that property via a from-parent() or from-nearest-specified-value() function call, what value is returned by that function call? I will pass this question on to the group. The tricky thing is that these functions return the "computed value" of the property, and I'm not sure if a property has a computed value if that property doesn't apply (but I'm not sure if it doesn't either, which is why I'll be asking others who are more expert on the data model here). paul
Received on Friday, 16 January 2004 11:15:56 UTC