XPath version identifier feels a bit confusing

[dret]

It seems a little odd that one identifier for XPath is xpath-30 and the intention seems to be that it identifies XPath 3.1. There is an existing XPath 3.0 specification which may not be what's intended to be referenced with the xpath-30 string, or is it?

https://www.w3.org/TR/xpath-30/

[frankkilcommins]

Hey @dret,

By default, if criteria in Arazzo leverage a type of xpath, then XPath 3.1 is assumed. See https://spec.openapis.org/arazzo/latest.html#fixed-fields-9

If you want to downgrade on either JSON Path or XPath, then one can leverage the Criterion Expression Type Object. This object allows one to state their intention to use syntax conforming to an older variant. The expectations are:

• xpath-30 for XPath 3.0
• xpath-20 for XPath 2.0
• xpath-10 for XPath 1.0

Regarding the Criterion Expression Type Object, Arazzo states the following:

An object used to describe the type and version of an expression used within a Criterion Object. If this object is not defined, then the following defaults apply:

• JSONPath as described by [RFC9535]
• XPath as described by XML Path Language 3.1

[dret]

Thanks, I think I did not fully understand the mechanics. But wouldn't it then be useful to also allows xpath-31 as a value even if that is the default? That would allow people to make their choice explicit.