Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Requests for XSLT 2.0 support

Requests for XSLT 2.0 support

2007-08-07       - By Henry Zongaro

Hello.

Henry Zongaro/Toronto/IBM@(protected) wrote on 2007-07-26 06:05:40 AM:
> I'd like to find out how much interest there is from others in
> seeing an open source XSLT 2.0 implementation from the ASF.  If
> you're interested in such an implementation (as a user), please
> respond and let us know which features you're most interested in.
> And conversely, I would also like to hear from any users who are
> satisfied with an XSLT 1.0 processor, and not much interested in
> migrating to XSLT 2.0.
>
> Feel free to respond either on the mailing list or to me directly,
> in private.  I'll summarize the results of this informal polling in
> a week or so.

I received eight (8) responses in which users indicated that they would
like to see an open source implementation of XSLT 2.0 from the ASF.  The
following features were mentioned as most desirable:

o Schema validation
o xsl:for-each-group
o xsl:analyze-string
o Regular expression support
o Applying path expressions to temporary trees
o Expanded repertoire of string functions
o Streaming capability for large documents

I should note that streaming capability isn't something that's really
changed from XSLT 1.0 to XSLT 2.0.

One respondent indicated that they like Xalan-J's support for Java and
scripting extension functions, and that having those facilities in an XSLT
2.0 implementation would make for a very desirable processor.

One respondent wanted Xalan to be as feature-rich as possible, but was
unsure whether their customers would require XSLT 2.0 features.  That
particular respondent didn't want Xalan's lack of XSLT 2.0 features to
impede customers, but indicated that that hasn't happened yet.  I didn't
include that response among the positive responses I received.

Nobody indicated that they are satisfied with XSLT 1.0.

Thanks,

Henry
------------------------------------------------------------------
Henry Zongaro      XSLT Processors Development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@(protected)


<br><tt><font size=2>Hello.</font></tt>
<br>
<br><tt><font size=2>Henry Zongaro/Toronto/IBM@(protected) wrote on 2007-07-26
06:05:40 AM:</font></tt>
<br><tt><font size=2>&gt; I'd like to find out how much interest there
is from others in <br>
&gt; seeing an open source XSLT 2.0 implementation from the ASF. &nbsp;If
<br>
&gt; you're interested in such an implementation (as a user), please <br>
&gt; respond and let us know which features you're most interested in.
&nbsp;<br>
&gt; And conversely, I would also like to hear from any users who are <br>
&gt; satisfied with an XSLT 1.0 processor, and not much interested in <br>
&gt; migrating to XSLT 2.0. <br>
&gt; <br>
&gt; Feel free to respond either on the mailing list or to me directly,
<br>
&gt; in private. &nbsp;I'll summarize the results of this informal polling
in <br>
&gt; a week or so.</font></tt>
<br>
<br><tt><font size=2>I received eight (8) responses in which users indicated
that they would like to see an open source implementation of XSLT 2.0 from
the ASF. &nbsp;The following features were mentioned as most desirable:</font><
/tt>
<br>
<br><tt><font size=2>o Schema validation</font></tt>
<br><tt><font size=2>o xsl:for-each-group</font></tt>
<br><tt><font size=2>o xsl:analyze-string</font></tt>
<br><tt><font size=2>o Regular expression support</font></tt>
<br><tt><font size=2>o Applying path expressions to temporary trees</font></tt>
<br><tt><font size=2>o Expanded repertoire of string functions</font></tt>
<br><tt><font size=2>o Streaming capability for large documents</font></tt>
<br>
<br><tt><font size=2>I should note that streaming capability isn't something
that's really changed from XSLT 1.0 to XSLT 2.0.</font></tt>
<br>
<br><tt><font size=2>One respondent indicated that they like Xalan-J's
support for Java and scripting extension functions, and that having those
facilities in an XSLT 2.0 implementation would make for a very desirable
processor.</font></tt>
<br>
<br><tt><font size=2>One respondent wanted Xalan to be as feature-rich
as possible, but was unsure whether their customers would require XSLT
2.0 features. &nbsp;That particular respondent didn't want Xalan's lack
of XSLT 2.0 features to impede customers, but indicated that that hasn't
happened yet. &nbsp;I didn't include that response among the positive responses
I received.</font></tt>
<br>
<br><tt><font size=2>Nobody indicated that they are satisfied with XSLT
1.0.</font></tt>
<br><tt><font size=2><br>
Thanks,<br>
<br>
Henry<br>
------------------------------------------------------------------<br>
Henry Zongaro &nbsp; &nbsp; &nbsp;XSLT Processors Development<br>
IBM SWS Toronto Lab &nbsp; T/L 969-6044; &nbsp;Phone +1 905 413-6044<br>
mailto:zongaro@(protected)</font></tt>
<br>