[Home]  [List]  [News]  [Docs]  [FAQ]  [Downloads]  [Resources]  [About]
Search :
/Home /List

list4xt : Mailing list for the XT users community.

[list4xt] Re: saxon:evaluate

Subject: [list4xt] Re: saxon:evaluate

User: Website

From: Paul T (pault12345@yahoo.com)
Date: 25/08/2000 - 22:32

 
> Sorry Paul, I steer well clear of such things!
> I'm no lawyer and freely admit it.

This is my simplified view on the world - I'm thinking that anybody who knows English is capable of understanding Mozilla license ;-)

> is there anything under the readme / copy notice that
> says it in plain English ( /American).

I failed to find...

Back to the point.

> Just my 2d worth (for Eric - I like that one Eric)

I have messy feelings on Eric's proposal. On one hand what is says is :

XML ( aka data ) is node-set. XSLT ( aka code ) is also node-set. Very consistent ( but it is not 'really true'. The 'really true' thing is that 'on the level of lexer both are streams of SAX events - see below ;-)

Turning string into Xpath with xt:evaluate is just a "generate the *small part* of the stylesheet on the fly", when Eric's suggestion means "generate the *entire* stylesheet on the fly".

If generating only *small part* of the stylesheet on the fly is evil, why "generate the entire stylesheet on the fly" is *less* evil ???

Also, I think that implementation of Eric's 'execution of the stylesheet which is compiled into nodeset' will require much more work than implementation of xt:evaluate.

What really happens inside XSLT engine is that *data* ( XML ) is compiled into one structure ( engine-specific node-set ), but *code* ( XSL ) is compiled into different internal structure. Yes, both code ( XML ) and data ( XSL ) have common 'access' with SAX when engine reads XML or XSL - both are turned into the stream of SAX events - but this 'common' happes only on the level of syntax parsing, not on the level of semantcis aka internal representation.

My conclusion on Eric's suggestion is: even it is logically consistent, implementing this in the core is more serious disaster to the engine than implementing xt:evaluate *and* I don't see any benefits comparing to the benefits of xt:evaluate.

I don't understand why generation of 'the entire stylesheet' is in any way better than 'generation of small part of the stylesheet == xt:evaluate" and I don't understand why xt:evaluate is evil.

Rgds.Paul.

 

---------------------------------
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere! 

--
Mailing list for the XT users community.     (http://2015usca.org)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)

Archive générée par hypermail 2b28 le 06/11/2001 - 11:46 CET

webmaster@4xt.org