This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Merging data (two xml documents, two context nodes)
I just wanted to make one more comment.
I personally like to call just one config file as my ONLY source file. From
there everything is KEYed so it is fast to access a particular page's info
(XSLT, content XMLs, other info...). Everything that is 'repeatedable' is
separated out into it's own type of config (content, xslt) and ID'ed in the
main config so the site is normailzed.
fwiw :)
-Rob
----- Original Message -----
From: "Robert Koberg" <rob@koberg.com>
To: <xsl-list@lists.mulberrytech.com>
Sent: Tuesday, December 18, 2001 8:37 AM
Subject: Re: [xsl] Merging data (two xml documents, two context nodes)
> Make a top level variable that holds the original document nodeset. Then
> whenever you need it you can access the variable
>
> best,
> -Rob
>
>
> > So the problem here is how to read data from the original context node
> > (data.xml/page) after the called template has changed its context to
> > congfig.xml/page/attributes/attribute?
> >
> > I think (hope) i'm just missing something simple...
> > Suddenly i'm wondering if i should be parsing config.xml as the base
> > document, and modifying it according to the contents of data.xml,
instead
> if
> > the other way around.
> >
> > Thanks for any comments,
> > Marty
> >
> >
> > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list