29053 2015-08-12 11:03:04 +0000 [xslt3.0] Streamability: current()/name() 2015-10-29 12:42:26 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 1 mike mike public-qt-comments oldest_to_newest 122566 0 mike 2015-08-12 11:03:04 +0000 Regarding the streamability of current(). In 19.8.9.3, we say (in a note) <quote> The effect of the rule is that expressions that use current as an operand with usage inspection are allowed (for example, name(current()) or current()/@class), but other operand usages fail. </quote> There's a problem here in that path expressions (like current()/@class) don't use the General Streamability Rules, and therefore don't define operand usage for their operands. It's not correct to imply that the LHS of a path expression has usage inspection. The *concept* of operand usage is defined for all operands of all expressions (see 19.4), and this section also states <quote> The assignment of operand usages to each operand role of each kind of construct is defined in 19.8 Classifying Constructs. </quote> But in fact we don't assign an operand role in all cases, including the common case cited here. (I came across this because I was trying to implement the rules for streaming current() in terms of operand usage, rather than using the normative algorithm in the spec, and it didn't work.) 122710 1 mike 2015-08-21 20:39:01 +0000 The WG agreed to change the Note under "streamability of current()" to retain the examples of constructs that work, but to remove the reference to operand usage inspection; and to clarify the description of the concept of "operand usage" to make it clear that it is not defined for all constructs. The changes have been applied.