Michael Kay
Michael Kay
During discussion of the `??` operator it was pointed out that we need more examples and explanation, especially of how to handle cases where the "flattening" behaviour of the operator...
We've made a decision -- for good reasons of maintaining extensibility -- not to make any of the functions in the system function library variadic. I think this raises the...
In §5.14 we document two changes to "declare default element namespace": 1. The [default namespace for elements and types] can now be declared to be `fixed` for a query module,...
Adds rules for the default priority of new match pattern options such as `element(p:*)` and `element(p|q)`. Fix #1394
With the number of functions in the fn:namespace now standing at 213, the use of a drop-down in the F+O "function finder" has become a little unwieldy. Are there ways...
We have dropped the syntax `??type(T)` for filtering the results of lookup expressions, because of problems with syntax ambiguity. This issue seeks an alternative. Although selection by type also makes...
The following functions define an argument that has a default value, but don't allow () to be supplied explicitly: ``` lang id element-with-id idref parse-html ``` As determined by running...
We have introduced two syntax extensions which achieve the same effect: `element(a|b)` vs `(element(a)|element(b))` Do we actually want both? If we do, I would suggest that we define `element(a|b)` as...
There are new possibilities for node tests used as XSLT patterns, for example `element(p:*)`, `element(*:local)`, `element(p:*, T)`, `element(*:local, T)`. These need to have default priorities assigned.