@qt4cg statuses

This is MK's PR with the compiled form of the schema added.

The CG agreed to merge this PR at meeting 151.

Close #2404 Close #2403 Close #2177

With the current grammar…

AxisStep         ::=  (AbbreviatedStep | FullStep) Predicate*
AbbreviatedStep  ::=  ".." | ("@" NodeTest) | SimpleNodeTest
FullStep         ::=  Axis NodeTest
NodeTest         ::=  UnionNodeTest | SimpleNodeTest
SimpleNodeTest   ::=  TypeTest | Selector
TypeTest         ::=  NodeKindTest | JNodeType

…type tests in axis steps are limited to node() and its subtypes as well as jnode(). The test cases include tests for additional types like gnode() or array(*).

Maybe TypeTest should be replaced by the RegularItemType:

RegularItemType  ::=  AnyItemTest | NodeKindTest | GNodeType | JNodeType | MapType | ArrayType | RecordType | EnumerationType

The current spec defines the following grammar for the jnode type:

JNodeType  ::=  "jnode" "(" (("*" | NCName | Constant) ("," ("*" | SequenceType))?)? ")"
Constant   ::=   StringLiteral | ("-"? NumericLiteral) | QNameLiteral | ("true" "(" ")") | ("false" "(" ")")

As far as I can judge, none of the current test cases seems to use this syntax. Instead, the tests I found expect a single sequence type argument, for example fn-jtree-006:

<test-case name="fn-jtree-006">
  <description> JNode applied to an array - type of result</description>
  <created by="Michael Kay" on="2025-06-16"/>
  <test>fn:jtree([1,2,3]) instance of jnode(array(xs:integer))</test>
  <result>
    <assert-true/>
  </result>
</test-case>

Is it the test suite or the spec that needs to be updated?

If this is still subject to discussion, my preference would be to disallow constants in the jnode syntax:

• It is not clear to me how fn:jtree({ 'a': 1, 'b': 2 }) instance of jnode(a)` can be interpreted.
• Instance checks for linear hierarchies are generelly more intuitive.
• With the presence of get(), the jnode constants should be redundant.
• We can only use atomic items in the node tests for which literals exists.

In EXPath Binary Module 4.0 some example functions have been redefined in a different namespace prefix (which was bin:) to avoid suggesting they were part of the supported library.

However in 2.2 Example – reading and writing variable length ASN.1 integers, the definitions of asn:int-octets() and asn:encode-ASN-integer() still contains references to the original prefix definition bin:int-octets() which should be asn:int-octets()