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

XSLFO in the workflow

From: Tobias Reif <tobiasreif@pinkjuice.com>
Date: Fri, 17 Aug 2001 12:12:10 +0200
Message-ID: <3B7CEDFA.F6D5432D@pinkjuice.com>
To: xsl-editors@w3.org

when working with XSLFO, I need to validate the files consisting of pure

If it's impossible to validate pure XSLFO documents with a DTD;
then the working group should provide other means/technologies that can
serve that purpose.

If XML-schema is able to to that, then please provide one;
if not, then either further develop XML-schema to a stage where it can
validate all W3C XML namespaces, including XSLFO.

Scenarios showing the necessity for validation:

Scenario 1.
I transform some XML via XSLT to XSLFO, then I want to convert it to
PDF. During the last step the conversion tool (XEP, FOP) throws myriads
of errors at me. Now I need to know if the input document, which is
nothing than pure XSLFO, is valid; in order to take the appropriate
steps of either altering my XSLT to generate valid XSLFO, or filing bugs
on the converter.

Scenario 2:
I author pure XSLFO (which is inflexible, but flexibility is not always
required). So I would like to load a schema/DTD/anything into my
favourite XML IDE, and start. Without any validation tool it's time
consuming to look up every single detail of the rules for the structure
of FOs. Also, when I author some XML namespace that comes with a DTD, I
get a choice of all valid possibilities at any given point in the
document (drop down selections for attribute values etc)

The poularity of the RenderX trial of a DTD clearly shows that this is a
real world need.


This is another try; previous messages didn't appear in the archives.
Tobias Reif

Received on Friday, 17 August 2001 06:13:06 UTC

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