W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20645] [QT3TS] parse-xml-010

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Jan 2013 16:06:16 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20645-523-5dfKeBKjnz@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20645

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |mike@saxonica.com
           Assignee|oneil@saxonica.com          |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
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().

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 11 January 2013 16:06:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 January 2013 16:06:18 GMT