This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Namespace incompatibility b/n XPath 2.0 Data Model and XPath 1.0 (Was Re: XML schema general convert with XSLT (namespaces..))
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] Namespace incompatibility b/n XPath 2.0 Data Model and XPath 1.0 (Was Re: XML schema general convert with XSLT (namespaces..))
- From: "cutlass" <cutlass at secure0 dot com>
- Date: Mon, 24 Sep 2001 15:58:21 +0100
- References: <20010924143705.20294.qmail@web14505.mail.yahoo.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
very interesting point.
> Another (minor) potential trap is that in XPath 2.0 a
> namespace node has no parent.
still unclear re this behavior,
>
> There are two consequences of this decision:
>
> 1) ../namespace::* will no longer find all namespace nodes in whose scope
is the
> element, whose attribute is the current node.
ouch !
> 2) more generally, this is an example, showing that the promise will not
be
> fulfilled that existing XSLT 1.0 transformations will work in XSLT 2.0 as
in XSLT
> 1.0
i think there is always a bit of tweaking, but your above example is a very
painful example.
i can see implementators putting in a special switch to force namespace
copying to all descendant nodes
yuk, jim fuller
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list