W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2016

[Bug 30033] [xslt30] Streamability rules for fn:current() lack an "otherwise" clause

From: <bugzilla@jessica.w3.org>
Date: Fri, 16 Dec 2016 10:44:17 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30033-523-1bRAQnflDl@http.www.w3.org/Bugs/Public/>

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
Proposed resolution:

Explanations in "[]", which may become notes in the spec if appropriate.

(1) Add special rules for the static type of a call to current():

(a) if the call is within an XPath expression, the *context item type* that
applies to the outermost containing XPath expression, determined by the rules
in 19.2.

(b) if the call is within a pattern, the *match type* of the pattern, as
defined in 19.2. [Note: a call to current() in a pattern will always be within
a predicate, which means that the match type of the pattern will never depend
on the static type of the call to current(), so there is no circularity in this

In, Streamability of fn:current(), change the rules to (§§ marks

The sweep and posture of a call to the current function are determined as

§§1. If the call appears within a pattern [Note: it will always be within a
predicate of the pattern], then climbing and motionless.

2. Otherwise, let E be the outermost containing XPath expression of the call to
the current function.

2(a) If the context posture of E is grounded, then motionless and grounded.

2(b) If the path in the expression tree that connects the call on current to E
(excluding E itself) contains an expression that is a higher-order operand of
its parent expression, then climbing and motionless.

§§2(c) Otherwise, the posture is the context posture, and the sweep is

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 16 December 2016 10:44:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:03 UTC