[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Saxon for C/PHP/Python/etc

Subject: RE: [xsl] Saxon for C/PHP/Python/etc
From: "R.Arulselvan, DS-Technology, Chennai" <arul.selvan@xxxxxxxxxxx>
Date: Thu, 24 Oct 2013 17:02:27 +0530

My email id changed, pls update it!


Arulselvan Rangarajan
Direct: +91 (0)44 4916 2259 | Ext 259
Mobile: +91 (0)9710416093  | arul.selvan@xxxxxxxxxxx

-----Original Message-----
From: Michael Kay [mailto:mike@xxxxxxxxxxxx]
Sent: Friday, October 04, 2013 7:04 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Saxon for C/PHP/Python/etc

> This does come up in the context of people wanting a XSLT 2.0-lite,
> but if starting now -- and starting a Kickstarter-like campaign now --
> would it be better to architect for something that could grow to full
> XSLT 2.0 or something that could grow to full XSLT 3.0?

You can certainly add functions and operators and instructions
incrementally, but changing the data model is a "big bang" and pretty well
has to be done before you can do anything else. There's no point
implementing bits and pieces on top of a 1.0 data model, as they will all
have to be reworked later.

I would just make one point about funding, which is that if you're asking
people for money, you not only need to persuade them that the product is
needed (which in this case should be fairly easy), but also that you can be
relied upon to deliver it. I've seen several attempts to write XSLT
processors in C fail; it's not an easy task.

Michael Kay

This e-mail and/or attachments are confidential and may also be legally
privileged. If you are not the intended recipient, any disclosure, copying,
distribution or action taken relying on the contents is strictly prohibited
and may be unlawful. If you have received this communication in error, please
notify the sender immediately by responding to this e-mail and deleting the
contents of the e-mail & related attachments from your system. Though MPS
Limited has taken reasonable steps to ensure no viruses are present in this
e-mail, it cannot accept responsibility for any loss or damage arising from
the use of this e-mail or attachments. No contracts may be concluded with MPS
through e-mail communication. Please consider the environment before printing
this e-mail.

Current Thread