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
Saxonica
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--