At 10:12 AM 1/18/2010, Mike wrote:
> 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.
Then too, there's the pipelining approach, whereby you use a simple
query to get at your data, then XSLT to process it -- XRXX, if you will.
The fact that XSLT and XQuery both do many of the same things is no
reason they have to be inimical. (I mean, where's the sense in that?)
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
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
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--