Hello David, Sorry for the delay. We run both XPath 2.0 and 3.1 query expressions using the Saxon 11 Enterprise Edition XSLT processor, providing the XSLT processor with the proper XPath version. In such cases probably as you say the XSLT processor should report more precisely if certain expressions although supported by it are not quite compatible with the imposed expression version. But this is not something we control. Regards, Radu Radu Coravu Oxygen XML Editor On 10/27/22 05:23, David Birnbaum wrote:
Dear oxygen-user@oxygenxml.com,
If I select XPath version 3.1 in the XPath toolbar and evaluate an expression like:
*//l => count()*
in a document that contains *<l>* elements, it correctly returns the count of those elements. If I select XPath 1.0 and evaluate the same expression, it correctly raises an error because it doesn't understand the arrow operator, which is not part of XPath 1.0. If I select XPath 2.0 I also expect an error because the arrow operator is not part of XPath 2.0, but instead the result is the same as with 3.1. Am I mistaken in expecting 2.0 to raise an error here?
Sincerely,
David
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user