This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: The XSL-List Digest V3 #2
- To: xsl-list at mulberrytech dot com
- Subject: Re: The XSL-List Digest V3 #2
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Wed, 3 May 2000 18:06:41 +0100 (BST)
- References: <200005031544.LAA10142@mulberrytech.com> <00f501bfb51f$25e261b0$7300000a@delllapnt>
- Reply-To: xsl-list at mulberrytech dot com
I would like to put an AVT inside an xsl:include as follows:
well you can't. tough:-)
<xsl:include href="{/DOC/AN_URL}"/>
The href attribute is being interpreted literally with my XSL processor
(XT). Should it be replacing the AVT value? The spec says the href must be
a uri-reference but I cannot find where a 'uri-reference' is defined or a
statement in the spec saying a 'uri-reference' can or cannot have AVTs.
The spec always says explictly, for each attribute, whether or not the
attribute takes an AVT, and this one doesn't (if it did, the effective
stylesheet would depend the data, which generally isn't supported in
xsl)
a URI reference is the bizarre terminology that means a string
that consists of a URI + # + a local fragment identifier.
So in particular it does not mean a reference to a URI which is what you
might expect it to mean.
the term comes from the RFC that defines URIs, referenced in xslt spec
as
RFC2396
T. Berners-Lee, R. Fielding, and L. Masinter. Uniform Resource
Identifiers (URI): Generic
Syntax. IETF RFC 2396. See http://www.ietf.org/rfc/rfc2396.txt.
which says:
URI-reference = [ absoluteURI | relativeURI ] [ "#" fragment ]
David
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list