Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

Hi Adam (or anyone else interested in getting the XQuery 3.1 test
suite running in eXist so we could report the eXist community's hard
work at supporting XQuery 3.1 features, as several other
implementations do at
https://dev.w3.org/2011/QT3-test-suite/ReportingResults31/),

I was able to get past the file module import problem simply by
commenting out this line:

  https://github.com/adamretter/fots-basex/blob/exist/fots-environment.xqm#L16

Luckily, it appears, the expath file:exists() function is basically
the same as exist's.

I'm now able to run fots.xq, and I see the output of quite a few tests
in exist.log.  But I encounter an error with the following test:

> 2016-09-08 15:05:31,148 [eXistThread-110] INFO  (LogFunction.java [eval]:151) - (Line: 97 /db/apps/fots-basex/fots.xqm) doc-uri=/db/QT3-test-suite/fn/abs.xml
> 2016-09-08 15:05:31,149 [eXistThread-110] INFO  (LogFunction.java [eval]:151) - (Line: 129 /db/apps/fots-basex/fots.xqm) query=declare base-uri "/db/QT3-test-suite/fn/"; declare context item := doc('/db/QT3-test-suite/fn/abs/e0.xml'); abs(xs:unsignedShort(.)) instance of xs:unsignedShort

Pasting this query into eXide, e.g.,

```
xquery version "3.1";

declare base-uri "/db/QT3-test-suite/fn/";
declare context item := doc('/db/QT3-test-suite/fn/abs/e0.xml');
abs(xs:unsignedShort(.)) instance of xs:unsignedShort
```

... eXide raises an error:

> Cannot compile xquery: exerr:ERROR org.exist.xquery.XPathException: err:XPST0003 unexpected token: declare [at line 4, column 1]

I'm not familiar with this "declare context item" declaration or
whether eXist supports it.  Do you by chance know if this is supported
in eXist, or how to work around this error?

Thanks,
Joe

On Thu, Sep 8, 2016 at 1:58 PM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Adam,
>
> I was just starting to look at this again, having received a note that
> the xquery working group has updated several of the tests for 3.1, and
> I encountered a roadblock that I'd be grateful for your help with.
> For context, I've done the following:
>
> 1. checked out the qt3 test suite from the w3c's cvs server as
> documented at https://dev.w3.org/2011/QT3-test-suite/
> 2. cloned your exist branch of Leo Worteler's fots-basex repo
> https://github.com/adamretter/fots-basex/tree/exist
> 3. uploaded the fots-basex directory to /db/apps/fots-basex
> 4. uploaded the QT3-test-suite to /db/QT3-test-suite, to reflect the
> $path variable defined in fots.xq line 12, but eXide complained of a
> syntax error on this line:
>
>     > error found while executing expression:
> org.exist.xquery.XPathException: err:XPST0003 expecting semicolon ';',
> found ':' [at line 12, column 46]
>
> 5. I worked around the error by deleting the "external" keyword from
> line 12. Odd that the "external" keyword would raise an error, no?
> The line in question:
>
>     https://github.com/adamretter/fots-basex/blob/exist/fots.xq#L12
>
> Anyway, next, eXide reported an error that I haven't been able to overcome yet:
>
>> error found while loading module fots: Error while loading module fots.xqm: error found while loading module env: Error while loading module fots-environment.xqm: prefix 'file' bind to 'http://exist-db.org/xquery/file'
>
> I took a look at fots.xqm, and it imports the expath file module:
>
>   https://github.com/adamretter/fots-basex/blob/exist/fots-environment.xqm#L16
>
> Thinking that your implementation of the expath file module might do
> the trick, I cloned
> https://github.com/adamretter/exist-expath-file-module and built the
> xar as directed in the readme. But when I tried to deploy the .xar
> file via Dashboard > Package Manager, I got this error:
>
>> Inconsistent package descriptor, the JAR file is not in the package: ntinuations-library_2.11-1.0.1.jar
>
> The closest name I can find to this is in
> target/file-module-1.0-SNAPSHOT-bin/lib/scala-continuations-library_2.11-1.0.1.jar,
> but I don't know how to overcome the error.  Can you suggest a way
> forward?  I've pasted in my console log from the maven builds here:
> http://pastebin.com/y54v4q3s.
>
> Should I keep trying to get the expath file module installed &
> registered with the namespace prefix "file" (I fear this would collide
> with eXist's own file module with this namespace prefix), or should I
> drop the idea of installing the expath file module and just adapt the
> code to use eXist's file module?
>
> Thanks for any guidance,
> Joe
>
> On Tue, Jan 19, 2016 at 5:02 AM, Adam Retter <ad...@ex...> wrote:
>> Hey Joe,
>>
>> Good question!
>>
>> Ultimately it is down to a lack of resources to be able to do this.
>> However, the good news is that you could help ;-)
>>
>> Leo from BaseX started a test-suite harness for the W3C XQuery Test
>> Suite, he wrote it in XQuery for BaseX. I started porting it over to
>> eXist early last year, but never had the time or pressing need to
>> complete it. My branch with the changes for eXist is here -
>> https://github.com/adamretter/fots-basex/tree/exist. Whilst a work in
>> progress, I think I was able to get some tests running. The nice thing
>> is that EXPath uses the same Test Suite format as W3C, so if we can
>> get a test harness working, we can run many tests :-)
>>
>> Perhaps this is something you would like to pick up and work on? I
>> could certainly offer guidance if you get stuck... but well I think
>> you are probably a pretty good XQuery programmer ;-)
>>
>> Cheers Adam.
>>
>> On 19 January 2016 at 04:33, Joe Wicentowski <jo...@gm...> wrote:
>>> Hi all,
>>>
>>> I notice eXist isn't included in this round of tests.  I'd be
>>> interested to know what are the barriers or obstacles to running the
>>> tests and participating in these exercises?
>>>
>>> I imagine the release of eXist 3.0 is a higher priority for the
>>> project than passing a not-yet-final spec, among others.  But I think
>>> that eXist's presence at some point would help the WG's work and
>>> strengthen the spec's goal of being supported by many implementations.
>>> Even if eXist doesn't promise complete XQ3.1 coverage (heck, they keep
>>> adding new features like templates!), the areas it does support are, I
>>> think, quite well developed - and this hard work would be worth
>>> celebrating through inclusion in these tests.
>>>
>>> Joe
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: O'Neil Delpratt <on...@sa...>
>>> Date: Mon, Jan 18, 2016 at 9:40 AM
>>> Subject: Reporting on QT3 test results for the 3.1 Specs
>>> To: pub...@w3...
>>>
>>>
>>> Dear All,
>>>
>>> I have re-generated the reports on the implementation results received
>>> for the QT3 test suite. See update:
>>> http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html
>>> We now have three implementations for XQuery 3.1, with one being
>>> anonymous. However we only have one for XPath 3.1.
>>>
>>> We have been working on the main page today. Specifically the stats on
>>> the optional features. We found that there were some overlap reported
>>> in the passes and failures. For example under ‘staticTyping’ it is
>>> reported that there are 75 test not being passed by any
>>> implementation. Under the 'higherOrderFunction’ feature we have 18
>>> test passed by no implementation. If you inspect the
>>> higherOrderFunction tests more closely we will see that 17 of these
>>> tests depend on staticTyping therefore the underlying reason for the
>>> higherOrderFunction failures is to do with staticTyping. With what I
>>> have said in mind we think it helpful to show the combination of
>>> optional features for the test case.
>>>
>>> I welcome feedback on your preference of presentation on the Optional
>>> Features section. I find 2) much more useful:
>>>
>>> 1) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optFeatures
>>> 2) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optComboFeatures
>>>
>>>
>>> Using 1) or 2) we observe that we have 75 tests with dependency on
>>> staticTyping not being passed by any implementation (including those
>>> with combinations of other dependencies).  I would like to ask if it
>>> still merits having tests on static typing?
>>>
>>> kind regards,
>>>
>>>
>>> -------------------------------
>>> O'Neil Delpratt
>>> Software Developer, Saxonica Limited
>>> Email: on...@sa...
>>> Twitter: https://twitter.com/ond1
>>> Tel: +44 118 946 5894
>>> Web: http://www.saxonica.com
>>> Saxonica Community site: http://dev.saxonica.com
>>> Bug tracking site: https://saxonica.plan.io/
>>>
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb