OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Doing it the other way around (Re: transformations)

[ Lists Home | Date Index | Thread Index ]
  • From: Matt Sergeant <matt@sergeant.org>
  • To: Alexey Gokhberg <alexei@bluewin.ch>
  • Date: Tue, 21 Nov 2000 16:07:47 +0000 (GMT)

On Tue, 21 Nov 2000, Alexey Gokhberg wrote:

> Most of pure XSLT problems can be solved by embedding XSLT into a
> powerful scripting engine (e.g., ECMAScript/JavaScript), and by adding
> XSLT extensions designed to call scripts from XSLT stylesheets.
> Furthermore, scripting engine can provide DOM support to handle
> intermediate results and SAX support to filter source/result data and to
> integrate various XML transformation components into pipelines. Add
> direct support for lower-level components like XPath expressions and
> node-sets or XSLT pattern matching, implement regular expressions for
> search/match/substitution in text data - and you will get the powerful
> transformation engine using only the already existing technologies.

I see people doing this with my own XPathScript too, but the model worries
me a little...

If what we're trying to achieve with stylesheet transformations is
separation of content from presentation, how are we justifying having data
(e.g. SQL results) appear in our presentation layer? 

(I have some answers to this, but I'm more interested in how other people
see it)


    /||    ** Director and CTO **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // **     Personal Web Site: http://sergeant.org/     **
    //  \\


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS