[xsl] How to specify document order location path for identical elements with different parents?

Subject: [xsl] How to specify document order location path for identical elements with different parents?
From: Alan Stein <as@xxxxxxxxxxx>
Date: Fri, 02 Apr 2004 14:37:45 -0500
Thanks much for the help with my previous posting.

I think I've better articulated my question in the following example:

Given the following XML:

<?xml version="1.0" encoding="UTF-8"?>
<reportlist>
   <report>
       <codelist>
           <code type="a"/>
       </codelist>
       <codelist>
           <code type="b"/>
           <code type="c"/>
       </codelist>
   </report>
   <report>
       <codelist>
           <code type="a"/>
           <code type="b"/>
       </codelist>
       <codelist>
           <code type="a"/>
       </codelist>
   </report>
   <report>
       <codelist>
           <code type="z"/>
           <code type="a"/>
           <code type="d"/>
       </codelist>
   </report>
   <report>
       <codelist>
           <code type="a"/>
           <code type="e"/>
           <code type="f"/>
       </codelist>
   </report>
   <report>
       <codelist>
           <code type="e"/>
       </codelist>
   </report>
</reportlist>


How do I perform the following queries?


1) What is the number of reports which are coded with either an "a" or "b" where the last "a" or "b" code of the report (in document order) is an "a"?

(correct number is 3. Yes, this has been double checked.)


2) What is the number of reports which are coded with either an "a" or "b" where the last "a" or "b" code of the report (in document order) is a "b".


(correct number is 1. Yes, this has been double-checked.)


In my previous posting I recevied several helpful responses. Unfortunate that I couldn't apply them to my application because my example was too simplified. Specifically, codes in the same report may have different codelist parents, and this seems to be what's at the root of my problem formulating an xpath statement. Hopefully the revised example more accurately reflects my problem.


Thanks again for the help. I'm impressed by the brainpower in XML design and available in this forum.
--Alan


Current Thread