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

[Bug 25327] Typo in 'sum(a/b/c)' general streamability example

From: <bugzilla@jessica.w3.org>
Date: Thu, 17 Jul 2014 15:27:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-25327-523-FKWwJ8LU9W@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25327

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abel.braaksma@xs4all.nl

--- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Some examples as requested by Eugene:

- zero-or-one(div//p) has OU of transmission and its argument, div//p has
posture crawling, sweep of consuming. The result of the analysis following the
GSR makes this consuming and striding (rule 2.d.iii).

- fn:tail(head//section) has OU of transmission and its argument,
head//section, is crawling and consuming. The result of the analysis following
the GSR makes this crawling and consuming (rule 2.d.iv).

- exactly-one(div | p) has OU of transmission and its argument, div | p, is
crawling and consuming. The result of the analysis following the GSR makes this
striding and consuming (rule 2.d.iii).

- fn:unordered(head | section) has OU of transmission and its argument, head |
section, is crawling and consuming. The result of the analysis following the
GSR makes this crawling and consuming (rule 2.d.iv).

In fact, I am unsure whether the rules for fn:tail correctly make it crawling
and consuming, I tend to think it should be free-ranging. For fn:unordered it
does not seem to matter.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 17 July 2014 15:27:16 UTC

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