W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2011

[Bug 13187] New: map in xquery/xpath

From: <bugzilla@jessica.w3.org>
Date: Sat, 09 Jul 2011 19:05:53 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-13187-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13187

           Summary: map in xquery/xpath
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Requirements for Future Versions
        AssignedTo: jim.melton@acm.org
        ReportedBy: jim.fuller@webcomposite.com
         QAContact: public-qt-comments@w3.org


I could not find a place where to register my desire for map:map in
xquery/xpath so I entered here ... apologies if this is a dupe, etc.

I have been using Saxon and MarkLogic implementation of map:map for the past
few months and am convinced of its usefulness.

some adhoc usage scenarios;

controller: keeping routing in memory makes things zippy, and a very common map
for me nowadays is one where the keys are uri's and values whatever I need
(think url rewriting) or even functions to be passed ala HOX (higher order
xquery) 


memoize: maps makes it easy to provide inline func caching ala

https://gist.github.com/954816

working with json: maps make life a bit easier in this respect

there are more ....

-- 
Configure bugmail: http://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 Saturday, 9 July 2011 19:05:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:13 GMT