Subject: RE: [xsl] Compound filter in for-each From: "Michael Kay" <mike@xxxxxxxxxxxx> Date: Tue, 24 Mar 2009 22:52:39 -0000 |
> <xsl:template match="Folder"> > > <xsl:for-each > select="Placemark/ExtendedData/Data[@name='rdb_status' and > value='Endangered']"> Does the Folder element have a child called Placemark? > > <xsl:value-of select="@id" />, > <xsl:value-of select="name" />, Does the Data element have both an attribute and a child element both called "name"? > <xsl:value-of > select="ExtendedData/Data[@name='location_name']/value"/>, Does the Data element have a child called ExtendedData? Hope you're starting to get the message. Paths follow a route from A to B, and they won't select anything if you don't know where you're starting from. Michael Kay http://www.saxonica.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Compound filter in for-ea, Alan Hale | Thread | [xsl] [XSL] Adding namespaces to ou, Anna Södling |
RE: [xsl] copy attribute question, Michael Kay | Date | Re: [xsl] copy attribute question, Garvin Riensche |
Month |