We have been working on implementing parsed source in an xslt engine
I'm sorry, I haven't the faintest idea what this means. Could you
explain more carefully what you are trying to do?
Michael Kay
Software AG
home: Michael(_dot_)H(_dot_)Kay(_at_)ntlworld(_dot_)com
work: Michael(_dot_)Kay(_at_)softwareag(_dot_)com
and have run into a question about what to do when parsing an xml
source that contains xsl instructions.
(By 'contains' I'm including both embedded xsl and PI referenced xsl.)
Is it expected that the resulting parsed source tree contains the xsl
as a subtree or should the resulting parsed source tree be the
transformed result of the contained xsl?
I can see arguments for both sides but I'm leaning toward the tree
containing an xsl subtree at this point. Is there any discussion or
documentation on this issue anywhere on the web?
Thanks,
John Mostrom
p.s. I'm subscribed to the digest so if you could cc: me on the
discussion, it would be great!
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list