- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 28 Mar 2006 09:59:07 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3055
Summary: [F+O] How does iri-to-uri() handle an invalid IRI?
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Functions and Operators
AssignedTo: ashok.malhotra@oracle.com
ReportedBy: mike@saxonica.com
QAContact: public-qt-comments@w3.org
The new rules for iri-to-uri() agreed in
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2457
do not say how an invalid IRI should be handled: for example, a string that is
not a valid IRI because it contains a space character.
There are two options: we define a new error code, or we say that invalid
characters should be %HH-encoded.
Because it is common practice to use a space in a URI with the expectation that
it will be encoded as %20, I suggest that we use the latter approach.
Received on Tuesday, 28 March 2006 09:59:41 UTC