OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [ANN] XQuery prototype

Dear Jonathan, while this is true for the syntax provided at the moment,
please note that the generator takes a syntax and generates the tests.
Since our developers tried to implement the normative parts of the
working draft and the February's working drafts normative grammar was -
umh - rather buggy, the implemented grammar had to make some

There is quite a difference between the use cases (that certainly can
and should serve as a start) and an automatically generated set of

I am sure as the time progresses and the new working draft will provide
a usable, normative grammar, the test cases that we generate will be
following the WD syntax...

Best regards

> -----Original Message-----
> From: Jonathan Robie [mailto:Jonathan.Robie@SoftwareAG-USA.com] 
> Sent: Tuesday, May 15, 2001 7:13 AM
> To: Michael Rys; xml-dev@ic.ac.uk; www-ql@w3c.org; 
> xmldb@xmldb.org; xml-dev@lists.xml.org
> Subject: Re: [ANN] XQuery prototype
> At 10:21 PM 5/13/2001 -0700, Michael Rys wrote:
> >In addition the sites offers a a set of compliance tests that can be 
> >used to check the syntax for the XQuery parser. Since the tests are 
> >automatically generated based on the syntax, some of the 
> statements may 
> >not have meaningful semantics.
> I would like to point out that these compliance tests were 
> generated using 
> the Microsoft grammar, not the grammar of the XQuery Working 
> Draft, so they 
> test compliance to the syntax of Microsoft's prototype, not 
> to the XQuery 
> language as described in the W3C specification.
> The examples in the XQuery Working Draft and in the solutions 
> to the Use 
> Cases exercise more features and are compliant with the 
> XQuery language. I 
> suggest that people use these for compliance testing.
> I write this as an individual, not in my role as an editor of 
> the XQuery 
> specification.
> Jonathan