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

CM recommendation for fo:static-content and fo:flow

From: Glen Mazza <grm7793@yahoo.com>
Date: Mon, 4 Jul 2005 07:50:19 -0700 (PDT)
Message-ID: <20050704145019.15606.qmail@web81912.mail.mud.yahoo.com>
To: XSL Editors List <xsl-editors@w3.org>

[Happy Independence Day fellow Americans!]


One more 1.1 WD CM suggestion (just editorial here)--
the constraints defined within fo:marker and
fo:retrieve-marker prohibit these FO's from being
descendants of fo:static-content and fo:flow,

I think it would be very helpful for the implementor
if these two rules were copied (or moved) to the CM
definitions of the parent fo:flow and
fo:static-content FO's.  I originally missed
implementing enforcement of these rules for fo:flow
and fo:s-c in FOP, because they were missing from
these FO's CM definitions.

For almost all of the formatting objects, the content
model is fully defined in the CM for that formatting
object--i.e., it is not necessary to do a full scan of
the XSL specification in order to determine the actual
CM of a formatting object.  This saves sanity on the
part of the implementor, and also adheres to the idea
normally held by the recommendation that the parent FO
defines its CM, rather than having child FO's
determine their legal parents.  


Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
Received on Monday, 4 July 2005 14:50:26 UTC

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