Hi Joseph,



thanks for your comment!



XSLT 2 is not an option....too bad.



I know that several people say that I should look at the muenchian
method. I have just read the lesson at jenitenisson's website, but

I still don't see why it has to do with grouping. you should be able
to pick out elements by their content, and check to see if that same
content is present in other siblings? Is it really necessary to do
grouping to do just that?

All the examples I've found - including the lesson at jenitenissons
website, only concentrate on the element names, not the content.

Have I totally misunderstood?



- Christian




On 6/3/06, Joseph Dane <jdane@xxxxxxxxxx> wrote:
Christian Rasmussen <christiankrasmussen@xxxxxxxxx> writes:



> These are grouped in elements of ManureTypeCodes and ManureTypeNames



sounds like some projects I've worked on ...



I have nothing really substantial to offer here, except to emphasize
that in XSLT2 this becomes extremely simple.  so my advice is to
very seriously consider using XSLT2.

that is, for various reasons, sometimes not an option.  in that case
you probably need to understand the so-called muenchian method, since
that technique is the only general purpose grouping method I know of
in XSLT1.  it's certainly not beginner level XSLT, but given a
moderate investment in puzzling it out, is not as they say rocket
science.

in fact, I learned the method from (indirectly) the man himself:



  Building Oracle XML Applications
  Steve Muench

At $44USD, it's not cheap, but it contains a section on the eponymous
method, with nice pictures and a thorough walk through.  it still took
me several tries before I really felt comfortable with the idea, but
if you're going to be doing any serious XSLT1 work, it's something you
pretty much need to understand.

--



joe