RE: Re: Re: An issue with XPath 2.0 sequences (Was Re:

> Also as Jeni pointed out the weird case of sequences changing their
> cardinality when mapped by a function that may return the null
> sequence...

Or when mapped by any other function that doesn't preserve the cardinality
of its input. A function that returns two items for every supplied item
works in exactly the same way as a function that returns zero items for
every supplied item: at least it's consistent! And it's also consistent with
the behaviour of the "/" operator in path expressions, which I haven't heard
anyone complain about.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list