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

[Bug 30013] New: [XSLT30] (editorial) Unclear or inverse Note in definition of non-positional predicates

From: <bugzilla@jessica.w3.org>
Date: Sat, 19 Nov 2016 00:46:41 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30013-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30013

            Bug ID: 30013
           Summary: [XSLT30] (editorial) Unclear or inverse Note in
                    definition of non-positional predicates
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: editorial
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

We say under non-positional predicates (section 19.8.10 Classifying Patterns):

"The exception for nested predicates is to avoid disqualifying patterns such as
match="p[@code = $status[last()]]"."

But the pattern "p[@code = $status[last()]]" is not a disqualifying pattern, it
is allowed and considered a non-positional pattern, and I think we explicitly
allow it.

Perhaps we meant to say:

"The exception for nested predicates is to allow patterns such as
match="p[@code = $status[last()]]", which are motionless [since they do not
need to retain positional information of the streamed node]."

(the added "[since....]" is just a suggestion)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 19 November 2016 00:46:47 UTC

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