- From: Michael Kay <mike@saxonica.com>
- Date: Wed, 13 Mar 2024 21:50:00 +0000
- To: Dimitre Novatchev <dnovatchev@gmail.com>
- Cc: Norm Tovey-Walsh <norm@saxonica.com>, "public-xslt-40@w3.org" <public-xslt-40@w3.org>
> I redefined the solution for producing all needed sort-keys with a single key() function as shown below. > The reason for having multiple sort key definitions is that you typically want to apply different criteria to each one - ascending/descending, collations, etc. The lack of support for descending keys in the 3.1 version of fn:sort was a big gap, we don't want to repeat it. For numeric keys there is an easy workaround by negating the value, but there is no easy workaround for strings. I basically can't see any reason for making fn:ranks different from fn:sort in areas where they are doing the same thing, other than the fact that you don't like the design, and I don't think that's a good enough reason. If someone drives two cars, they want the pedals on both to be in the same place, rather than having every designer do their own thing. Michael Kay Saxonica
Received on Wednesday, 13 March 2024 21:50:17 UTC