- From: Kay, Michael <Michael.Kay@softwareag.com>
- Date: Mon, 16 Jun 2003 21:58:08 +0200
- To: David.Pawson@rnib.org.uk, public-qt-comments@w3.org
> 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 specification makes it clear that xsl:namespace is an instruction, therefore it must appear in places where instructions are allowed. > > The example, on that basis, is unclear, as an example. > Your use of a called template is noted, hence my phrasing was wrong. I agree that an example that shows the use of this instruction in-context might be more helpful. > > 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. > List item 4 in section 5.6.1 is concerned with the order of nodes: >>>It is a dynamic error if the result sequence used to construct the content of an element node contains a namespace node or attribute node that is preceded in the sequence by a node that is neither a namespace node nor an attribute node. This is a recoverable error... Michael Kay
Received on Monday, 16 June 2003 16:01:38 UTC