 |
|
|
On Sun, 01 Jul 2007 09:56:13 -0600, Manfred Staudinger
<manfred.staudinger@xxxxxxxxx> wrote:
What I don't know
is who to apply a different stylesheet with it???
This is a definite -1 for this technique. There's two ways I can think of
working around this,
1) Have two different file versions with the same XML data, changing the
value the PI.
2) Import the necessary transformation files and use an XML driven
approach to deciding which one to use (e.g. <xsl:template
match="/foo">...</xsl:template> <xsl:template
match="/bar">...</xsl:template>
Dependent on the size of both the XML data file and the XML transformation
file(s), there could be a significant barrier to entry for using either of
the above solutions. The best solution in this regard would be to use
JavaScript-based transformations.
--
/M:D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
http://dev.aol.com/blog/3155
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
