XPath 3.1 support

Are you missing a feature? Request it's implementation here.
Martin Honnen
Posts: 56
Joined: Tue Aug 19, 2014 12:04 pm

XPath 3.1 support

Post by Martin Honnen » Sat Feb 23, 2019 6:33 pm

Given that the current and latest (and probably last) version of XPath is 3.1 and not 3.0 I wonder why the XPath field and the XPath builder in oXygen 21 continue to only list 3.0 as the possible highest XPath value.

It also seems that some XPath 3.1 language features like the string concatenation operator "||" work nevertheless, so that seems to indicate that under the hood you use a version of Saxon that supports XPath 3.1 and not 3.0.

When I use other features like the XPath 3.1 map or array types, for instance

Code: Select all

array { //*[not(*)]/string() } 
against any XML document that does have some leaf elements with text data I get no error that I have used some expression not being supported, instead a dialog pops up "The XPath query returned no results".

This feature request is to allow the use of full XPath 3.1 and some way to allow an XPath query to return maps and/or arrays.

tavy
Posts: 187
Joined: Thu Jul 01, 2004 12:29 pm

Re: XPath 3.1 support

Post by tavy » Mon Feb 25, 2019 1:43 pm

Hello Martin,

Thanks for the feedback.
Yes, the XPath support in Oxygen is 3.1. I added an issue to change the XPath version in the user interface.
For the XPath result, to return maps and/or arrays, we need to update our internal result model to support this type of constructs. I added an issue also for this.

Best Regards,
Octavian
Octavian Nadolu
<oXygen/> XML Editor
http://www.oxygenxml.com

tavy
Posts: 187
Joined: Thu Jul 01, 2004 12:29 pm

Re: XPath 3.1 support

Post by tavy » Mon May 27, 2019 2:34 pm

Hello Martin,

We just released Oxygen 21.1. The issue that you reported regarding the XPath version presented in the interface has been solved.
Thanks again for your feedback.

Best Regards,
Octavian
Octavian Nadolu
<oXygen/> XML Editor
http://www.oxygenxml.com

Post Reply