Hi Henri,
An XSLT 2.0 processor is also a perfectly good XSLT 1.0 processor for
the large majority of use cases. The incompatibilities between XSLT 2.0
in backwards compatible mode and XSLT 1.0 are detailed here:
http://www.w3.org/TR/xslt20/#incompatibilities
BTW the reason Saxon doesn't have column numbers in error messages is
because you can only get very limited location information back from a
standard SAX parser. I presume Xalan has it's own customized XML parser
in order to do what it does.
John
Henri Sivonen wrote:
> Validator.nu uses a patched version of oNVDL with Xalan as its
> Schematron 1.5 back end. I switched from Saxon 6 to Xalan in order to
> get column numbers in addition to line numbers on errors. However, I'm
> not happy with the performance of Xalan, which is why I'm considering
> going back to Saxon. To do that without feature loss, I need to patch
> Saxon to support column numbers.
>
> Should I put my effort into patching Saxon 6 or 9? That is, can I use
> Saxon 9 without breaking the semantics of Schematron 1.5 schemas that
> use XPath 1.0 queries?
>
> --Henri Sivonen
>
> http://hsivonen.iki.fi/
>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe:
> subscribe:
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
--
John Snelson, Oracle Corporation http://snelson.org.uk/john
Berkeley DB XML: http://www.oracle.com/database/berkeley-db/xml
XQilla: http://xqilla.sourceforge.net
