This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Combining stylesheets for baseclass-subclass type documents
- From: "Daniel Brockman" <daniel dot brockman at utb dot sandviken dot se>
- To: xsl-list at lists dot mulberrytech dot com
- Cc: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 15 Apr 2002 00:22:34 +0200
- Subject: Re: [xsl] Combining stylesheets for baseclass-subclass type documents
- References: <fc.0064b54a0167c46c0064b54a0167c46c.167c4b5@utb.sandviken.se><BAD.8050306@koberg.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
>Can you break out the common templates/variables/params into separate
>XSL documents? This way you can directly target your unique
>circumstance. For example, what i do is have a global_defintions.xsl
>that includes all the common XSLT documents (variables, params) that
>have common usage. Then in the unique XSLTs, I just include
>global_defintions.xsl. When you need the unique view you call the unique
>XSLT doc which includes the common stuff.
Well, in a way, my a.xsl is like your global_definitions.xsl: stylesheets
for unique circumstances (e.g., b.xsl) indeed include this base
stylesheet. The problem lies in how the two need to be combined
(explained and examplified in my previous message) under the restrictions
in place:
a.xsl has to be independent of b.xsl, and b.xsl has to inherit the
a-specific information from a.xsl. Additionally, a.xsl should be able to
transform a document on its own; it's not just a "library-stylesheet".
-
Daniel Brockman
mailto:daniel.brockman@utb.sandviken.se
"To spot the expert, pick the one who predicts
the job will take the longest and cost the most."
- Murphy
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list