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

[Bug 29983] [XSLT30] Scanning expressions and function calls

From: <bugzilla@jessica.w3.org>
Date: Thu, 12 Jan 2017 22:57:17 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29983-523-PhXHBMIwQX@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29983

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #13 from Michael Kay <mike@saxonica.com> ---
The proposal in comment #9 was accepted.

In implementing the proposal, I realized that the definition of "equivalent
expression" is not quite right, because the equivalent expression of the
pattern "section//head" is not "section//head", but
"child-or-top::section//head", and "section//head" is therefore not the
equivalent expression of any pattern.

So I reformulated the rule as:

<p><termdef id="dt-scanning-expression" term="scanning expression">A 
<code>RelativePathExpr</code> is a <term>scanning expression</term> if and only
if it is syntactically equivalent to some <termref def="dt-motionless"/>
<termref def="dt-pattern"/>.</termdef></p>

followed by a note explaining what "syntactic equivalence" means.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 12 January 2017 22:57:25 UTC

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