W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2012

[Bug 18907] [XQ31ReqUC] Decode URIs

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Oct 2012 20:58:57 +0000
Message-Id: <E1TIn4r-0007o4-19@jessica.w3.org>
To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18907

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> 2012-10-01 20:58:56 UTC ---
The WG looked at this last week. There is some sympathy with the requirement,
but we're at a stage of development where all requests for new features are
being parked in a shopping list for a post-3.0 release, currently labelled 3.1. 

On the substance, I do know that it isn't going to be easy - the current batch
of functions, iri-to-uri, encode-for-uri, and escape-html-uri - went through
many iterations before we got them right, and accounted for well more than
their fair share of comments and bugs. Even their names reflect the tortuous
process we went through. We will have many questions to consider, for example
what to do when % is not followed by two hex digits, and what to do when
encoded URIs contain percent-escaped characters such as "/", where putting the
"/" into the decoded value is unlikely to yield a string that serves any useful
purpose. I think it's because these questions looked difficult that the
function was not present in 2.0.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 1 October 2012 20:58:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 1 October 2012 20:58:58 GMT