Re: [xsl] Are there any free, fully-compliant XSLT/XPath 3.0 processors?

Subject: Re: [xsl] Are there any free, fully-compliant XSLT/XPath 3.0 processors?
From: Adam Retter <adam.retter@xxxxxxxxxxxxxx>
Date: Sun, 27 Jan 2013 12:38:29 +0000
eXist is working towards full XPath and XQuery 3.0 compliance and we
already implement most of this. eXist is open source under LGPL 2.1

Whilst eXist can run as a standalone database you can also use it as
an embeddable library in your own Java applications and it will allow
you to execute XPath 3, XQuery 3 and XSLT 2.

On 27 January 2013 08:09, James Fuller <james.fuller.2007@xxxxxxxxx> wrote:
> Hello Roger,
> Yes I see your situation ... when non techies are confronted by
> choosing between XYZ technology and one has a cost and another
> apparently has no cost ... they classically drift towards the zero
> cost solution. I sometimes wonder how much 'impl' detail to give to
> people making cost decisions ... e.g. there is always a cost
> associated with adopting any software.
> I believe what your challenge is to present the true costs of both
> approaches; remember to include major risks as well (what if Oracle
> wanted to try and kill off Java ???). as the positives (xslt has a
> rich history in document manipulation)(extensible markup is not going
> away). Software is a bit different then buying some part of a piece of
> machinery, it can enable cost optimisations but it can also present
> new opportunities which create new revenue generating scenarios ... I
> sometimes think the most successful software is when it was brought in
> to do a job (does it well), and also enables a range of future
> positive scenarios.
> While having a 'free' implementation may seem like a 'silver bullet'
> solution to your conundrum its not ... you have enough 'free' out
> there IMO to tell your non techies the story.
> A software license of a few k to a medium sized company represents a
> very minor cost (Compared to the humans running/managing the software)
> .. .its easy to demonstrate how the license pays for itself, getting
> over that first unit of currency is the issue.
> gl, Jim Fuller
> On Sun, Jan 27, 2013 at 12:16 AM, Costello, Roger L. <costello@xxxxxxxxx>
>> Liam wrote:
>>     If you see XPath as a domain-specific language
>>     for pointing into XML documents, or into XDM
>>     trees, it's hard to see a lot of people wanting
>>     to pay for something if all it did was save them
>>     money, improve reliability, reduce costs and
>>     speed up development.
>> That is a wonderful argument Liam. When I tell my operational people this
and then tell them, "Oh, you want to distribute this capability to the xx
thousands of people in the field. Okay, I'll implement it using XSLT/XPath and
you'll have to buy a license for them and that will cost many yy thousands of
dollars." They simply respond, "No, do not use XSLT/XPath. Implement the
capability in Java and distribute it for free to the people in the field."
>> Dimitre wrote:
>>     BaseX is free and as an XQuery 3.0 implementation
>>     it is also an XPath 3.0 implementation.
>> Thanks for notifying me of this Dimitre. I took a look at it. It appears to
be a database supporting XPath and XQuery queries. That won't help me build
fieldable applications. Please correct me if I am wrong.
>> Jim wrote:
>>     Who are the people you are trying to convince
>>     to use XSLT vnext ? .. it might be that these folks
>>     will never learn such a language as XSLT e.g. are
>>     the docheads ? datageeks ? Javascript folk ?
>> Jim, they are non-techies. They don't care about XML or XSLT or XPath. They
are people with real, operational needs. Particular technologies is of no
interest to them. But telling them that by using XSLT/XPath they will have to
purchase licenses costing many yy thousands of dollars -- that gets their
attention. And immediate dismissal of XSLT/XPath.
>> /Roger

Adam Retter

skype: adam.retter
tweet: adamretter

Current Thread