RE: Dynamic XSL Templates

Thanks for the info. How "standard" are extension functions? I am using
Xalan, so is the use if evaluate going to tie me to Xalan?

The business case is that we have 3 documents, which have the same
equivilant structure but different node names. So <parent><child> is
essentialy equal to <p><c>. We can not pre-process the data to first
transform <p><c> into <parent><child>. So, we hoped to have an intermediate
template call the final template with the path to the data.

-- bk


>> -----Original Message-----
>> From: Oleg Tkachenko [mailto:olegt@xxxxxxxxxxxxx]
>> Sent: Monday, November 19, 2001 8:45 AM
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> Subject: Re:  Dynamic XSL Templates
>> 
>> 
>> Bryan Kearney wrote:
>> 
>> > I do not know if this is a good thing or not, but is it 
>> possible. We have a
>> > valid business case around this, but the essence is can I 
>> dynamicly navigate
>> > the XPATH node? Assume the data is as follows:
>> You need xxx:evaluate extension function, where xxx is 
>> processor specific.
>> 
>> Check out documentstion of your processor.
>> btw, could you explain your case?
>> 

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