[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: xsl:include is necessary after all

Subject: Re: xsl:include is necessary after all
From: David Carlisle <davidc@xxxxxxxxx>
Date: Fri, 18 May 2001 18:31:48 +0100
Re:  xsl:include is necessary after all
> Besides breaking existing stylesheets, what sorts of issues would arise if
> conflicts were resolved the other way around instead (priority first and
> *then* import precedence)?

I suspect the reason why import wins is that if it were the other way
round you'd have to know more about the sheets you were importing.

Take a big collection like Norm's DocBook stylesheets, you can import
that then make customisations with templates in your top level stylesheet
and you know anything you define wins. You can treat Norm's code as a
black box. (I know this doesn't always work, but...)
If priority won then you would have to know the priorities of the
templates in all the docbook stylesheets, so you could make sure your
customisations had higher priority.


This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.