re: saxon 8 because we started with it two years ago and
don't want to take a chance on an upgrade right now.
A cross-your-fingers strategy that reminds me very much of the lead-up to
the current banking crisis.
Just remember that the longer you delay your upgrade
(a) the more work it will be, because
(i) the number of changes to the product will have accumulated,
(ii) you won't benefit from the fact that there are often aids to
transition, like marking methods as deprecated for a release or two before
removing them)
(iii) you will have written more application code that needs to be
converted
(b) the more likely you are to end up doing the upgrade in an emergency when
you hit some nasty bug that was solved several releases ago
(c) the less help you will be able to get.
Also remember that the current W3C specs were finished in January 2007, and
any Saxon release earlier than that is going to do some things in a way that
doesn't conform to the standard.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--