This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XSL and Namespace
- To: "Perry Molendijk" <perry at inflexions dot com>
- Subject: Re: [xsl] XSL and Namespace
- From: Jeni Tennison <mail at jenitennison dot com>
- Date: Mon, 28 May 2001 21:21:01 +0100
- CC: xsl-list at lists dot mulberrytech dot com
- Organization: Jeni Tennison Consulting Ltd
- References: <008401c0e779$927f4fd0$8cad3bcb@inflexions>
- Reply-To: xsl-list at lists dot mulberrytech dot com
Hi Perry,
> I am using a namespace called "documentation" in my XSL which I process with
> its own XSL to produce html documentation for the XSL file. The following
> code snippet causes an error when using Saxon (both Instant and 6.1),
> telling me that the import tags need to be the first tags after the
> xsl:stylesheet element, however Xalan and MSXML 3 process without error. The
> spec says <xsl:import> has to be the first element but does it have to be
> the first element of all namespaces?
The XSLT Recommendation says:
"The xsl:import element children must precede all other element
children of an xsl:stylesheet element, including any xsl:include
element children."
It doesn't predicate the 'element children' of the xsl:stylesheet
element as being 'XSLT element children' or 'element children in the
XSLT namespace'. So, strictly, you can't have any other element
children, no matter what namespace, before xsl:import elements.
Cheers,
Jeni
---
Jeni Tennison
http://www.jenitennison.com/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list