Hi Bryan, hi everybody,
Bryan Rasmussen wrote:
A know little about his company but taking a glance on the developer
count [2] the opensource community around Saxon seems quite singular.
On the other hand I see heavy traffic on the dev mailing list of Xalan
[3].
Pro's and cons both ways to my way of thinking.
The source is available on sourceforge though.
It seems the source is used more for translation to other platforms,
implementations, I'm thinking specifically of that .Net XSLT 2.0 open source
processor, can't remember name, but they started from the Saxon source.
Maybe people don't work with the Saxon source cause there isn't any need for
it. What I mean is that there would seem to be a good community of people
with familiarity with the source, I expect that if Saxon was dropped then
people would start maintaining it as well. As has happened with other
one-man open source projects in the past.
That is a good point.
Concerning the comparance of features (aside of XSLT2) and performance
of XSLT processors I am in need of some more facts (preferable links).
For example, are there recent results of a common XSLT testsuite, which
guarantees the user a common feature set?
>For compliance, or speed or something else?
>XSLT has no formal (W3C) test suite to my knowledge.
http://www.oasis-open.org/committees/documents.php?wg_abbrev=xslt may help.
http://www.datapower.com/xmldev/xsltmark.html for performance.
Actually Michael Kay did a presentation at xtech 2005 on performance
comparisons between Xquery/XSLT, including a discussion of certain types of
optimization that people often don't do. I was under the impression that
these optimizations which increased performance were included in the latest
Saxon, and that performance was at this point among the best.
Many thanks to all of you, who posted informations about XSLT processors.
It became clear that to many of us a XSLT 2.0 compliant processor is a
desired feature in the next Office release (OOo 3.0).
In the meantime I will exchange informations with Sun's JDK team, as
they might run into the same problem with upcoming JDKs.
If anybody stumbles over further informations, as XML processing
benchmarks, please post them.
- Svante
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
