- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 24 Feb 2014 10:22:43 -0800
- To: "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>
- Cc: www-svg <www-svg@w3.org>, "bugzilla@jessica.w3.org" <bugzilla@jessica.w3.org>, jcgregorio@google.com
On Sat, Feb 22, 2014 at 6:25 AM, Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de> wrote: > I'm no expert in BNF notations, but the '|' obviously means only 'or' > and 'a or b' or 'b or a' is equivalent. Per meaning of 'or' the order in > such a list implies never an order of importance or relevance or preference. > Because many W3C recommendations (for example) CSS use > a similar syntax of '|' without implying an order, all these should > be in trouble, in case the bug applies. CSS 2.1 defined that longest-match semantics apply in its parsing rules, so it was always unambiguous. Individual CSS properties are either never ambiguous, or use prose to manually disambiguate. ~TJ
Received on Monday, 24 February 2014 18:23:30 UTC