- From: Innovimax W3C <innovimax+w3c@gmail.com>
- Date: Thu, 18 Nov 2010 23:28:12 +0100
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: public-xml-processing-model-wg@w3.org
I just send on xproc-dev an implementation of sort You can find a blog post on that [1] It might be inefficient, but it surely work (in the case of OAuth you don't have thousands of thing to sort, so it will wokr as is) [1] http://xmltoday.org/2010/11/power-of-xproc-straight-to-quicksort/ Mohamed On Thu, Nov 18, 2010 at 7:48 PM, Norman Walsh <ndw@nwalsh.com> wrote: > Any other business? > > Vojtech: I was wondering if having a p:sort would add any value. > ... something like split-sequence that takes an XPath expression to use > for ordering the documents. > > Norm: I'm not opposed. I never even thought of doing it. > > Vojtech: Maybe it's better to put something like this in EXProc. > > Norm: Yeah, we can leave it there and see if we get requests for a better > job. > > Vojtech: My concern is that it might not be sufficient for more complex > use cases. > ... if the sort criteria are not easy to express in an XPath expression, > for example. > > Alex: I'm just not sure what the use cases are. > > Vojtech: The use case that I had was that I was trying to implement OAuth > and you have to sort the request parameters before you hash them. > ... For that I needed a sort. It was simple string sort so you could do > that with XSLT or XQuery. -- Innovimax SARL Consulting, Training & XML Development 9, impasse des Orteaux 75020 Paris Tel : +33 9 52 475787 Fax : +33 1 4356 1746 http://www.innovimax.fr RCS Paris 488.018.631 SARL au capital de 10.000 €
Received on Thursday, 18 November 2010 22:28:45 UTC