W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2014

[Bug 24543] Supplying a streamable initial context item on a non-streamable initial mode

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 Jul 2014 13:34:49 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24543-523-pbr06raiyC@http.www.w3.org/Bugs/Public/>

--- Comment #9 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Yes, I think that would work and solve the issues with
xsl:accumulator/@initial-value and global params/variables.

I'm not sure we need to restrict the type, though. If the type is a non-node,
streamable="yes" simply has no effect and every initializing expression is
grounded by default (i.e., type-determined context posture). If the type is not
a document node, it can still be streamable="yes", because the rule for
allowing expressions such as "/" or "root()" already says "if the context item
is statically known to be a document node" (see, and will statically
(and correctly) fail.

Still, if as="element()" you can do expressions such as base-uri(.) or
ancestor-or-self::*/name(), which are motionless.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 16 July 2014 13:34:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:47 UTC