Subject: Re: [xsl] Are there any free, fully-compliant XSLT/XPath 3.0 processors? From: Michael Sokolov <msokolov@xxxxxxxxxxxxxxxxxxxxx> Date: Sun, 27 Jan 2013 15:12:14 -0500 |
We are slow adopters: used to use 1, switched to 2 only in the last couple of years. The main advantages we noticed at first were enhanced function library (especially the string functions), and the ability to have more powerful XPath expressions - I think being able to express sequences wasn't possible in XPath 1 (vague on the details, sorry), and there were some real pain points there. Even now, I don't think anyone in my office has quite figured out how to use the grouping operators in XSLT 2 - not because they're dumb, but just because the need only arises infrequently and they've already figured out how to write complex recursive XSLT 1 expressions that do the job, howeever painfully. I am advocating the use of more X-technologies, but most of the guys I work with are Java- and Javascript-oriented, and interested in staying up with the latest trends, which seems to mean node.js, Grails, and other stuff I'm not current with. I don't think they're even aware there *is* such a thing as X*/3.0. But of course this is only one shop, and maybe not the sweet spot for the tech?
My simple questions, Who is aligned to each of the 3 specs? Agreed it's a bit early
for 3.0 and many won't have decided yet, though the 1 to 2 changes are a good
intimation of where 3.0 has gone.
Suggested form of a question.
For the majority of your work do you use 1, 2 or (plan to move to) 3.0?
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Are there any free, fully, davep | Thread | Re: [xsl] Are there any free, fully, Adam Retter |
Re: [xsl] Are there any free, fully, Dimitre Novatchev | Date | Re: [xsl] Are there any free, fully, Adam Retter |
Month |