- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 09 Jul 2005 05:28:04 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1383 ------- Additional Comments From scott_boag@us.ibm.com 2005-07-09 05:28 ------- (In reply to comment #0) > A.2 Lexical structure > > [See a later comment for suggested alternate wording.] > > Thanks for excising the state machine! You're wellcome. You were right that it needed to be excised. > > "and [XML Names]are" > Insert space before "are". Done. > > "When patterns are simple string matches, the strings are embedded directly into > the EBNF. In other cases, named terminals are used." > Delete. It doesn't say anything that isn't already said better in the EBNF > notation section. Plus it isn't connected to anything else in the section. Deleted. > > "that together may help disambiguate the individual symbols." > Ditto my comments re this sentence in A.1. Fixed. > > "When tokenizing, the longest possible match that is valid in the current > context is preferred ." > Delete space before period. Fixed. > > What constitutes "the current context"? What constitutes "valid"? Longest > match of what? Given that tokenization is up to the implementor, it seems > that the effect of this sentence would vary between implementations, which > is probably not what you want. > > Luckily, I think this rule can be deleted. The rules about required > whitespace (to prevent two adjacent terminals from being mis-recognized as > one) should (if fixed) handle anything that the "longest possible match" > would have. I'm not inclined to delete this, at least at this time. I think the rule is clear enough, and longstanding. This should be discussed at the Seattle F2F, especially against the light of other changes or non-changes.
Received on Saturday, 9 July 2005 05:28:06 UTC