- From: James Clark <jjc@jclark.com>
- Date: Fri, 13 Aug 1999 11:06:22 +0700
- To: Jon Smirl <jonsmirl@mediaone.net>
- CC: xsl-editors@w3.org
I wonder whether it would be sufficient to tweak the definition of xsl:include to say that an xsl:include element should be ignored if the specified URI has already been included with the same import precedence. I can't think of any cases where you would to include the same URI more than once with the same import precedence. Jon Smirl wrote: > > I am finding it useless to have one XSL sheet import or include another and > then use these sheets with the embedded include/import in a larger system. > The problem stems from multiple includes of the same file. There really > needs to be a way to say: don't include/import this file if it is already > loaded. > > For example > file A has a wild card match, Z, in it > file B includes A - B is used standalone, has templates named X and Y > file C includes A - C is used standalone, has different template named X > file D needs X, Y and Z from C, B, A > > You can't import C, B, A because C includes A and A has a wild card (hides > contents of B) > If you include C, B, A you have to rely on the multiple templates of the > same name error resolution > > Two solutions, provide a way to say don't load if already loaded. Or create > two more wrapper files, E/F which split B/C into templates and includes. In > my system I will need hundreds of wrapper files and I don't want to do this. > > Jon Smirl > jonsmirl@mediaone.net
Received on Friday, 13 August 1999 00:08:15 UTC