I've run into this issue with the design of a recent XML solution I needed. At the time, XInclude support was not very stable in any implementation I had access to, so I decided to use XLink and implement a "poor-man's" XInclude by using a simple XSLT transformation to take all XLink references and "inline" them as the source XML document was processed. It worked quite well. I'm attaching the XSLT stylesheet that I used to accomplish this:
As part of this stylesheet, I also needed to generate a unique document ID for each included document that I processed. The XSL would have been much simpler if I was just doing a simple inclusion. - Tim -----Original Message----- From: Joseph Kesselman [mailto:[EMAIL PROTECTED] Sent: Friday, March 24, 2006 10:40 AM To: [email protected] Cc: [email protected] Subject: Re: Xlink support >3. The idea is to use XLink to "Include" an XML document into another. >By "Include" I mean reference but still access the node as if it were >in the current document. At least that was the idea I was given. Sounds like you want to look at XInclude as well as XLink. I think more implementations of XInclude currently exist, since it's a more specific and hence more easily coded mechanism. ______________________________________ "... Three things are most perilous: Connectors that corrode, Unproven algorithms, and self-modifying code! ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XlinkPreprocessor.xsl
Description: XlinkPreprocessor.xsl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
