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

[Bug 22767] Default priority calculation for parenthesized patterns

From: <bugzilla@jessica.w3.org>
Date: Tue, 23 Jul 2013 13:29:37 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-22767-523-O9OIb4v29S@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22767

--- Comment #2 from Vitaliy <vyudenkov@hotmail.com> ---
(In reply to comment #1)
> Your understanding of the current specification is correct.
> 
> Basing the default priority on the syntactic form of the pattern has always
> had the potential to create anomalies, for example many people are caught
> out that match="//a" has a different priority to match="a". We have to find
> a compromise between keeping the rules simple and easy to explain, and
> giving intuitive results for people who do not know the rules.
> 
> It would certainly be possible to have a rule that redundant outer
> parentheses are stripped before applying the other rules.

Thank you, for response.

Yes, probably a good solution just to remove unnecessary parentheses before
default priority calculation.

Could be the pattern EBNF be simplified as following:

    Pattern30            ::= ParenthesizedPattern | Pattern

    Pattern              ::= PatternTerm ( ('|' | 'union') PatternTerm )*

    ParenthesizedPattern ::= '(' Pattern ')' 

    QualifiedPattern     ::= ParenthesizedPattern PredicateList

Thank you, 
Vitaliy

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 23 July 2013 13:29:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:53 UTC