Implementing 2.0 requires some moderately basic data structure changes to track Schema types (I believe there's a stub in the code, but not more than that) and to handle Sequences which aren't simply nodesets. Doable, but not simple.
I'd love to see Xalan tackle it -- but Xalan lost its most active contributors a few years ago due to time demands from Real Jobs, and development slowed down as a result. Starting with some of the 2.0 functions (a 2.0 subset) is an interesting idea. Unfortunately I don't think there's any good way to make that very portable; it would have to be treated as extensions to a 1.0 processor which are syntax-compatible with the 2.0 versions. And you certainly couldn't tackle the whole 2.0 library; some of the functions use sequences and schema-types. So... I'd say that if you like the idea, you should start drafting versions of this and submit them to Xalan as proposed changes when you've got a large enough bundle to be an interesting contribution. But you might want to check with the current committers to see whether they'll be receptive to the idea before starting. (I'm probably still on that list, but as the blues song says, I'm currently "overworked, underpaid, underloved and overlayed." ______________________________________ "... Three things see no end: A loop with exit code done wrong, A semaphore untested, And the change that comes along. ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish ( http://www.ovff.org/pegasus/songs/threes-rev-11.html)
