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

RE: removing fo:color-profile requirement from fo:declarations

From: Paul Grosso <pgrosso@arbortext.com>
Date: Fri, 15 Oct 2004 16:22:02 -0400
Message-ID: <F13E1BF26B19BA40AF3C0DE7D4DA0C03F4295D@ati-mail01.arbortext.local>
To: "Glen Mazza" <grm7793@yahoo.com>, "XSL Editors" <xsl-editors@w3.org>

Glenn,

The XSL FO SG agrees that the + should be a *.

Paul Grosso
for the XSL FO SG

> -----Original Message-----
> From: xsl-editors-request@w3.org 
> [mailto:xsl-editors-request@w3.org] On Behalf Of Glen Mazza
> Sent: Monday, 14 June, 2004 22:02
> To: XSL Editors
> Subject: removing fo:color-profile requirement from fo:declarations
> 
> Editors:
> 
> In the 1.0Rec/1.1WD, the contents listing for fo:declarations[1] 
> requires at least one fo:color-profile child element:
> 
> Contents: (color-profile)+
> 
> However, there is an immediate qualification to this as follows:  
> "The fo:declarations flow object may have additional child 
> elements in a 
> non-XSL namespace."
> 
> With this qualification, the requirement for at least one 
> fo:color-profile seems strange.  Because you can use 
> fo:declarations for 
> non-XSL child elements, it is conceivable that a user could use 
> fo:declarations precisely for this reason, with no concern or need of 
> fo:color-profiles.
> 
> I recommend switching the fo:declarations contents listing to 
> the following:
> 
> Contents: (color-profile)*
> 
> This makes the entry of an fo:color-profile optional, and similar in 
> nature to the zero-or-more child FO requirements of fo:title, 
> fo:block, 
> fo:inline, and others.
> 
> Thanks,
> 
> Glen Mazza
> EDS / Apache FOP Team
> 
> [1] http://www.w3.org/TR/2003/WD-xsl11-20031217/#fo_declarations
> 
Received on Friday, 15 October 2004 20:22:38 UTC

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