Michael Kay
Michael Kay
I think it would be a lot less confusing if instead of ``` **Expression:** hash("abc") => string() **Result:** "900150983CD24FB0D6963F7D28E17F72" ``` we wrote: ``` **Expression:** hash("abc") **Result:** xs:hexBinary("900150983CD24FB0D6963F7D28E17F72") ```
Rebased to current master, and fixed a typo.
(1) I don't think a feature that changes the spec, by relaxing constraints that the specification imposes on implementations, can be considered vendor-specific. (2) The performance effect of using the...
Let me just address one of your points: `As the File Module states that file:write is ·nondeterministic·, my point of view is that the function is not implemented correctly if...
>Why should then someone write transient { file:write(....) } My primary use case for this feature has nothing to do with achieving predictable behaviour for nondeterministic functions. It's all about...
This proposal met some resistance and I've decided to withdraw it.
Rebased against current master to get a better diff.
Q1: I chose to make this an error; you can't select two items A and B if one contains the other. Dropping the update on the child would have been...
I see the deep-update function as a primitive onto which we can put XQuery/XSLT syntactic sugar, so I'm not too concerned about the usability of the function. The main reason...
One potential simplification would be to select (for replacement) only values that are immediate members of an array or entry-values of a map, rather than individual items within those values....