Re: A new approach

I'll point out again that having the top level element called <rootnode>
will always lead to confusion in Xpath as you will have the root node
(/) having a child called rootnode, but anyway if it's a pre-existing
xml vocabulary and you are stuck with the names XSLT won't get confused,
it's all legal.

It isn't at all clear from your description why you need two xsl files.
Why not put it all in to one?

The usual model is that you put common shared code into a file that you
_include_ (or _import_)  into your top level stylesheet and you have
different top level stylesheets that implement different customisations.

But in your case it doesn't appear that you are trying to generate
different styles, ao you could just have one stylesheet.

David

-- 
http://www.dcarlisle.demon.co.uk/matthew

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list