It was John Snelson who told me about the ‘ XQuery 1.0 Grammar Test Page’ which presents a Java Applet that will parse your XQuery or convert it into XQueryX. For those people dipping their toe in the XQueryX waters then this is a better place to start than stumbling around using oXygen and the XQueryX schema like I did initially. I also found ‘ XQ2XML: XML syntaxes for XQuery’ by David Carlisle I haven’t had a chance to look at it yet but it may prove useful too

Originally posted here:
A quick straw poll – XQueryX have you or are you
using it?

Just a quick question, if I may, Have you or are you using XQueryX? I’ve noticed that the XQueryX recommendation has been updated as part of the XQuery 1.1 work and I’m interested in knowing if people are using XQueryX, you don’t have to say why or what for, I just want to gauge how many people are using it.

See original here:
A quick straw pole – XQueryX have you or are you
using it?

Hurts me every time I write an XML file as well !!! David A Lee On Jul 31, 2010, at 1:52 AM, Daniela Florescu wrote: > > > > > > > It could be done with an extra-grammatical disambiguation rule not unlike many of the rules we already have: if the next thing after the “> ” at the end of a direct constructor is immediately followed by “

Read more here:
Comma problem Re: ANSWERS to "What’s wrong
with XQuery" question

> > > > It could be done with an extra-grammatical disambiguation rule not > unlike many of the rules we already have: if the next thing after > the “> ” at the end of a direct constructor is immediately followed > by “

Read the original here:
Comma problem Re: ANSWERS to
"What’s wrong with XQuery" question

> use cases where the expression appears within curly braces, e.g. in a > function body, were particularly noticeable. That is a of course a question of taste, but I think I’d prefer such an explicit way of sequence construction

More:
Comma problem Re: ANSWERS to "What’s wrong with
XQuery" question

> * make your new version a clean break with the past (and change the names) – > that tends to mean you will end up with a large user community who don’t > move forward, because it’s too much work. There is a fourth choice, there are even people making incompatible changes all the time, but not caring about backwards compatibility or renaming (e.g. ObjectWeb ASM); but I think that is just bad engineering Martin

Read more from the original source:
module versioning

> It was somewhat surprising to me, coming from that background, that the precedence of “,” was so low, and from the other responses, it seems some others shared (or at least have been made aware of) the same confusion, although it is, as you say, easily remedied. The explanation of why the precedence is so low lies in the overloading of “,” to separate arguments in a function call, which was something where we really had no choice. This meant that we needed the concept of “ExprSingle” to mean “an expression not containing a top-level comma” to define what was allowed as a function argument, and this decision led to “,” having lower precedence than any other operator

See the original post here:
Comma problem Re: ANSWERS to "What’s wrong with
XQuery" question

On 28/07/2010 22:47, Pavel Minaev wrote: > An obvious alternative would be to provide some explicit top-level > construct that introduces (and clearly delineates) an XML fragment as > a sequence of direct element constructors, with no need for > interleaving commas. …… /*

Continue reading here:
Comma problem Re: ANSWERS to "What’s wrong with
XQuery" question

Daniela Florescu wrote: > On Jul 19, 2010, at 3:46 PM, Michael Kay wrote: Hi, I am sorry to respond to a quite old thread, I am still going through my unread emails, because I am back from holidays… > > I think if I were writing a library for a vocabulary where > > schema validation is the norm (like FpML , say), > What would you do for the EXPath’s HTTP module ?

Link:
Schema Typed Parameters and Return Values in
Library Modules

To be fair to my colleagues, the product’s documentation and the massive online tutorials we have published explain well what XQJ is and how to use DataDirect XQuery. http://web.datadirect.com/resources/dis/xqj-tutorial/index.html True, DataDirect XQuery is a commercial product, an enterprise -class implementation and an embeddable component. but that doesn’t mean that it cannot be easily used for querying plain XML.

More here:
Cannot access DDXQDataSource for XQuery in java