24540 2014-02-05 22:55:10 +0000 Definition for predicate pattern and path patterns 2014-02-24 12:52:47 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC Windows NT CLOSED FIXED P2 minor --- 1 abel.braaksma mike cmsmcq public-qt-comments oldest_to_newest 99844 0 abel.braaksma 2014-02-05 22:55:10 +0000 The introduction of predicate patterns is quite a major one, I think it is worthwhile to use a specific definition for this term. Same applies to its counterpart, path patterns. I know we don't want to define every single term we use, but this one is quite important for understanding patterns. In addition, I thought we once said that .[1] (or any numeric in a predicate pattern) is always true and .[0] is always false, but I couldn't find it, did that decision make it to the spec? 100382 1 cmsmcq 2014-02-12 10:20:50 +0000 The WG discussed this during the ftf meeting in Prague and concluded that the issue should be left to the discretion of the editor. There was some support for the view that definitions of 'predicate pattern' and 'path pattern' as terms would be helpful, even though (as was pointed out) they do not partition the set of all patterns between them. 101232 2 mike 2014-02-24 12:51:24 +0000 I have introduced "predicate pattern" and "selection pattern" as defined terms for the two kinds of pattern; these now partition the space. Concerning the last para of the bug report, the note in 5.6.3 has this information: "A predicate with the numeric value 1 (one) always matches, and a predicate with any other numeric value never matches. Numeric predicates in a PredicatePattern are therefore not useful, but are defined this way in the interests of consistency with XPath."