Subject: RE: [xsl] Definite list of XSLT 2.0 processors? From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Mon, 18 Jan 2010 13:11:33 -0500 |
> is Marklogic use own XSLT engine? > > XSLT engine integrated with database engine look like very > powerfull but also sound like "too good to be true"
There's no intrinsic reason why it should be hard. XSLT does nearly all its access to source documents by means of explicit XPath expressions (with minor exceptions like xsl:number), so if you've got an XPath engine to access the database then you're 90% of the way there. The main difficulty is likely to be optimization: it's hard to work out by static analysis what a stylesheet is doing, and therefore whether it can take advantage of indexes.
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Definite list of XSLT 2.0, Michael Kay | Thread | Re: [xsl] Definite list of XSLT 2.0, Justin Johansson |
Re: [xsl] Command Line, Syd Bauman | Date | Re: [xsl] Definite list of XSLT 2.0, Wendell Piez |
Month |