I think we cannot do push processing in XQuery, whereas in XSLT we
can. Is it correct?
Whereas, we can do pull processing in both XSLT and XQuery.
Any comments please ...
On 6/4/08, Wendell Piez <wapiez(_at_)mulberrytech(_dot_)com> wrote:
At 12:24 PM 6/4/2008, you wrote:
In that sense the two are different aren't they...? XSLT's
recursive descent processing model makes it ideal for the
task, while in XQuery you would pretty much require XQuery
Update to do the same task.
Yes. XQuery tends to work better when you want to extract a small amount
of
information from a large document and ignore the rest. XSLT tends to work
better if you want to keep most things the same and make a few small
changes. Of course there's a range of tasks between those extremes.
To say nothing of making a wholesale transposition or "transformation", as
it is called, from one structure to another.
Of course, that's the job XSLT was designed for, and it'll be interesting to
see how much reinventing of wheels there is on the XQuery side.
More than one smart person has derided XSLT's syntax. Maybe someone should
disguise it as XQuery.
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
======================================================================
--
Regards,
Mukul Gandhi
--~------------------------------------------------------------------
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>
--~--