5351 2008-01-08 18:29:25 +0000 [XPath] PI name test must require string literals that satisfy NCName rules 2009-02-23 19:12:52 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XPath 2.0 Recommendation All All RESOLVED DUPLICATE 6559 P2 normal --- 1 jim.melton chamberl andrew.eisenberg jonathan.robie tim public-qt-comments oldest_to_newest 18245 0 jim.melton 2008-01-08 18:29:25 +0000 Bug 5269 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=5269) reported the fact that the name test processing-instruction("123ncname") is a syntactically-valid XPath (and XQuery) expression, even though the string literal "123ncname" cannot be transformed into a valid PITarget (which must be an NCName). We've closed Bug 5269 because it was reported as an XQueryX problem, which it is not. This bug was opened to capture the problem for XPath. 18246 1 jim.melton 2008-01-08 18:30:38 +0000 The name test shown in this bug report will always result in a dynamic error. In its teleconference on 2008-01-08, the WG decided (because the error, caused by a string literal, can be caught statically) to make it a type error (XPTY0004) if the string literal of a PI name test cannot be converted to an NCName. 18255 2 mike 2008-01-08 21:59:23 +0000 Just a reminder that whoever drafts the erratum on this should add an entry to the XPath 1.0 backwards compatibility appendix. In XPath 1.0, (and in XPath 2.0 until today), processing-instruction('123abc'), like @comment(), was a legitimate if perverse way of denoting the empty node-set. 18484 3 jim.melton 2008-01-23 15:26:06 +0000 *** Bug 5355 has been marked as a duplicate of this bug. *** 22553 4 tim 2008-11-28 09:48:38 +0000 To resolve Bug 6238, could you please clarify whether "...PI name test cannot be converted to an NCName." means that processing-instruction("b ") raises XPTY0004, or is equivalent to processing-instruction("b") because "b " can be converted to an NCName using xs:NCName("b "). 23886 5 jonathan.robie 2009-02-23 19:12:52 +0000 *** This bug has been marked as a duplicate of bug 6559 ***