Reece H. Dunn

Right, so the actual ambiguity is in LookupExpr parsing a TypeQualifier or NCName: ``` $tree??type(foo) ^^^^^^^^^ -- KeySpecifier / TypeQualifier ^^^^^^^^^^^ -- Lookup ^^^^^^^^^^^^^^^^ -- LookupExpr $tree??type(foo) ^^^^ -- KeySpecifier...

I'm not sure as I've only hand-written the XPath/XQuery parser, so would handle this case by maximally matching the TypeQualifier i.e. by placing it before testing for an NCName.

Could we define a `type::xyz` style axis and selector then? E.g. `$tree??type::foo`. -- That's clear enough and should not be ambiguous. It also generalizes to other axes as well such...

I'd be happy with keeping this syntax to a limited set of functions where it makes most sense. As noted, the motivation for this was `fn:concat` being written in the...

Collations define the ordering of characters/codepoints when performing string comparisons for sorting or comparing strings. They apply to the set of strings in the same group (e.g. family names) and...

1. How do you identify whether a string contains German, French, etc. when extracting it from e.g. a text node? 2. How do you deal with cases where a text...

Another issue with this is that it will make integrating with or using databases as a backend impossible. See e.g. [1]. Databases generally: 1. allow you to specify a single...

The equality and transitivity is given by the collation. With a single collation there is a well-defined ordering and comparison of codepoints. The issue is when dealing with multiple collations...

Collations are used for sorting as well as equality, as per fn:sort, etc.

But whatever approach we choose for equality needs to work with sorting/ordering. That's because collations are used for both of these and thus needs to work for both. An implementation...