- From: <bugzilla@jessica.w3.org>
- Date: Tue, 01 Mar 2016 21:21:33 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29501 --- Comment #6 from Michael Kay <mike@saxonica.com> --- I agree that if these three expressions are allowed, then they should have the meanings described. I was very surprised by the discovery that the "longest token" rule currently leads to *:a:b parsing as * : a:b But I think my preference is probably to impose restrictions requiring the use of whitespace - I think that reduces the risk of users writing something they didn't intend. Again, I'm not sure exactly what the rule should be. Part of it is probably that (like "-" and ".") ":" as a token is not allowed immediately after an NCName (including an NCName that is part of a QName). That leaves questions about ":" after "*". We might find that the grammar works better if we define wildcards using composite tokens "*:" and ":*", or even if we make wildcards (like QNames) into single tokens. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 1 March 2016 21:21:38 UTC