Re: [xsl] transform optimization for a schema-constrained domain

Joerg Pietschmann wrote

> Again, to press my point home: A processor which would use a DTD/Schema
> to catch misspelled element names and some expressions which would always
> result in an empty node set because of DTD/Schema-constraints would have
> saved me a lot of debugging time. I see this as a feature which could be
> turned on at development time, much like tracing.
>
> You may have noticed that this might have prevented quite a few "why is
> there no output from my code?" questions on this list (assuming the guys
> had a proper DTD attached...)
>
> Are there other XSLT-users who think this could be a useful feature?
> Rally to the flag! We might convince some friendly processor implementors
> to implement it for us :-)
>
> Well, asking for DTD support would probably be to much. Schemas are XML
and
> could probably hooked into the processors much easier, without inventing
> APIs for element definition access and such stuff. So i'm willing to
settle
> for Schema support only :-)

SAX-based processors do already have an API to give them access to DTD
declarations.  Not all SAX processors support them, but they have been
defined.  See DeclHandler from the SAX2-ext package at [1].

Regards
~Rob

--
Rob Lugt
ElCel Technology
http://www.elcel.com/

[1] http://www.megginson.com/Software/index.html




 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list