- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 04 Nov 2005 16:54:36 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2462
Summary: [XQuery] Escaping URILiterals
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: XQuery
AssignedTo: chamberl@almaden.ibm.com
ReportedBy: mike@saxonica.com
QAContact: public-qt-comments@w3.org
Section 2.4.5, URILiterals, says:
"...however, no escaping normalization is applied."
It's not obvious to me what "escaping normalization" is but I suspect it's
something to do with representing special characters as %HH (an operation we
are now required to call encoding rather than escaping, for reasons that,
er, elude me).
I think that the above phrase has nothing to do with ampersand-escaping.
Specifically, I think that an ampersand in a URILiteral must be written as
& just as an ampersand in a string literal is written.
It might be useful (after CR, I guess) to add some clarification here.
Michael Kay
previously raised at
http://lists.w3.org/Archives/Member/w3c-xml-query-wg/2005Oct/0006.html
Received on Friday, 4 November 2005 16:54:39 UTC