3606 2006-08-17 09:12:55 +0000 [XPath] delimiting tokens 2007-02-25 23:47:01 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XPath 2.0 Candidate Recommendation PC Windows XP CLOSED FIXED P2 normal --- 3765 1 mike chamberl public-qt-comments oldest_to_newest 11192 0 mike 2006-08-17 09:12:55 +0000 For unrelated reasons, I was looking at test LocalNameFromQNameFunc018, which contains the line: declare default element namespace"http://www.example.com/QNameXSD"; This test is intended to succeed, and Saxon parses it successfully; but looking at the spec, it seems this isn't allowed. A2.2 (in XQuery) says: (a) The non-delimiting terminal symbols are: ... namespace, ... StringLiteral, ... (b) It is customary to separate consecutive terminal symbols by whitespace and Comments, but this is required only when otherwise two non-delimiting symbols would be adjacent to each other. Is there any good reason why StringLiteral is classified as a non-delimiting symbol? Am I correct in saying that as the spec stands, the above line should be a syntax error? There are other oddities in the list of non-delimiting symbols as well. For example, it includes Char. This suggests that in the production rule [159] CommentContents ::= (Char+ - (Char* ('(:' | ':)') Char*)) the Char tokens must be separated by whitespace, whereas of course the opposite is true. I think that symbols that are used only in ws:explicit rules have no place in this list. Also, the statement "There are two exceptions to this, that of "." and "-", which do require a symbol separator if they follow a QName or NCName" isn't quite complete: "." also requires a separator if it precedes or follows a numeric literal. I encountered this in XQuery, but it applies in principle to XPath also. 11276 1 scott_boag 2006-08-25 15:38:02 +0000 > Is there any good reason why StringLiteral is classified as a non-delimiting > symbol? Not that I can see. In fact, I think it's contradicts """ and "'" being delimiting characters. So, yes, I think this is a bug and should be fixed. > Am I correct in saying that as the spec stands, the above line should be a > syntax error? I would let it pass, given my statement above that there is a contradiction. >> There are other oddities in the list of non-delimiting symbols as well. For >> example, it includes Char. This suggests that in the production rule >> >> [159] CommentContents ::= (Char+ - (Char* ('(:' >| >> ':)') Char*)) >> >> the Char tokens must be separated by whitespace, whereas of course the >>opposite >> is true. I think that symbols that are used only in ws:explicit rules have no >> place in this list. I agree. >> "." also requires a separator if it precedes or follows a >> numeric literal. I agree. 11283 2 scott_boag 2006-08-25 18:49:37 +0000 Resolution accepted by WG. 14153 3 jim.melton 2007-02-25 23:47:01 +0000 Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.