[Home] [By Thread] [By Date] [Recent Entries]
On 04/09/2011 10:59, Alex Muir wrote:
Something I'm just wondering for the sake of learning more... Having both xsl:import and xsl:include is probably one of the more confusing and arguably least successful parts of the XSLT language design, but I think one of the main factors governing the design of xsl:import is that you should be able to take a big stock stylesheet as a black box (say the docbook or TEI collections) and over-ride templates for specific elements without knowing too much about the internals. hence the design that import precedence trumps priority. On the other hand though, the fact that import precedence has such a fundamental effect on template matching makes it hard to use xsl:import as a means of splitting up large stylesheets purely for organisational convenience, hence the need for xsl:include... David
|

Cart



