RE: xslt 11.6

Let me try again.
11.6, the example, shows xsl:namespace as a standalone,
possibly a top level element, same status as xsl:variable.

As we appear to agree,  it must (somehow)
be wrapped in an element, literal or xsl:element.

The example, on that basis, is unclear, as an example.
Your use of a called template is noted, hence my phrasing was wrong.

2.
quote.Note the restrictions described in 5.6.1 Constructing Complex Content
for the position of a namespace node relative to other nodes in the node
sequence returned by a sequence constructor. unquote.

The list at 5.6.1 reads, to me, as quite unconnected with the position of a
ns node,
simply noting what happens when two with same name are used.

regards DaveP





> > Has an xsl:namespace example.
> > 
> > the reference to 5.6.1 implies its use is discussed.
> > If saxon 7.5.1 implements it correctly, there is an 
> > implication that it must be the child of an lre or an xsl:element.
> > 
> > Appears not to be stated.
> 
> No, there is no restriction that an xsl:namespace element 
> must be a child of
> an xsl:element or literal result element. For example, it's 
> perfectly OK to
> do
> 
> <lre>
>   <xsl:call-template name="x"/>
> </lre>
> 
> <xsl:template name="x">
>   <xsl:namespace name="prefix">uri</xsl:namespace>
> </xsl:template>
> 
> In fact, the rules are almost exactly the same as for xsl:attribute.
> 
> What 5.6.1 says is that you'll get an error if you do:
> 
> <lre>
>   <xsl:call-template name="x"/>
> </lre>
> 
> <xsl:template name="x">
>   <child/>
>   <xsl:namespace name="prefix">uri</xsl:namespace>
> </xsl:template>
> 
> It's entirely possible that Saxon doesn't implement the rules 
> correctly, if
> you have evidence of this, please submit it on the Saxon list.
> 
> Michael Kay
> 

- 

NOTICE: The information contained in this email and any attachments is 
confidential and may be legally privileged. If you are not the 
intended recipient you are hereby notified that you must not use, 
disclose, distribute, copy, print or rely on this email's content. If 
you are not the intended recipient, please notify the sender 
immediately and then delete the email and any attachments from your 
system.

RNIB has made strenuous efforts to ensure that emails and any 
attachments generated by its staff are free from viruses. However, it 
cannot accept any responsibility for any viruses which are 
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk

Received on Monday, 16 June 2003 03:49:23 UTC