There are two issues with this function: 1. The description is confusing: “This function takes a sequence, or more typically, an expression, that evaluates to a sequence, as input .” Is “an expression, that evaluates to a sequence” a separate datatype in Xpath/Xquery 2.0? This phrase is not necessary, confusing and has to be removed. All other functions "take an expression" that evaluates to the necessary argument types -- we know this and don't need to be told this just for one specific function. 2. There isn't a meningful example to demonstrates the usefulness of this function. The explanation given does not tell the reader when and why to use the function: "Query optimizers may be able to do a better job if the order of the output sequence is not specified. For example, if you want to retrieve all the prices from a purchase order, and if there is an index on prices, it may be possible to compute an unordered result more efficiently." This tells the reader why he/she may receive unordered sequence as result, not why and when he/she should use fn:unordered() to provide an unordered sequence to other functions. Dimitre Novatchev. __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/Received on Saturday, 22 November 2003 09:19:02 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:03 GMT