This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: mapping (Was: Re: Re: . in for)
- From: Joerg Pietschmann <joerg dot pietschmann at zkb dot ch>
- To: XSL List <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 09 Jan 2002 14:07:02 +0100
- Subject: RE: mapping (Was: Re: [xsl] Re: . in for)
- Organization: ZKB
- Reply-to: xsl-list at lists dot mulberrytech dot com
DPawson@rnib.org.uk wrote:
> Yes, I suppose to follow a standard function form it should be
> select ='map (lower-case(), $departments)'.
Is there a reason why we can't identify and pass functions by their
QName? We could then write select ='map(xf:lower-case, $departments)'.
This would circumvent the lexical problems. Probably this avoids
having functions as data type in the data model, although their
QNames de facto are used as such.
> I'm sure David C or Dimitre could extend this to a piped form?
> Guessing,
> select='map (fnA(), (map (fnb(), $departments)))'
If Jeni's proposal for having XSLT functions constructing sequences
is accepted, this should be perfectly possible. I'd omit unnecessary
spaces and parenthesis:
select='map(fnA(), map(fnb(), $departments))'
or
select='map(my:fnA, map(my:fnb, $departments))'
Regards
J.Pietschmann
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list