Jörn Nettingsmeier wrote:
[ ... ]
Therfore i decided to do the first step in java in order to resolve
all includes and following all refs to their defs.
This class then generates the appropriate xslt-file.
supporting only a subset of rng was a design decision to keep the
prototype simple and get working results more quickly. it's by no means
impossible (actually quite easy since xslt2 supports intermediary result
trees) to support all internal and external refs with plain xsl code.
Nice to hear ....
as to my choice of language, it may be hard to believe for anyone who
has tried to solve nontrivial problems in xslt version 1, but
That's the reason why I did not even think of starting it with xslt ....
xslt2/xpath2 is actually beautiful and very pleasant to use, mostly due
to the fact that variables are no longer second-class citizens and can
contain usable trees, and to the introduction of <xsl:function/>.
So, I need to dig into xslt2/xpath2 :-)
Jann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
