Jeni Tennison wrote:
In other words, you can do things like:
keyword/lower-case(.)
*big sigh of happiness*
but you can't do:
keyword/lower-case(.)/substring-before(., '-')
Pity.
I've been using a programming language in which atomic values could be part of a node-set as well.
Works really nice sometimes. The syntax is almost similar to XPath, but the / is replaced by .
(period) and is called a 'replacement operator'. It substitutes each value of the node set that
resulted from the previous steps by the values (or nodes) from the following step. The result of
each step is flattened to one list, though the evaluation order is still depth first unless braces
are used...
descendant[?noteref].getindex(@id).($note := this).(<|ref, @id:=$note(_dot_)(_at_)id|> node, <|footnote
id:=$note(_dot_)(_at_)id |> node { $node.contents})
And this can be continued endlessly...
(Does this look familiar to anyone? ;-)
Grtz,
Geert
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--