Kenny Akridge wrote:
I've looked at the FAQ and can't seem to find an exact answer. I am trying
to generate all nodes who contain two specific children nodes. I'm thinking
that using a key would be the best method, but it doesn't seem right to me
to use multiple keys.
For instance, if I have:
<Attendance>
<FirstName>Bill</FirstName>
<LastName>Smith</LastName>
... some other important data
</Attendance>
Assuming FirstName + LastName is a unique identifier, how can I find all
<Attendance> such that Attendance/LastName == LastName being processed and
Attendance/FirstName == FirstName being processed?
I don't think you want to use first and last name as unique identifiers.
The chance of having two Bill Smiths is pretty high...
Why not just create a truly unique identifier and use that as your key/@use?
<Attendance id="a12345">
> <FirstName>Bill</FirstName>
> <LastName>Smith</LastName>
> ... some other important data
> </Attendance>
best,
-Rob
Thanks
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--