<br><br><div class="gmail_quote">2008/4/24 John Snelson <<a href="mailto:john.snelson@oracle.com">john.snelson@oracle.com</a>>:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How about moving forward with a few of these suggestions:<br>
<br>
1) XQuery probably needs a standard native application platform like Rails to enable rapid web development. This also gives us a good chance to choose a name without "query" in it, which undoubtedly pigeon holes XQuery itself sometimes.<br>
<br></blockquote></div><br>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. Majority of programmers cannot even understand where to start from. We need an application platform and well eleborated scenarios for all main use-cases of *end-to-end* Web/Web2 application development. Such scenarious should include not only database querying/updating but also Web interface development, integration with other languages and services (including REST services), deployment, etc.<br>
<br>BTW our team can contribute to such a platform.<br><br>Maxim Grinev<br><a href="http://www.modis.ispras.ru/sedna">www.modis.ispras.ru/sedna</a><br><br><br><br>