[Bug 18907] New: Decode URIs

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18907

           Summary: Decode URIs
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.0
        AssignedTo: mike@saxonica.com
        ReportedBy: hannesbauer@yahoo.com
         QAContact: public-qt-comments@w3.org


Wouldn't it be helpful, and symmetric, to have an function in the specification
for decoding URIs?

  fn:decode-uri($uri-part as xs:string?) as xs:string

I have seen that existing XQuery implementations already provide something
equivalent:

  http://exist-db.org/exist/functions/xmldb/decode-uri
  http://www.zorba-xquery.com/html/modules/zorba/xdm/atomic/uri

Decoding a URI via plain XQuery feels like a pretty tedious job, and I think it
shouldn't be too hard to add the functionality to others implementations, so
I'm wondering why this function hasn't made it to the standard yet.

I have just found two discussions that also seem to focus on this issue..

 
http://markmail.org/thread/knd246eiayderbd6#query:+page:1+mid:knd246eiayderbd6+state:results
 
http://markmail.org/thread/nt3hjtdizvz2ltvx#query:+page:1+mid:nt3hjtdizvz2ltvx+state:results

..but the argument "difficulty in the detail of specifying it", as Michael Kay
put it, didn't really convince me, because functions like format-date() appear
much more sophisticated to me. Regarding the use cases, I have one for myself,
and the existing implementations and discussions seem to prove that there is
some need.

Sorry for bothering, thanks for reading,
Hannes

-- 
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 Tuesday, 18 September 2012 12:15:56 UTC