This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XPointer support in document() ?
Yes, I'm thinking about the design of a generic XSLT template that takes an
href attribute, checks for the presence of a "#" fragment, then dissects the
URI into to pieces and calls both document()and saxon:evaluate(). If I get
something working, I'll post it.
BTW, XPointer moved to candidate recommendation this week, so it may be time
to begin experimentation with its integration into Saxon.
Dave Carlson
----- Original Message -----
From: Kay Michael <Michael.Kay@icl.com>
To: <xsl-list@mulberrytech.com>
Sent: Friday, June 09, 2000 3:11 AM
Subject: RE: XPointer support in document() ?
> Have any of the XSLT processors implemented a tentative support for
> XPointer in the document() function? Or, do they minimally
> support an ID fragment?
Saxon doesn't (yet): I wanted to wait for XPointer to stabilise.
It's interesting to note that document() using a fragment identifier gives
you, in a rather roundabout way, the capability of saxon:evaluate(): that
is, the ability to locate nodes using an XPath expression constructed at
run-time or stored in the source document.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list