Backwards-compatible behavior is really important and complicated issue.
According to XSLT 2.0 docs (see http://www.w3.org/TR/xslt20/#backwards)
"It is implementation-defined whether a particular XSLT 2.0 implementation
supports backwards-compatible behavior".
We are analyzing this issue.
Igor Hersht
XSLT Development
IBM Canada Ltd., 8200 Warden Avenue, Markham, Ontario L6G 1C7
Office D2-260, Phone (905)413-3240 ; FAX (905)413-4839
Foxyshadis
<[EMAIL PROTECTED]
il.com> To
[EMAIL PROTECTED]
04/05/2004 06:27 cc
AM
Subject
Retrofitting XSLT2 into Xalan 2
Please respond to
xalan-dev
I'm wondering just how similar the codebases for XalanJ2 vs. 3 are shaping
up. In particular, I'm wondering if it would be possible at all to migrate
backward XSLT2 features, like for-each-group or regular expressions, as
extension elements into XalanJ 2. I know the low level requirements of the
two are somewhat different, but I don't know how that effecs the various
elements.
I haven't kept up with the development of the xslt20 branch at all, and
it's been almost a year since I actively worked on extensions to the
current one, so I feel a bit out of my league at the moment. However, if I
become interested enough in the topic, I might try out something along
these lines. If successful, it would beat abusing the nodeset/evaluate
functions or the key function for complex grouping.
Foxy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
