At 2:35 pm +0200 10/4/02, Stefano Mazzocchi wrote:
>Ulrich Mayring wrote:
>
>> Could you explain where XSLT lacks solidity?
<snip/>
>In short: stylesheets's declarativeness was designed to make their
>contracts less solid ("if this template matches, run it, otherwise do
>nothing and don't even signal it"). It's very easy to have 'dead parts'
>of your declarative code.
Absolutely true
>This is a *feature* when it comes to 'what-if' scenarios but Jeremy has
>been using them in a procedural case and this, IMO, sacrifices contract
>solidity, expecially in a multi-authored environment like this one.
>
>HOpe this helps.
XSLT is just a language ....
A very easily adaptable one in the Cocoon environment, hence the ease with
which I can experiment with different ideas and switch things around.
A problem in a production environment however as you point out.
My hope with the <slash-edit/> experiment is that a clean identification
and separation of concerns can be found, and applied to XSLT as to the
other components; the XSLT language could be used by more than just the
'style' group.
As contracts solidify, decisions can be made about which XSLT implemented
contracts it is worth converting to Java Transformers what adapt the
pipeline according to their role.
It's heretical stuff, I know ;)
Thanks for the interest
regards Jeremy
--
___________________________________________________________________
Jeremy Quinn Karma Divers
webSpace Design
HyperMedia Research Centre
<mailto:[EMAIL PROTECTED]> <http://www.media.demon.co.uk>
<phone:+44.[0].20.7737.6831> <pager:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
