Subject: Re: [xsl] Input requested for a good genuine example of the best parts of XSLT 2 From: Rashmi Rubdi <dev_subscriptions@xxxxxxxxx> Date: Wed, 24 Jan 2007 17:16:49 -0800 (PST) |
I don't mean to interrupt this thread but I'm simply replying one of the statements made earlier. May this thread continue. >> until then, those who use Xalan have to stay with XSLT1.0. > >Or switch to Saxon if they can. (Xalan is Java too, isn't it?) It is not possible to switch to Saxon in the case of certain Java developers who use JSP Tag Libraries (JSTL), because JSTL uses Xalan. I don't know and don't think JSTL works with Saxon. JSTL comes with XML processing tag it reads the XML and the XSL file, and then transforms them inside the JSP file. So, JSP, JSTL developers have to wait until Xalan implements XSLT2.0 and XPath2.0 , until then I guess it's a good idea to practice XSLT2.0 with Saxon. I was reading on a thread (I'm unable to find it at the moment), where they mentioned that implementors wait till XSLT becomes a W3C recommendation, before they even proceed to implement the changes only because the changes are not finalized. Perhaps .Net and other technologies have support for XSLT2.0, I don't know about that. -Rashmi ----- Original Message ---- From: Abel Braaksma <abel.online@xxxxxxxxx> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Sent: Wednesday, January 24, 2007 5:36:45 PM Subject: Re: [xsl] Input requested for a good genuine example of the best parts of XSLT 2 Rashmi Rubdi wrote: > For example 2.0 has an extensive set of date functions, it has a function dedicated to convert upper case to lower case unlike 1.0. > indeed, see my example stylesheet. > Some of us don't have a choice but to stick with XSLT1.0 for a while, until the dependent technologies implement the features of XSLT2.0 > I know, I am aiming at those who can, because they have a choice (.NET developers, Eiffel developers, Java developers etc) > Given that XSLT2.0 and XPath2.0 attained W3C recommendation status only a day ago, it will take time before dependent technologies like Xalan upgrade from XSLT1.0 to 2.0 > a long time, likely, as it is quite a complex standard, especially considering the SA parts, of which only one compliant implementation is available. > Otherwise using the latest version of XSLT is as simple as, using better and easier features. > > Are you trying to translate everything written in XSLT1.0/XPath1.0 to their 2.0 version No. Maybe I did not make my point clear. I wanted to invite everybody involved with XSLT 2 (and XPath 2, for that matter) to augment or alter my example of showcasing / displaying the main (or typical) features that XSLT 2 has to offer in comparison to XSLT 1. I am quite aware of XSLT 2 and all that's involved. I am using it for > 2 years now, of which 1 year more actively. What I am trying to achieve is a showcase template that can be used to trigger people sticking to XSLT 1 to consider moving to XSLT 2. Something like: look, you can do this and that in XSLT 2 that you can't in XSLT 1. Look at my proposal template. It showcases several key concepts, but I am sure others will find other things important to show the main characteristics of XSLT 2. I am aiming for some input to end up with a best-of-breed showcase XSLT 2 example template (wow, that's a mouthful!) Cheers, -- Abel Braaksma _____________________________________________________________________________ _______ Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Input requested for a goo, Abel Braaksma | Thread | RE: [xsl] Input requested for a goo, Michael Kay |
Re: [xsl] XSLT 2.0 has arrived, David Carlisle | Date | [xsl] ANN: Naxos, an XSLT 1.0 proce, Deborah Pickett |
Month |