[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Why aren't rules matched with "*"?
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@xxxxxxxxxxxxxxxx [mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Kay Michael Sent: Friday, July 21, 2000 7:56 AM To: 'xsl-list@xxxxxxxxxxxxxxxx' 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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|