Re: Antwort: comments. (Re: key() Re: Saxon VS XT)

Subject: Re: Antwort: comments. (Re: key() Re: Saxon VS XT)
From: David Tolpin <dvd@xxxxxxxxxxxxx>
Date: Sat, 12 Aug 2000 17:28:23 +0500 (AMST)
> What I do know is that XSL ( the original one, XSLT + XSL FO ) 
> was a language designed for a pipe of 2 components 
> ( XSLT | XSL FO ) based on the years of expereince 
> that James Clark got with DSSSL. The thing which 
> is good for the pipe of 2 components is by induction 
> good for pipe of N components. 

There is no such thing as a pipe between XSLT and XSL FO.
XSLT converts something into XSL FO. What happens later
has no relation to XML. Where do you see several steps piped?

> > Whether pipes make impossible things possible or just turn frustration
> > into fun, I dare not judge now. Good question, I'll think about it.
> 
> Because pipes do not introduce any new syntax to XSLT, pipes 
> have no impact on 'possibility'  of anything. This means I don't 
> understand what do you mean comparing 'fun' with 'possibility'.
> 
Pipes ARE new syntax. One needs a way to describe a pipe (A|B|C|tie D). 
The way it describes it is a language. The language for pipes is either becomes
a part of XSLT or an extension to it.

> Because  I'm just mortal hacker  - I simply don't understand 
> how to avoid call-template, but of course I'l appreciate 
> the snippet of  some code ( in the 'true' transformation  language, 
> 'procedural' , 'declaratibve'  or whatever  ) which will show, say, 
> calculation of max value  of some list  -  written without 
> call-template AKA procedural hint.
> 

Paul,

the question is not whether to use call-template, key, pipes or not for
the sake of their conceptuality or purity. Anything that gives result
may and must be used. 

The point is that there is no difference other than personal preferences
between (call-template/key staff and using pipes) -- they do the same
thing to the declarative ideas of XSLT and have equally harmful. But
useful. Pipes are just another language for the same techniques. And
it is not necessarily a better language, since pipes have only limited
functionality compared to call-template/key, while providing the 
same level of drawbacks.

There are may be cases when pipes are the most convenient, while
at other times they are just a pain in the neck. Whether they must
be made a part of XSLT or not is an open question.

Dvd


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


Current Thread