RE: XSL and Namespace

I think this is another case where the spec needs clarification; both
behaviors can be justified.

In particular, it is not clear which of the following two statements is
intended to override the other:

(a) (2.6.1) The xsl:import element children must precede all other element
children
of an xsl:stylesheet element.

(b) (2.2) An XSLT processor must ignore a top-level element without giving
an error
if it does not recognize the namespace URI.

I will register this as an issue needing clarification by posting it on
xsl-editors@xxxxxxx

Mike Kay

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Perry
> Molendijk
> Sent: 28 May 2001 14:25
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  XSL and Namespace
>
>
> 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?
>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:fo="http://www.w3.org/1999/XSL/Format"
> xmlns:fox="http://xml.apache.org/fop/extensions"
> xmlns:documentation="http://sealcorp.com.au/documentation">
>
>     <documentation:file-title number-tags="0"
> class="title">report_logic.xsl</documentation:file-title>
>
>     <documentation:file-description name="report_logic.xsl"
> number-tags="0"
> class="fileDescription">Report_logic.xsl is the central axis
> between general
> layout     and actual styling of the report. It reads
> report_layout.xml and
> calls templates from report_xsl.xsl.</documentation:file-description>
>
>     <documentation:comment number-tags="2" class="nodeDescription">
>
>         The following nodes import the files with the main XSL display
> rules, report_xsl.xsl is for the actual pdf report,
> report_outline.xsl is
> for the pdf outline you         can see in the right hand nav
> bar of Adobe
> Acrobat Reader.
>
>     </documentation:comment>
>
> <xsl:import href="report_xsl.xsl"/>
>
> <xsl:import href="report_outline_xsl.xsl"/>
>
> ... rest of xsl...
>
> I tend to use a couple of processors to check the validity of
> my XSLs and
> this one has thrown me. Can anyone tell me if my XSL is wrong
> and therefor
> Xalan and MSXML too or Saxon makes the error or perhaps an
> other explanation
> all together.
>
> Perry Molendijk
>
>
> Inflexions (WA) Pty Ltd
> PO Box 57
> Inglewood WA 6052
> Australiat: +61 08 9271 8552
> m: 0401 677 453
> e: perry@xxxxxxxxxxxxxx
>
>
> This message and any files transmitted with it are
> confidential and should
> be read only by those persons to whom it is addressed. If you
> have received
> this message in error, please notify us immediately by way of
> reply. Please
> also destroy and delete the message from your computer. Any
> unauthorised
> form of reproduction of this message is strictly prohibited.
> It is the duty of the recipient to virus scan and otherwise test the
> information provided before loading onto any computer system.
> Inflexions
> (WA) Pty Ltd does not warrant that the information is free of
> a virus or any
> other defect or error.
> Inflexions (WA) Pty Ltd is not liable for the proper and complete
> transmission of the information contained in this
> communication, nor for any
> delay in its receipt.
> Any views expressed in this message are those of the
> individual sender,
> except where the sender specifically states them to be the views of
> Inflexions (WA) Pty Ltd.
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list