W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2017

[Bug 30064] [xslt30ts] Test case function-5006

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Mar 2017 14:20:04 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30064-523-F1j3BLvBpM@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30064

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Rereading my own comment, you could conclude there are two things here:

1) it is possible to interpret the current rules liberal enough to make path
expressions like .//x streaming

2) it is not clear that .//x (or $a//x) is not streamable

3) suggested fix is to allow path expressions .//A/B or $x//A, I believe the
intent of our text and rules is to allow such expressions anyway

Wouldn't another definition of scanning expressions be that (draft definition,
needs tuning): 

<DEF>
If each step is a StepExprP starting from posture grounded/striding/crawling,
and if the whole expression is roaming, then the result-posture is crawling.
</DEF>

Such a definition would have the benefit of applying to many common situations
currently incorrectly forbidden (I think), without requiring the expression to
also be a rootless path, and hopefully removing the present ambiguities.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 9 March 2017 14:20:11 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 March 2017 14:20:11 UTC