- From: Christian Grün <christian.gruen@gmail.com>
- Date: Mon, 16 Mar 2015 14:09:40 +0100
- To: "Liam R. E. Quin" <liam@w3.org>
- Cc: Hans-Juergen Rennau <hrennau@yahoo.de>, "expath@googlegroups.com" <expath@googlegroups.com>, "public-expath@w3.org" <public-expath@w3.org>, "dannes@exist-db.org" <dannes@exist-db.org>
> The only satisfactory answer I've seen is that XQuery was designed to > be embedded in other languages, rather like SQL, and not as a complete > system. When you try and introduce side-effects you have problems. My perspective on this is: The existence of the EXPath modules and many other side-effecting modules in XQuery processors (eXist, Saxon, Zorba, MarkLogic, our own, possibly others) indicates that there *is* a need to do more with the language than just using it as focused query language. XProc seems as a useful extension to me, but it couldn't imagine writing full applications with it. And from the implementation perspective, my experience is that it is fine to have side-effecting functions as long as they are consistently dealt with. However, it would be quite some effort at this stage to define rules that all implementors will agree with. But the major issue is that we will hardly find anyone who would be willing to take care of this. But I may be wrong… Any volunteers out there? > At any rate I don't see the XQuery Working Group making much more > progress in the area of managing side-effects. I agree. Christian
Received on Monday, 16 March 2015 13:10:28 UTC