list4xt : Mailing list for the XT users community.

[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]

User: Website

New Message
• Reply
• Next message: Karen Lease: "[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]"
• Previous message: Dave Pawson: "[list4xt] Re: Sun XSLT compiler"
• Next in thread: Karen Lease: "[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]"
• Maybe reply: Paul T: "[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

 
  Eric van der Vlist <vdv@dyomedea.com> wrote:

Leigh Dodds wrote:

> The speaker was quite derogatory about XSLT in general
> (a 'toy' language lacking 'scientific rigour') and
> the current XSLT processors ('naive implementations').

I don't know if it's what you meant, but I think everyone has his own
personal reasons of being frustrated by XSLT depending on his prior
experiences.

# XSLT is OK ;-) The XSLT VM paper is also OK. The funny story is that there could be not too much efficiency difference between compiling into "bytecode with stack" and compiling into "objects with action functions/methods with global heap" ( "naive XSLT implementation" ).

# In fact, the XMLT VM paper is weaker than it may look. I'm sure *this* bytecode is not the way to go.

To be fair with XSLT, we need to remember that "XSLT is not intended as
a completely general-purpose XML transformation language" as mentioned
in the abstract at the very beginning of the recommendation.

# It will be. ;-) Tersenness + streaming + maybe variables == XSLT v 2. And it will be universal.

# In UX I'm currently re-writing some typical perl stuff into XSLT. I like the results.

Going further, I have the feeling that a same "reality" can be
represented using different models (such as "raw XML" for simple trees
and RDF or topic maps when it's beginning to get more complex) and that
more abstract languages could/should be able to work more transparently
on these models.

# Hm... Why can't you serialize different models into some unified model, chaining XSLT stylesheets, and then use your 'abstract' processing part on the serialized 'uni-model' ? I don't think there should be a language for this sort of things, but maybe I don't understand your point. This is related to 'processing MinML, but colorizing MinML on output' ( from SML-dev )

> But it's not XSLT any longer ;=) ... unless maybe if you can plug
> alternative predicate evaluation mechanisms to XPath.

# When everyting is XML - XPath is OK, right ? ;-)

# Rgds.Paul.

---------------------------------
Do You Yahoo!?
Send instant messages with Yahoo! Messenger.

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

• Next message: Karen Lease: "[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]"
• Previous message: Dave Pawson: "[list4xt] Re: Sun XSLT compiler"
• Next in thread: Karen Lease: "[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]"
• Maybe reply: Paul T: "[list4xt] Re: Naive XSLT [was: Sun XSLT compiler]"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]