Hello all, using Xalan for quite a long time, I like to give some comments: - I do XSLT 1.0 as long as I know the job is an easy one because I know the language (XSLT 1.0/XPath 1.0) well. - When I see problems ahead, I turn to XSLT 2.0 (and XPath 2.0), because the language is a lot more orthogonal. I do not have to make a distinction between the possibilities I have in XPath expressions, where I can have functions written in XSLT syntax, or from results from XSLT templates. - I do not use the Schema features in XSLT 2.0 because I didn't have the need, at least not until now.
I then use Saxon from Michael Kay and XML Spy for editing. For sure I have no time to consider contributing to such a formidable Task like the construction of an XSLT 2.0/XPath 2.0 implementation, unfortunately. Best regards, Werner -----Original Message----- From: Brian Minchau [mailto:[EMAIL PROTECTED] Sent: Dienstag, 5. Februar 2008 20:17 To: [EMAIL PROTECTED] Cc: xalan-j-users@xml.apache.org; [EMAIL PROTECTED] Subject: Apache Members Question: Xalan doing XSLT 2.0? Hi Gary. You were inquiring about an Apache version of XSLT/XPath 2.0 I'm a member of the Apache Xalan PMC, in fact I'm the Chairperson. In this note I'm not speaking on behalf of the PMC. The PMC discusses non-confidential business on the xalan-dev mailing list. I can tell you that nothing has been discussed in private by the PMC outside of that mailing list for quite some time (years). If the PMC had put in place any plans for producing an XSLT/XPath 2.0 implementation, it would have been discussed on the xalan-dev mailing list, and it hasn't been discussed on this list. I personally would very much like to see an open source XSLT 2.0 implementation developed by Apache. However, I don't think a "critical mass" of contributors who are able to commit the time necessary to produce such an implementation has stepped forward yet. (I myself am unable to commit the time right now.) Until we achieve that critical mass, we won't see an XSLT 2.0 implementation in this space. - Brian - - - - - - - - - - - - - - - - - - - - Brian Minchau e-mail: [EMAIL PROTECTED]
