30130 2017-06-21 16:34:54 +0000 [xslt30] Trivial editorial errors in the final XSLT 3.0 Recommendation 2019-02-18 16:05:59 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Recommendation PC All RESOLVED FIXED P2 trivial --- 1 mike mike abel.braaksma public-qt-comments oldest_to_newest 128656 0 mike 2017-06-21 16:34:54 +0000 I'm opening this bug as a place to capture trivial typos in the XSLT 3.0 Recommendation, that should be fixed if we ever get a chance, but which don't warrant errata. 1. In 15.4, Streamable Merging, after the first example, in the sentence "This works because of the merge key is evaluated on the result of implicitly applying the snapshot function.": s/because of/because/ 128657 1 mike 2017-06-21 16:40:31 +0000 2. Immediately after the definition of error XTSE3200, in the sentence The value of Nth merge key value of an item J in a merge input sequence S is the result of the expression in the select attribute of the Nth xsl:merge-key child of the corresponding xsl:merge-source element, or in the absence of the select attribute, the result of the contained sequence constructor. This is evaluated with a singleton focus based on J, or, if streamable=yes is specified on the xsl:merge-source, a singleton focus based on a snapshot of J (see 15.4 Streamable Merging). s/The value of Nth merge key value of an item J/The value of the Nth merge key of an item J/ 128658 2 mike 2017-06-21 16:44:47 +0000 3. In 15.5 para 2, in the sentence: The syntax and semantics of an xsl:merge-key element are closely based on the rules for the xsl:sort element (the only exception being the absence of the stable attribute) s/only exception/only difference in syntax/ [There are other differences in semantics, for example the fact that with sort keys, the focus for evaluation sets position() to the position in the unsorted sequence, whereas with merge keys position() is always 1] 128724 3 mike 2017-07-17 11:38:07 +0000 In the second example of xsl:source-document in §18.1.2, rule 4 of the streamability analysis has the sentence: The right-hand operand @value, given that it appears in a node value context, is motionless. The parenthetical phrase "given that it appears in a node value context" is not aligned with the terminology in the final spec. It should say "given that the context posture is striding". 128931 4 mike 2017-10-13 20:25:27 +0000 Errata E3 and E9 have been drafted. 128938 5 mike 2017-10-19 16:22:29 +0000 The WG decided that we should record errors in the errata document however trivial they are. 128954 6 mike 2017-10-30 09:48:02 +0000 The errata were approved 129509 7 mike 2019-02-18 16:05:59 +0000 Note, there is some overlap here with bug #30382