- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 19 Dec 2005 19:29:47 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2610
Summary: Is an invalid character reference a parse error?
Product: XPath / XQuery / XSLT
Version: Working drafts
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: normal
Priority: P2
Component: XQuery
AssignedTo: chamberl@almaden.ibm.com
ReportedBy: abehm@ca.ibm.com
QAContact: public-qt-comments@w3.org
In the XML Query Test Task Force we are not sure wether the following query
should be a parser error or some other static error:
<new>�</new>
The following rule in the grammer applies:
[153] CharRef ::= [http://www.w3.org/TR/REC-xml#NT-CharRef]
The XML standard refers to character references as:
[66] CharRef ::= '&#' [0-9]+ ';'
| '&#x' [0-9a-fA-F]+ ';'
and in a side note restricts the value set:
"Characters referred to using character references MUST match the production for
Char."
and "Char" excludes certain values:
[2] Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] |
[#x10000-#x10FFFF]
The question for XQuery is: does the side note restricting range for character
references in the XML standard propagate into a parse error in XQuery, or does
there need to be a seperate error defined for this scenario.
Test case Constr-cont-charref-2 applies.
Received on Monday, 19 December 2005 19:29:49 UTC