20645 2013-01-11 15:38:00 +0000 [QT3TS] parse-xml-010 2013-01-11 18:04:22 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Working drafts PC Windows NT RESOLVED FIXED P2 normal --- 1 tim mike mike public-qt-comments oldest_to_newest 81240 0 tim 2013-01-11 15:38:00 +0000 I think the test should be <test><![CDATA[parse-xml("<!DOCTYPE a [<!ELEMENT a (#PCDATA)><!ENTITY foo SYSTEM 'parse-xml/foo.entity'>]><a>&foo;</a>")]]></test> in <test-case name="parse-xml-010"> <description>parse-xml test - with external entity</description> <created by="Michael Kay" on="2013-01-07"/> <environment name="empty"/> <test><![CDATA[parse-xml("<!DOCTYPE a [<!ELEMENT a (#PCDATA)><!ENTITY foo SYSTEM 'parse-xml/foo.entity'>]><a>&amp;foo;</a>")]]></test> <result> <assert-xml><![CDATA[<a><bar>baz</bar></a>]]></assert-xml> </result> </test-case> to match the intent of the test. 81245 1 mike 2013-01-11 16:06:16 +0000 I think it depends on whether you run it using an XPath processor or an XQuery processor. The expression is this: parse-xml("<!DOCTYPE a [<!ELEMENT a (#PCDATA)><!ENTITY foo SYSTEM 'parse-xml/foo.entity'>]><a>&amp;foo;</a>") In XQuery, the query processor interprets "&amp;" in the string literal as &, so it passes &foo; to the XML parser. In XPath, the xpath processor does nothing to the string, so it passes "&amp;foo;" to the XML parser. Do you agree with that analysis? If so, it looks like we need to split it into different tests for XPath and XQuery. Alternatively, we can construct the XML string using string concatenation and codepoints-to-string(). 81250 2 tim 2013-01-11 16:44:49 +0000 > Do you agree with that analysis? Yes. I hadn't spotted that it was only failing for XP30 runs, and not XQ30. 81262 3 mike 2013-01-11 18:04:22 +0000 Fixed by using codepoint-to-string() for the ampersand.