W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2015

[Bug 28775] [XSLT30] Suggestion: prioritise templates with named modes over templates with mode="#all"

From: <bugzilla@jessica.w3.org>
Date: Sun, 07 Jun 2015 08:34:39 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28775-523-v4DpDaS9nY@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28775

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Personal response (and/or request for clarification):

In your example, 

match="text()[contains(., 'x')]"

(with no priority attribute)

would have higher priority than

match="node()|@*"

Even without the predicate a text node would match match="text()" in preference
to match="node()".

So I'm not sure the example justifies the proposal.

I can see the logic that mode="#all" is intuitively some kind of fallback and
should therefore rank lower, but it's not clear how this would fit into the
priority/precedence rules, and it's not clear that it could be made backwards
compatible. Even if we only took the mode attribute into account when the two
rules have the same precedence/priority, XSLT 2.0 processors are entitled to
resolve the ambiguity by choosing the rule that comes last, and a stylesheet
that relied on this behaviour would need to be changed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 7 June 2015 08:34:44 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 7 June 2015 08:34:44 UTC