This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Why aren't rules matched with "*"?
- To: <xsl-list at mulberrytech dot com>
- Subject: RE: Why aren't rules matched with "*"?
- From: "Darrin Bishop" <dbishop at legis dot state dot il dot us>
- Date: Fri, 21 Jul 2000 12:06:01 -0500
- Reply-To: xsl-list at mulberrytech dot com
I spent some time looking over the original source and transformation that
started this thread. By looking at the XML, the issue for why '*' did not
work became apparent. * returns true for the default element for the
current axis, the current axis was an element, there for it found elements.
What was not stated was off the current context element there were children
text nodes. * was not returning true since they were not element nodes. By
using node() instead of *, all the child nodes were processed.
-----Original Message-----
From: owner-xsl-list@mulberrytech.com
[mailto:owner-xsl-list@mulberrytech.com]On Behalf Of Kay Michael
Sent: Friday, July 21, 2000 7:56 AM
To: 'xsl-list@mulberrytech.com'
Subject: RE: Why aren't rules matched with "*"?
> child::* means, essentially:
>
> from among all the nodes along the child axis,
> just the ones that are elements with any name,
> in no namespace.
No, it means "with any name, in any namespace". If you want only those
elements whose name has a null namespace URI, I think the only way to get
them is
child::*[namespace-uri()=""]
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list