XQuery and Web 2.0

[Maxim Grinev]

I don't mean to say that the whole application should be implemented in
XQuery. Nether our team nor Sedna users try to do this. If XQuery were such
a language which allows to do this, there should be no problems. One cannot
implement everything in XQuery that is why he/she has to understand what
other languages/tools can be used and how to integrate them with XQuery. A
pipeline language does not provide complete answer to these questions.

In our paper we described why XQuery is not good for some tasks and proposed
ideas of combining XSLT/OmniMark with XQuery to implement the tasks, but it
is also only part of the answer:
http://www.xml.com/pub/a/2006/12/06/xquery-xslt-omnimark-mixed-content-processing.html

Maxim


2008/4/26 Michael Kay <http://x-query.com/mailman/listinfo/talk>:

>  I agree with John. Absence of an application platform like Rails is one
> of the main reason of not using XQuery widely. According to our experience
> (we are developers of Sedna XML DB) with Sedna users only very smart
> programmers can build *end-to-end* applications using XQuery.
>
>
> They shouldn't even try (in fact, I don't think they are very smart if
> they do try). Use something like Orbeon XPL as the general application
> framework, and use it to link together components written in XQuery, XSLT,
> XForms, or anything else. The important thing is that the data should be in
> XML end-to-end, not that the logic should be in XQuery end-to-end.
>
> Michael Kay
> http://www.saxonica.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://x-query.com/pipermail/talk/attachments/20080426/025bb2c0/attachment-0001.htm