Nabble - w3.org - public-xqts-comments

Re: Test Harness for SQL Server 2005

2008-08-05T11:13:36Z

Sorry, but I'm not aware of any test harness implementations for SQL Server 2005.

-- Andrew (co-chair XML Query WG)

--------------------
Andrew Eisenberg
IBM
4 Technology Park Drive
Westford, MA 01886

andrew.eisenberg@...

From:	"Matias Reina" <mellimatias@...>
To:	public-xqts-comments@...
Date:	08/04/2008 10:36 PM
Subject:	Test Harness for SQL Server 2005

Hello,
I'm looking for an implementation of "Guidelines for Running the XML Query Test Suite" for SQL Server 2005.

Anyboy can help me?

Thanks in advance
Matías Reina
Centro de Ensayos de Software

Test Harness for SQL Server 2005

2008-08-04T14:07:06Z

Hello,
I'm looking for an implementation of "Guidelines for Running the XML Query Test Suite" for SQL Server 2005.

Anyboy can help me?

Thanks in advance
Matías Reina
Centro de Ensayos de Software

Re: Remarks and questions about XQ Update Facility test suite

2008-05-23T13:57:01Z

I forgot to mention a new XQuery Update tutorial that XMLmind has just
published
http://www.xmlmind.com/_tutorials/XQueryUpdate/index.html
(I am going to write to Liam for announcing it on the XQuery page)

You are most welcome to comment about this tutorial and signal any
mistake of inaccuracy
or obscurity, including in my English.

Cheers
Xavier

Jonathan Robie wrote:

> Excellent - thanks for sending these Xavier! As you know, results like
> these really help us make the case that our specification should
> progress. I assume we can put these results on our public test results
> page?
>
> Jonathan
>
> Xavier Franc wrote:
>> Hello Jonathan,
>>
>> my apologies too for the delay in responding to you, this is not
>> retalation :-)
>> I was just waiting to be ready to provide results for the new version
>> Qizx 2.1
>> which supports the XQuery Update Facility 1.0.
>> Pleas find attached these results.
>>
>> Concerning my previous remarks/questions, I completely understands
>> your reasons.
>>
>> best regards
>> Xavier
>>
>> Jonathan Robie wrote:
>>>
>>> Andrew Eisenberg wrote:
>>>>
>>>> > - it would be nice to have a zip distribution of the XQUF TS.
>>>>
>>>> I'll ask Jonathan to comment on this.
>>>
>>> First off, Xavier, my apologies, I just check and I see that I
>>> failed to respond to an earlier inquiry from you.
>>>
>>> So far, I've been resisting suggestions to create a zip distribution
>>> because most developers are able to use source code control systems,
>>> which are a better way to develop a test suite collaboratively, and
>>> I don't want to have to worry about whether a zip distribution is
>>> out of sync with the source code repository. If enough people give
>>> me a good reason that the source code control system does not work
>>> for them, I may change my mind, but I'm reluctant to provide a zip
>>> without a really good reason.
>>>
>>>> > - Is there a plan to publish a result page like for XQuery ?
>>>>
>>>> You'll find our early results in
>>>> http://dev.w3.org/2007/xquery-update-10-test-suite/results/.
>>>
>>> And your results would be very welcome.
>>>
>>> Jonathan
>>>
>>>
>>>
>>
>
>
>

Re: Remarks and questions about XQ Update Facility test suite

2008-05-23T13:44:22Z

Excellent - thanks for sending these Xavier! As you know, results like
these really help us make the case that our specification should
progress. I assume we can put these results on our public test results page?

Jonathan

Xavier Franc wrote:

> Hello Jonathan,
>
> my apologies too for the delay in responding to you, this is not
> retalation :-)
> I was just waiting to be ready to provide results for the new version
> Qizx 2.1
> which supports the XQuery Update Facility 1.0.
> Pleas find attached these results.
>
> Concerning my previous remarks/questions, I completely understands
> your reasons.
>
> best regards
> Xavier
>
> Jonathan Robie wrote:
>>
>> Andrew Eisenberg wrote:
>>>
>>> > - it would be nice to have a zip distribution of the XQUF TS.
>>>
>>> I'll ask Jonathan to comment on this.
>>
>> First off, Xavier, my apologies, I just check and I see that I failed
>> to respond to an earlier inquiry from you.
>>
>> So far, I've been resisting suggestions to create a zip distribution
>> because most developers are able to use source code control systems,
>> which are a better way to develop a test suite collaboratively, and I
>> don't want to have to worry about whether a zip distribution is out
>> of sync with the source code repository. If enough people give me a
>> good reason that the source code control system does not work for
>> them, I may change my mind, but I'm reluctant to provide a zip
>> without a really good reason.
>>
>>> > - Is there a plan to publish a result page like for XQuery ?
>>>
>>> You'll find our early results in
>>> http://dev.w3.org/2007/xquery-update-10-test-suite/results/.
>>
>> And your results would be very welcome.
>>
>> Jonathan
>>
>>
>>
>

Re: Remarks and questions about XQ Update Facility test suite

2008-05-23T12:43:54Z

Hello Jonathan,

my apologies too for the delay in responding to you, this is not
retalation :-)
I was just waiting to be ready to provide results for the new version
Qizx 2.1
which supports the XQuery Update Facility 1.0.
Pleas find attached these results.

Concerning my previous remarks/questions, I completely understands your
reasons.

best regards
Xavier

Jonathan Robie wrote:

>
> Andrew Eisenberg wrote:
>>
>> > - it would be nice to have a zip distribution of the XQUF TS.
>>
>> I'll ask Jonathan to comment on this.
>
> First off, Xavier, my apologies, I just check and I see that I failed
> to respond to an earlier inquiry from you.
>
> So far, I've been resisting suggestions to create a zip distribution
> because most developers are able to use source code control systems,
> which are a better way to develop a test suite collaboratively, and I
> don't want to have to worry about whether a zip distribution is out of
> sync with the source code repository. If enough people give me a good
> reason that the source code control system does not work for them, I
> may change my mind, but I'm reluctant to provide a zip without a
> really good reason.
>
>> > - Is there a plan to publish a result page like for XQuery ?
>>
>> You'll find our early results in
>> http://dev.w3.org/2007/xquery-update-10-test-suite/results/.
>
> And your results would be very welcome.
>
> Jonathan
>
>
>

<?xml version="1.0" encoding="UTF-8"?>
<test-suite-result
xmlns='http://www.w3.org/2005/02/query-test-XQTSResult'
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<implementation
name='Qizx'
version='Qizx 2.1'
anonymous-result-column="false">

<organization
name='XMLmind'
website="http://www.xmlmind.com/qizx/"
anonymous="false" />

<submittor
name="Xavier Franc"
email="[see web site]" />

<description>
Qizx is an embeddable XML database engine written in Java.
</description>

<implementation-defined-items>

<implementation-defined-item name="implicitTimezone" spec="XQuery"
value="Can be set through the API. Default is local timezone.">
<description last-mod="2005-04-04">The implicit timezone.</description>
</implementation-defined-item>

</implementation-defined-items>

<features>
<feature
name='Minimum Conformance'
supported='true' />
</features>

<context-properties>
<context-property
name="Default collation"
context-type='static'
value="codepoint." />
<context-property name="Statically known namespaces" context-type="static"
value="prefix x for extension functions, can be augmented through the API and by the Java binding mechanism."/>
</context-properties>

</implementation>

<syntax>XQuery</syntax>

<test-run dateRun='Tue May 20 19:45:59 GMT+01:00 2008'>
<test-suite version="0.7" />
<transformation>
 Some results have been slightly changed because of whitespace issues.
</transformation>
<comparison>
Comparisons as recommended by the guidelines.
Whitespace is stripped before comparison in most cases,
except when 'preserve' is present in the query.
</comparison>
</test-run>

<test-case name='id-insert-expr-01' result='pass' />
<test-case name='id-insert-expr-02' result='pass' />
<test-case name='id-insert-expr-03' result='pass' />
<test-case name='id-insert-expr-04' result='pass' />
<test-case name='id-insert-expr-05' result='pass' />
<test-case name='id-insert-expr-06' result='pass' />
<test-case name='id-insert-expr-07' result='pass' />
<test-case name='id-insert-expr-08' result='pass' />
<test-case name='id-insert-expr-09' result='pass' />
<test-case name='id-insert-expr-010' result='pass' />
<test-case name='id-insert-expr-011' result='pass' />
<test-case name='id-insert-expr-012' result='pass' />
<test-case name='id-insert-expr-013' result='pass' />
<test-case name='id-insert-expr-014' result='pass' />
<test-case name='id-insert-expr-015' result='pass' />
<test-case name='id-insert-expr-016' result='pass' />
<test-case name='id-insert-expr-017' result='pass' />
<test-case name='id-insert-expr-018' result='pass' />
<test-case name='id-insert-expr-019' result='pass' />
<test-case name='id-insert-expr-020' result='pass' />
<test-case name='id-insert-expr-021' result='pass' />
<test-case name='id-insert-expr-022' result='pass' />
<test-case name='id-insert-expr-023' result='pass' />
<test-case name='id-insert-expr-024' result='pass' />
<test-case name='id-insert-expr-025' result='pass' />
<test-case name='id-insert-expr-026' result='pass' />
<test-case name='id-insert-expr-027' result='pass' />
<test-case name='id-insert-expr-028' result='pass' />
<test-case name='id-insert-expr-029' result='pass' />
<test-case name='id-insert-expr-030' result='pass' />
<test-case name='id-insert-expr-031' result='pass' />
<test-case name='id-insert-expr-032' result='pass' />
<test-case name='id-insert-expr-033' result='pass' />
<test-case name='id-insert-expr-034' result='pass' />
<test-case name='id-insert-expr-035' result='pass' />
<test-case name='id-insert-expr-036' result='pass' />
<test-case name='id-insert-expr-037' result='pass' />
<test-case name='id-insert-expr-038' result='pass' />
<test-case name='id-insert-expr-039' result='pass' />
<test-case name='id-insert-expr-040' result='pass' />
<test-case name='id-insert-expr-041' result='pass' />
<test-case name='id-insert-expr-042' result='pass' />
<test-case name='id-insert-expr-043' result='pass' />
<test-case name='id-insert-expr-044' result='pass' />
<test-case name='id-insert-expr-045' result='pass' />
<test-case name='id-insert-expr-046' result='pass' />
<test-case name='id-insert-expr-047' result='pass' />
<test-case name='id-insert-expr-048' result='pass' />
<test-case name='id-insert-expr-049' result='pass' />
<test-case name='id-insert-expr-050' result='pass' />
<test-case name='id-delete-expr-01' result='pass' />
<test-case name='id-delete-expr-02' result='pass' />
<test-case name='id-delete-expr-03' result='pass' />
<test-case name='id-delete-expr-04' result='pass' />
<test-case name='id-delete-expr-05' result='pass' />
<test-case name='id-delete-expr-06' result='pass' />
<test-case name='id-delete-expr-07' result='pass' />
<test-case name='id-delete-expr-08' result='pass' />
<test-case name='id-delete-expr-09' result='pass' />
<test-case name='id-delete-expr-010' result='pass' />
<test-case name='id-delete-expr-011' result='pass' />
<test-case name='id-delete-expr-012' result='pass' />
<test-case name='id-replace-expr-01' result='pass' />
<test-case name='id-replace-expr-02' result='pass' />
<test-case name='id-replace-expr-03' result='pass' />
<test-case name='id-replace-expr-04' result='pass' />
<test-case name='id-replace-expr-05' result='pass' />
<test-case name='id-replace-expr-06' result='pass' />
<test-case name='id-replace-expr-07' result='pass' />
<test-case name='id-replace-expr-08' result='pass' />
<test-case name='id-replace-expr-09' result='pass' />
<test-case name='id-replace-expr-010' result='pass' />
<test-case name='id-replace-expr-011' result='pass' />
<test-case name='id-replace-expr-012' result='pass' />
<test-case name='id-replace-expr-013' result='pass' />
<test-case name='id-replace-expr-014' result='pass' />
<test-case name='id-replace-expr-015' result='pass' />
<test-case name='id-replace-expr-016' result='pass' />
<test-case name='id-replace-expr-017' result='pass' />
<test-case name='id-replace-expr-018' result='pass' />
<test-case name='id-replace-expr-019' result='pass' />
<test-case name='id-replace-expr-020' result='pass' />
<test-case name='id-replace-expr-021' result='pass' />
<test-case name='id-replace-expr-022' result='pass' />
<test-case name='id-replace-expr-023' result='pass' />
<test-case name='id-replace-expr-024' result='pass' />
<test-case name='id-replace-expr-025' result='pass' />
<test-case name='id-replace-expr-026' result='pass' />
<test-case name='id-replace-expr-027' result='pass' />
<test-case name='id-rename-expr-01' result='pass' />
<test-case name='id-rename-expr-02' result='pass' />
<test-case name='id-rename-expr-03' result='pass' />
<test-case name='id-rename-expr-04' result='pass' />
<test-case name='id-rename-expr-05' result='pass' />
<test-case name='id-rename-expr-06' result='pass' />
<test-case name='id-rename-expr-07' result='pass' />
<test-case name='id-rename-expr-08' result='pass' />
<test-case name='id-rename-expr-09' result='pass' />
<test-case name='id-rename-expr-010' result='pass' />
<test-case name='id-rename-expr-011' result='pass' />
<test-case name='id-rename-expr-012' result='pass' />
<test-case name='id-rename-expr-013' result='pass' />
<test-case name='id-rename-expr-014' result='pass' />
<test-case name='id-rename-expr-015' result='pass' />
<test-case name='id-rename-expr-016' result='pass' />
<test-case name='id-rename-expr-017' result='pass' />
<test-case name='id-rename-expr-018' result='pass' />
<test-case name='id-rename-expr-019' result='pass' />
<test-case name='id-rename-expr-020' result='pass' />
<test-case name='id-transform-expr-01' result='pass' />
<test-case name='id-transform-expr-02' result='pass' />
<test-case name='id-transform-expr-03' result='pass' />
<test-case name='id-transform-expr-04' result='pass' />
<test-case name='id-transform-expr-05' result='pass' />
<test-case name='id-transform-expr-06' result='pass' />
<test-case name='id-transform-expr-07' result='pass' />
<test-case name='id-transform-expr-08' result='pass' />
<test-case name='id-transform-expr-09' result='pass' />
<test-case name='id-transform-expr-010' result='pass' />
<test-case name='id-transform-expr-011' result='pass' />
<test-case name='id-transform-expr-012' result='pass' />
<test-case name='id-transform-expr-013' result='pass' />
<test-case name='id-transform-expr-014' result='pass' />
<test-case name='id-transform-expr-015' result='pass' />
<test-case name='id-transform-expr-016' result='pass' />
<test-case name='id-transform-expr-017' result='pass' />
<test-case name='id-transform-expr-018' result='pass' />
<test-case name='id-transform-expr-019' result='pass' />
<test-case name='id-transform-expr-020' result='pass' />
<test-case name='id-transform-expr-021' result='pass' />
<test-case name='id-transform-expr-022' result='pass' />
<test-case name='id-transform-expr-023' result='pass' />
<test-case name='id-transform-expr-024' result='pass' />
<test-case name='id-transform-expr-025' result='pass' />
<test-case name='id-transform-expr-026' result='pass' />
<test-case name='id-transform-expr-027' result='pass' />
<test-case name='id-transform-expr-028' result='pass' />
<test-case name='id-transform-expr-029' result='pass' />
<test-case name='id-transform-expr-030' result='pass' />
<test-case name='id-transform-expr-031' result='pass' />
<test-case name='id-flwor-expr-01' result='pass' />
<test-case name='id-flwor-expr-02' result='pass' />
<test-case name='id-flwor-expr-03' result='pass' />
<test-case name='id-flwor-expr-04' result='pass' />
<test-case name='id-flwor-expr-05' result='pass' />
<test-case name='id-flwor-expr-06' result='pass' />
<test-case name='id-flwor-expr-07' result='pass' />
<test-case name='id-flwor-expr-08' result='pass' />
<test-case name='id-flwor-expr-09' result='pass' />
<test-case name='id-flwor-expr-010' result='pass' />
<test-case name='id-flwor-expr-011' result='pass' />
<test-case name='id-flwor-expr-012' result='pass' />
<test-case name='id-flwor-expr-013' result='pass' />
<test-case name='id-flwor-expr-014' result='pass' />
<test-case name='id-flwor-expr-015' result='pass' />
<test-case name='id-flwor-expr-016' result='pass' />
<test-case name='id-flwor-expr-017' result='pass' />
<test-case name='id-flwor-expr-018' result='pass' />
<test-case name='id-flwor-expr-019' result='pass' />
<test-case name='id-flwor-expr-020' result='pass' />
<test-case name='id-flwor-expr-021' result='pass' />
<test-case name='id-flwor-expr-022' result='pass' />
<test-case name='id-typeswitch-expr-01' result='pass' />
<test-case name='id-typeswitch-expr-02' result='pass' />
<test-case name='id-typeswitch-expr-03' result='pass' />
<test-case name='id-typeswitch-expr-04' result='pass' />
<test-case name='id-typeswitch-expr-05' result='pass' />
<test-case name='id-typeswitch-expr-06' result='pass' />
<test-case name='id-typeswitch-expr-07' result='pass' />
<test-case name='id-typeswitch-expr-08' result='pass' />
<test-case name='id-typeswitch-expr-09' result='pass' />
<test-case name='id-typeswitch-expr-010' result='pass' />
<test-case name='id-typeswitch-expr-011' result='pass' />
<test-case name='id-typeswitch-expr-012' result='pass' />
<test-case name='id-typeswitch-expr-013' result='pass' />
<test-case name='id-typeswitch-expr-014' result='pass' />
<test-case name='id-typeswitch-expr-015' result='pass' />
<test-case name='id-typeswitch-expr-016' result='pass' />
<test-case name='id-typeswitch-expr-017' result='pass' />
<test-case name='id-typeswitch-expr-018' result='pass' />
<test-case name='id-typeswitch-expr-019' result='pass' />
<test-case name='id-typeswitch-expr-020' result='pass' />
<test-case name='id-typeswitch-expr-021' result='pass' />
<test-case name='id-typeswitch-expr-022' result='pass' />
<test-case name='id-typeswitch-expr-023' result='pass' />
<test-case name='id-typeswitch-expr-024' result='pass' />
<test-case name='id-typeswitch-expr-025' result='pass' />
<test-case name='id-typeswitch-expr-026' result='pass' />
<test-case name='id-typeswitch-expr-027' result='pass' />
<test-case name='id-typeswitch-expr-028' result='pass' />
<test-case name='id-typeswitch-expr-029' result='pass' />
<test-case name='id-typeswitch-expr-030' result='pass' />
<test-case name='id-typeswitch-expr-031' result='pass' />
<test-case name='id-typeswitch-expr-032' result='pass' />
<test-case name='id-typeswitch-expr-033' result='pass' />
<test-case name='id-typeswitch-expr-034' result='pass' />
<test-case name='id-typeswitch-expr-035' result='pass' />
<test-case name='id-conditional-expr-01' result='pass' />
<test-case name='id-conditional-expr-02' result='pass' />
<test-case name='id-conditional-expr-03' result='pass' />
<test-case name='id-conditional-expr-04' result='pass' />
<test-case name='id-conditional-expr-05' result='pass' />
<test-case name='id-conditional-expr-06' result='pass' />
<test-case name='id-conditional-expr-07' result='pass' />
<test-case name='id-conditional-expr-08' result='pass' />
<test-case name='id-conditional-expr-09' result='pass' />
<test-case name='id-conditional-expr-010' result='pass' />
<test-case name='id-conditional-expr-011' result='pass' />
<test-case name='id-conditional-expr-012' result='pass' />
<test-case name='id-conditional-expr-013' result='pass' />
<test-case name='id-conditional-expr-014' result='pass' />
<test-case name='id-conditional-expr-015' result='pass' />
<test-case name='id-conditional-expr-016' result='pass' />
<test-case name='id-conditional-expr-017' result='pass' />
<test-case name='id-conditional-expr-018' result='pass' />
<test-case name='id-conditional-expr-019' result='pass' />
<test-case name='id-conditional-expr-020' result='pass' />
<test-case name='id-conditional-expr-021' result='pass' />
<test-case name='id-conditional-expr-022' result='pass' />
<test-case name='id-conditional-expr-023' result='pass' />
<test-case name='id-conditional-expr-024' result='pass' />
<test-case name='id-conditional-expr-025' result='pass' />
<test-case name='id-conditional-expr-026' result='pass' />
<test-case name='id-conditional-expr-027' result='pass' />
<test-case name='id-conditional-expr-028' result='pass' />
<test-case name='id-conditional-expr-029' result='pass' />
<test-case name='id-conditional-expr-030' result='pass' />
<test-case name='id-conditional-expr-031' result='pass' />
<test-case name='id-conditional-expr-032' result='pass' />
<test-case name='id-conditional-expr-033' result='pass' />
<test-case name='id-conditional-expr-034' result='pass' />
<test-case name='id-conditional-expr-035' result='pass' />
<test-case name='id-comma-expr-01' result='pass' />
<test-case name='id-comma-expr-02' result='pass' />
<test-case name='id-comma-expr-03' result='pass' />
<test-case name='id-comma-expr-04' result='pass' />
<test-case name='id-comma-expr-05' result='pass' />
<test-case name='id-comma-expr-06' result='pass' />
<test-case name='id-comma-expr-07' result='pass' />
<test-case name='id-comma-expr-08' result='pass' />
<test-case name='id-comma-expr-09' result='pass' />
<test-case name='id-comma-expr-010' result='pass' />
<test-case name='id-comma-expr-011' result='pass' />
<test-case name='id-comma-expr-012' result='pass' />
<test-case name='id-comma-expr-013' result='pass' />
<test-case name='id-comma-expr-014' result='pass' />
<test-case name='id-comma-expr-015' result='pass' />
<test-case name='id-comma-expr-016' result='pass' />
<test-case name='id-comma-expr-017' result='pass' />
<test-case name='id-comma-expr-018' result='pass' />
<test-case name='id-comma-expr-019' result='pass' />
<test-case name='id-comma-expr-020' result='pass' />
<test-case name='id-comma-expr-021' result='pass' />
<test-case name='id-comma-expr-022' result='pass' />
<test-case name='id-comma-expr-023' result='pass' />
<test-case name='id-comma-expr-024' result='pass' />
<test-case name='id-comma-expr-025' result='pass' />
<test-case name='id-comma-expr-026' result='pass' />
<test-case name='id-comma-expr-027' result='pass' />
<test-case name='id-comma-expr-028' result='pass' />
<test-case name='id-comma-expr-029' result='pass' />
<test-case name='id-comma-expr-030' result='pass' />
<test-case name='id-comma-expr-031' result='pass' />
<test-case name='id-comma-expr-032' result='pass' />
<test-case name='id-comma-expr-033' result='pass' />
<test-case name='id-comma-expr-034' result='pass' />
<test-case name='id-comma-expr-035' result='pass' />
<test-case name='id-function-declaration-01' result='pass' />
<test-case name='id-function-declaration-02' result='pass' />
<test-case name='id-function-declaration-03' result='pass' />
<test-case name='id-function-declaration-04' result='pass' />
<test-case name='id-function-declaration-05' result='pass' />
<test-case name='id-function-declaration-06' result='pass' />
<test-case name='id-function-declaration-07' result='pass' />
<test-case name='id-function-declaration-08' result='pass' />
<test-case name='id-function-declaration-09' result='pass' />
<test-case name='id-function-declaration-010' result='pass' />
<test-case name='id-function-declaration-011' result='pass' />
<test-case name='id-function-declaration-012' result='pass' />
<test-case name='id-function-declaration-013' result='pass' />
<test-case name='id-function-declaration-014' result='pass' />
<test-case name='id-function-call-01' result='pass' />
<test-case name='id-function-call-02' result='pass' />
<test-case name='id-function-call-03' result='pass' />
<test-case name='id-function-call-04' result='pass' />
<test-case name='id-function-call-05' result='pass' />
<test-case name='id-function-call-06' result='pass' />
<test-case name='id-other-expr-01' result='pass' />
<test-case name='id-other-expr-02' result='pass' />
<test-case name='id-other-expr-03' result='pass' />
<test-case name='id-other-expr-04' result='pass' />
<test-case name='id-other-expr-05' result='pass' />
<test-case name='id-other-expr-06' result='pass' />
<test-case name='id-other-expr-07' result='pass' />
<test-case name='id-other-expr-08' result='pass' />
<test-case name='id-other-expr-09' result='pass' />
<test-case name='id-other-expr-010' result='pass' />
<test-case name='id-other-expr-011' result='pass' />
<test-case name='id-other-expr-012' result='pass' />
<test-case name='id-other-expr-013' result='pass' />
<test-case name='id-other-expr-014' result='pass' />
<test-case name='id-other-expr-015' result='pass' />
<test-case name='id-other-expr-016' result='pass' />
<test-case name='id-other-expr-017' result='pass' />
<test-case name='id-other-expr-018' result='pass' />
<test-case name='id-other-expr-019' result='pass' />
<test-case name='id-other-expr-020' result='pass' />
<test-case name='id-other-expr-021' result='pass' />
<test-case name='id-other-expr-022' result='pass' />
<test-case name='id-other-expr-023' result='pass' />
<test-case name='id-other-expr-024' result='pass' />
<test-case name='id-other-expr-025' result='pass' />
<test-case name='id-other-expr-26' result='pass' />
<test-case name='id-other-expr-027' result='pass' />
<test-case name='id-other-expr-028' result='pass' />
<test-case name='id-other-expr-029' result='pass' />
<test-case name='id-other-expr-030' result='pass' />
<test-case name='id-other-expr-031' result='pass' />
<test-case name='id-other-expr-032' result='pass' />
<test-case name='statictyp-xqupd-01' result='pass' />
<test-case name='statictyp-xqupd-02' result='pass' />
<test-case name='statictyp-xqupd-03' result='pass' />
<test-case name='statictyp-xqupd-04' result='pass' />
<test-case name='statictyp-xqupd-05' result='pass' />
<test-case name='statictyp-xqupd-06' result='pass' />
<test-case name='statictyp-xqupd-07' result='pass' />
<test-case name='statictyp-xqupd-08' result='pass' />
<test-case name='statictyp-xqupd-09' result='pass' />
<test-case name='statictyp-xqupd-10' result='pass' />
<test-case name='statictyp-xqupd-11' result='pass' />
<test-case name='statictyp-xqupd-12' result='pass' />
<test-case name='statictyp-xqupd-13' result='pass' />
<test-case name='statictyp-xqupd-14' result='pass' />
<test-case name='statictyp-xqupd-15' result='pass' />
<test-case name='statictyp-xqupd-16' result='pass' />
<test-case name='statictyp-xqupd-17' result='pass' />
<test-case name='statictyp-xqupd-18' result='pass' />
<test-case name='statictyp-xqupd-19' result='pass' />
<test-case name='statictyp-xqupd-20' result='pass' />
<test-case name='statictyp-xqupd-21' result='pass' />
<test-case name='statictyp-xqupd-22' result='pass' />
<test-case name='statictyp-xqupd-23' result='pass' />
<test-case name='statictyp-xqupd-24' result='pass' />
<test-case name='statictyp-xqupd-25' result='pass' />
<test-case name='statictyp-xqupd-26' result='pass' />
<test-case name='statictyp-xqupd-27' result='pass' />
<test-case name='statictyp-xqupd-28' result='pass' />
<test-case name='statictyp-xqupd-29' result='pass' />
<test-case name='statictyp-xqupd-30' result='pass' />
<test-case name='statictyp-xqupd-31' result='pass' />
<test-case name='statictyp-xqupd-32' result='pass' />
<test-case name='statictyp-xqupd-33' result='pass' />
<test-case name='statictyp-xqupd-34' result='pass' />
<test-case name='statictyp-xqupd-35' result='pass' />
<test-case name='statictyp-xqupd-36' result='pass' />
<test-case name='statictyp-xqupd-37' result='pass' />
<test-case name='statictyp-xqupd-38' result='pass' />
<test-case name='statictyp-xqupd-39' result='pass' />
<test-case name='statictyp-xqupd-40' result='pass' />
<test-case name='statictyp-xqupd-41' result='pass' />
<test-case name='statictyp-xqupd-42' result='pass' />
<test-case name='statictyp-xqupd-43' result='pass' />
<test-case name='statictyp-xqupd-44' result='pass' />
<test-case name='statictyp-xqupd-45' result='pass' />
<test-case name='statictyp-xqupd-46' result='pass' />
<test-case name='statictyp-xqupd-47' result='pass' />
<test-case name='statictyp-xqupd-48' result='pass' />
<test-case name='statictyp-xqupd-49' result='pass' />
<test-case name='statictyp-xqupd-50' result='pass' />
<test-case name='statictyp-xqupd-51' result='pass' />
<test-case name='statictyp-xqupd-52' result='pass' />
<test-case name='statictyp-xqupd-53' result='pass' />
<test-case name='statictyp-xqupd-54' result='pass' />
<test-case name='statictyp-xqupd-55' result='pass' />
<test-case name='statictyp-xqupd-56' result='pass' />
<test-case name='statictyp-xqupd-57' result='pass' />
<test-case name='statictyp-xqupd-58' result='pass' />
<test-case name='statictyp-xqupd-59' result='pass' />
<test-case name='statictyp-xqupd-60' result='pass' />
<test-case name='relational-data-q1' result='pass' />
<test-case name='relational-data-q2' result='pass' />
<test-case name='relational-data-q3' result='pass' />
<test-case name='relational-data-q4' result='pass' />
<test-case name='relational-data-q5-1' result='pass' />
<test-case name='relational-data-q5-2' result='pass' />
<test-case name='relational-data-q6-1' result='pass' />
<test-case name='relational-data-q6-2' result='pass' />
<test-case name='relational-data-q7' result='pass' />
<test-case name='relational-data-q8' result='pass' />
<test-case name='relational-data-q9' result='pass' />
<test-case name='address-book-q1' result='pass' />
<test-case name='soap-q1' result='pass' />
<test-case name='namespaces-q1' result='pass' />
<test-case name='parts-q1' result='pass' />
<test-case name='parts-q2' result='pass' />
<test-case name='parts-q3-1' result='pass' />
<test-case name='parts-q3-2' result='pass' />
<test-case name='parts-q4-1' result='pass' />
<test-case name='parts-q4-2' result='pass' />
<test-case name='parts-q6' result='pass' />
<test-case name='nil-q1' result='pass' />
<test-case name='valskip-ins-001' result='fail' />
<test-case name='valskip-ins-002' result='fail' />
<test-case name='valskip-ins-003' result='fail' />
<test-case name='valskip-ins-004' result='fail' />
<test-case name='valskip-ins-005' result='fail' />
<test-case name='valskip-ins-006' result='fail' />
<test-case name='valskip-ins-007' result='fail' />
<test-case name='valskip-ins-008' result='fail' />
<test-case name='valskip-ins-009' result='fail' />
<test-case name='valskip-ins-010' result='fail' />
<test-case name='valskip-ins-011' result='fail' />
<test-case name='valskip-ins-012' result='fail' />
<test-case name='valskip-ins-013' result='fail' />
<test-case name='valskip-ins-014' result='fail' />
<test-case name='valskip-del-001' result='fail' />
<test-case name='valskip-del-002' result='fail' />
<test-case name='valskip-del-003' result='fail' />
<test-case name='valskip-del-004' result='fail' />
<test-case name='valskip-del-005' result='fail' />
<test-case name='valskip-ren-001' result='fail' />
<test-case name='valskip-ren-002' result='fail' />
<test-case name='valskip-ren-003' result='fail' />
<test-case name='valskip-ren-004' result='pass' />
<test-case name='valskip-ren-005' result='fail' />
<test-case name='valskip-ren-006' result='pass' />
<test-case name='valskip-repnode-001' result='fail' />
<test-case name='valskip-repnode-002' result='fail' />
<test-case name='valskip-repnode-003' result='fail' />
<test-case name='valskip-repnode-004' result='fail' />
<test-case name='valskip-repnode-005' result='fail' />
<test-case name='valskip-repnode-006' result='fail' />
<test-case name='valstrict-del-001' result='pass' />
<test-case name='valstrict-del-002' result='fail' />
<test-case name='valstrict-del-003' result='pass' />
<test-case name='valstrict-del-004' result='fail' />
<test-case name='valstrict-ins-001' result='pass' />
<test-case name='valstrict-ins-002' result='pass' />
<test-case name='valstrict-ins-003' result='fail' />
<test-case name='valstrict-ins-004' result='pass' />
<test-case name='valstrict-ins-005' result='fail' />
<test-case name='valstrict-ins-006' result='pass' />
<test-case name='valstrict-ins-007' result='fail' />
<test-case name='valstrict-ren-001' result='pass' />
<test-case name='valstrict-ren-002' result='pass' />
<test-case name='valstrict-ren-003' result='fail' />
<test-case name='valstrict-repnode-001' result='pass' />
<test-case name='valstrict-repnode-002' result='pass' />
<test-case name='valstrict-repnode-003' result='fail' />
<test-case name='valtrans-ins-001' result='pass' />
<test-case name='valtrans-ins-002' result='fail' />
<test-case name='valtrans-ins-003' result='pass' />
<test-case name='put-001' result='fail' />
</test-suite-result>

Re: Remarks and questions about XQ Update Facility test suite

2008-04-21T15:29:10Z

Andrew Eisenberg wrote:
>
> > - it would be nice to have a zip distribution of the XQUF TS.
>
> I'll ask Jonathan to comment on this.

First off, Xavier, my apologies, I just check and I see that I failed to
respond to an earlier inquiry from you.

So far, I've been resisting suggestions to create a zip distribution
because most developers are able to use source code control systems,
which are a better way to develop a test suite collaboratively, and I
don't want to have to worry about whether a zip distribution is out of
sync with the source code repository. If enough people give me a good
reason that the source code control system does not work for them, I may
change my mind, but I'm reluctant to provide a zip without a really good
reason.

> > - Is there a plan to publish a result page like for XQuery ?
>
> You'll find our early results in
> http://dev.w3.org/2007/xquery-update-10-test-suite/results/.

And your results would be very welcome.

Jonathan

Re: Remarks and questions about XQ Update Facility test suite

2008-04-21T14:38:09Z

public-xqts-comments-request@... wrote on 04/17/2008 01:29:57 PM: > - Apparently there are some issues with the files in directory > xquery-update-10-test-suite/ReportingResults of the XQUF test suite. > It seems that these files are simple copies of the standard XQuery test > suite rather then what is mentioned on the web site (XQUTSReport.html, > XQUTSReportSimple.html, XQUTSResult.xsd etc).
I'm not sure what you mean. The files in this directory were updated about a month ago.

> - it would be nice to have a zip distribution of the XQUF TS.
I'll ask Jonathan to comment on this.

> - Is there a plan to publish a result page like for XQuery ?

You'll find our early results in http://dev.w3.org/2007/xquery-update-10-test-suite/results/.

> - Or to integrate this as an optional module of the standard test suite ?
We're keeping these results separate for now. This might change when we get further along with XQuery 1.1.

--------------------
Andrew Eisenberg
IBM
4 Technology Park Drive
Westford, MA 01886

andrew.eisenberg@...
Phone: 978-399-5158 Fax: 978-399-7012

Remarks and questions about XQ Update Facility test suite

2008-04-17T10:29:57Z

Hello all,

- Apparently there are some issues with the files in directory
xquery-update-10-test-suite/ReportingResults of the XQUF test suite.
It seems that these files are simple copies of the standard XQuery test
suite rather then what is mentioned on the web site (XQUTSReport.html,
XQUTSReportSimple.html, XQUTSResult.xsd etc).

- it would be nice to have a zip distribution of the XQUF TS.

- Is there a plan to publish a result page like for XQuery ?
- Or to integrate this as an optional module of the standard test suite ?

Cheers
Xavier

Re: x.query update

2007-12-18T13:36:44Z

Hello Schneur,

The XQuery Update Facility Last Call Working Draft was published on Aug. 28, 2007 [1]. We have recently published an early draft of the XQuery Update Test Suite [2].

We haven't started listing XQuery Update implementations on the XML Query public page [3] quite yet. We should probably do so shortly.

I have noticed that XQilla claims support for the XQuery Update Facility [4]. Perhaps this is what you are looking for.

-- Andrew

[1] XQuery Update Facility 1.0, http://www.w3.org/TR/xquery-update-10/.

[2] XQuery Update Facility Test Suite, http://dev.w3.org/cvsweb/~checkout~/2007/xquery-update-10-test-suite/Overview.html.

[3] W3C XML Query (XQuery), List of XQuery Implementations, http://www.w3.org/XML/Query/#implementations.

[4] XQilla : HomePage, http://xqilla.sourceforge.net/HomePage.

--------------------
Andrew Eisenberg
IBM
4 Technology Park Drive
Westford, MA 01886

andrew.eisenberg@...
Phone: 978-399-5158 Fax: 978-399-7012

schneur <schneur1@...>
Sent by: public-xqts-comments-request@...

12/16/2007 07:54 AM

To	public-xqts-comments@...
cc
Subject	x.query update

Hi;

is there any clear standard on the x.query (not XML:DB update api) update proposal(more then one implementation)?, and is their any implementation of a x query update capacity in a open source xml native DB?

thanks for your kind help schneur

x.query update

2007-12-16T04:54:09Z

war

2007-09-24T20:45:24Z

NEW YORK (Hollywood Reporter) - The premiere of Ken Burns' new
documentary series "The War" brought in 7.3 million
viewers Sunday night, PBS said.

The first episode of the multipart documentary averaged a 5.0 household
rating/7 share in the top 56 "metered" markets,
according to preliminary estimates released Monday by Nielsen Media
Research.

That is on par with the opener of Burns' 1994 highly rated documentary
series for PBS' "Baseball," which had a 5.1 household
rating. (The 1990 premiere of Burns' "The Civil War" brought in a 9.0
rating.)

"The War" ran between 8 p.m. and 10:30 p.m. against season premieres on
CBS and Fox, as well as a heavily watched
"Sunday Night Football" matchup between the Dallas Cowboys and the
Chicago Bears. At least 15.5 million people tuned in
for some of the telecast, PBS said.

With the addition of a second airing nationwide, the first episode
averaged 18.7 million viewers total, PBS said. The first
episode was particularly strong in such markets as Minneapolis-St. Paul,
Seattle, San Francisco and New York.

http://www.wholeearthphonesex.com
http://www.phone-sex-psychologist.com
http://www.phone-sex-hypnosis.com
http://www.phone-sex-dictionary.com
http://www.phone-sex-handjobs.com
http://www.your-account.info
http://www.freephonesex.org
http://www.1800phonesex.net
http://www.1on1phonesex.com
http://www.phonesexphone.com
http://www.hotphone.com
http://www.xxx-rated.com

docu

2007-09-24T20:44:23Z

Status update for XQTS 1.0.3

2007-05-23T05:35:32Z

Hello everyone!

One might wonder, with valid reason, when the next release of XQTS will be
out. The testing task force will try to make this into "soon."

Beyond the couple of open reports still remaining, we're working on getting
the XMark bench suite included in the XQTS, to expand our range of realistic
queries. Hopefully it will make it easier for implementors to improve &
verify their interoperability.

The XMark files are ready to go. In fact, all queued in my CVS working
directory, but we need a final ok from the lawyers to make sure no one gets
into trouble.

Though, XQTS_current.zip has recently been updated in CVS and does by now
contain a great deal of fixes. And as of yesterday new tests in murky and
tricky areas. So feel welcome to test it out and report back.

Cheers,

Frans

Re: XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

2006-08-22T06:49:25Z

On Tuesday 22 August 2006 12:17, Margaret Gruen-Kerr wrote:
> Frans -
> You are right, but I am afraid it does not answer my question, I will try
> to rephrase it: Should a node name test on an undefined context return
> differently than a nodename test on a empty sequence?

Yes, the former is a type error(e.g, it doesn't return at all) while the
latter do return.

However, note that it is significant what the empty sequence originates from
in "a nodename test on a empty sequence". Evaluating b in a/b is ok if `a'
evaluates to the empty sequence(subsequently, b will as well evaluate to the
empty sequence). When evaluating only `b'(therefore implicitly accessing the
focus), the focus is either undefined(which it is inside a user function, for
example), or be defined. However, the focus cannot never be the empty
sequence.

See 2.1.2 Dynamic Context:

[Definition: The context item is the item currently being processed. An item
is either an atomic value or a node.] // NB, this is cardinality exactly-one

[Definition: The context position is the position of the context item within
the sequence of items currently being processed.] It changes whenever the
context item changes. When the focus is defined, the value of the context
position is an integer greater than zero.
[Definition: The context size is the number of items in the sequence of items
currently being processed.] Its value is always an integer greater than zero.

> The correct result
> for a nodename selection on a function returning the empty sequence is the
> empty sequence (the context size is not greater than zero)
> noResult()/nodeName==>empty sequence

Yes, assuming the function manages to evaluate to the empty sequence without
errors. It is ok for a axis step to evaluate to the empty sequence.

> From reading the spec. is it not acceptable for a nodename selection on an
> undefined context to return the empty sequence also?

No, if any expression such as a node test accesses the focus and it is
undefined, XPDY0002 must be raised.

Perhaps the key to this is that the focus never can be the empty sequence.

Cheers,

Frans

>
>
> ... Margaret A. Grün-Kerr
> ... Quality Assurance Engineer
> ... Altova GmbH
>
> ===================================================================
> Altova® accelerates application development and data management
> projects with software and solutions that enhance productivity
> and maximize results. Uncover why Altova is the preferred choice of
> over 2 million developers worldwide! Look into www.altova.com today
> XML Suite: XMLSpy MapForce StyleVision SemanticWorks SchemaAgent
> Developer Tools: UModel DiffDog FREE: Authentic, AltovaXML engine
> NEW in v2006: Advanced standards compliance, XSLT 2.0, XPath 2.0,
> XQuery 1.0, Legacy text file parsing, Web Services implementation,
> Semantic Web, RDF / OWL editor, VS.Net 2005 & Eclipse 3.1 support
> UML 2.1 support, UML Sequence Diagrams, C# code-gen and round-trip
> ===================================================================
>
> Altova, XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent,
> UModel, DiffDog, ACXE, AltovaXML, and Authentic are trademarks
> and/or registered trademarks of Altova GmbH in the United States of
> America, the European Union, and numerous other countries.
> The information transmitted in this message and/or as an attachment
> to it is intended only for the person or entity to which it is
> addressed and may contain confidential and/or privileged material.
> Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons
> or entities other than the intended recipient is prohibited. If you
> received this in error, please contact the sender and delete the
> material from any computer. Altova GmbH and Altova, Inc. do not
> accept legal responsibility for the contents of this message. Any
> views or opinions presented are solely those of the author and do
> not necessarily represent those of Altova GmbH and Altova, Inc.
> unless otherwise specifically stated. Thank you!
>
>
> -----Original Message-----
> From: Frans Englich [mailto:englich@...]
> Sent: August 22, 2006 13:01
> To: Margaret Grün-Kerr (QA)
> Cc: public-xqts-comments@...
> Subject: Re: XQTS - Test externalcontextitem-1.xq, nodename selection on an
> undefined context same as on empty sequence
>
> On Tuesday 22 August 2006 09:25, Margaret Gruen-Kerr wrote:
>
> Hello Margaret,
>
> > The test externalcontextitem-1.xq performs a nodename selection with no
> > context item. The reference result is the error XPDY0002. I couldn't find
> > a clear answer in the spec why a node selection on an empty sequence
> > (which implies no context item) return the empty seq. and the node
> > selection with no context item returns an error. It's clear why functions
> > that try to access the context item, report an error when there is no
> > context item, however not when a nodename selection is performed.
>
> Inside user functions the focus is undefined. See 3.1.5 Function Calls step
> 4:
>
> <quote>
> During evaluation of a function body, the focus (context item, context
> position, and context size) is undefined, except where it is defined by
> some expression inside the function body.
> </quote>
>
> I hope I am correct and that it helps.
>
>
> Cheers,
>
> Frans

RE: XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

2006-08-22T06:17:45Z

RE: XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

Frans -
You are right, but I am afraid it does not answer my question, I will try to rephrase it:
Should a node name test on an undefined context return differently than a nodename test on a empty sequence?
The correct result for a nodename selection on a function returning the empty sequence is the empty sequence (the context size is not greater than zero)

noResult()/nodeName==>empty sequence

From reading the spec. is it not acceptable for a nodename selection on an undefined context to return the empty sequence also?

... Margaret A. Grün-Kerr
... Quality Assurance Engineer
... Altova GmbH

===================================================================
Altova® accelerates application development and data management
projects with software and solutions that enhance productivity
and maximize results. Uncover why Altova is the preferred choice of
over 2 million developers worldwide! Look into www.altova.com today
XML Suite: XMLSpy MapForce StyleVision SemanticWorks SchemaAgent
Developer Tools: UModel DiffDog FREE: Authentic, AltovaXML engine
NEW in v2006: Advanced standards compliance, XSLT 2.0, XPath 2.0,
XQuery 1.0, Legacy text file parsing, Web Services implementation,
Semantic Web, RDF / OWL editor, VS.Net 2005 & Eclipse 3.1 support
UML 2.1 support, UML Sequence Diagrams, C# code-gen and round-trip
===================================================================

Altova, XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent,
UModel, DiffDog, ACXE, AltovaXML, and Authentic are trademarks
and/or registered trademarks of Altova GmbH in the United States of
America, the European Union, and numerous other countries.
The information transmitted in this message and/or as an attachment
to it is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. Altova GmbH and Altova, Inc. do not
accept legal responsibility for the contents of this message. Any
views or opinions presented are solely those of the author and do
not necessarily represent those of Altova GmbH and Altova, Inc.
unless otherwise specifically stated. Thank you!

-----Original Message-----
From: Frans Englich [englich@...]
Sent: August 22, 2006 13:01
To: Margaret Grün-Kerr (QA)
Cc: public-xqts-comments@...
Subject: Re: XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

On Tuesday 22 August 2006 09:25, Margaret Gruen-Kerr wrote:

Hello Margaret,

> The test externalcontextitem-1.xq performs a nodename selection with no
> context item. The reference result is the error XPDY0002. I couldn't find a
> clear answer in the spec why a node selection on an empty sequence (which
> implies no context item) return the empty seq. and the node selection with
> no context item returns an error. It's clear why functions that try to
> access the context item, report an error when there is no context item,
> however not when a nodename selection is performed.

Inside user functions the focus is undefined. See 3.1.5 Function Calls step 4:

<quote>
During evaluation of a function body, the focus (context item, context
position, and context size) is undefined, except where it is defined by some
expression inside the function body.
</quote>

I hope I am correct and that it helps.

Cheers,

Frans

Re: XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

2006-08-22T04:47:10Z

On Tuesday 22 August 2006 09:25, Margaret Gruen-Kerr wrote:

Hello Margaret,

> The test externalcontextitem-1.xq performs a nodename selection with no
> context item. The reference result is the error XPDY0002. I couldn't find a
> clear answer in the spec why a node selection on an empty sequence (which
> implies no context item) return the empty seq. and the node selection with
> no context item returns an error. It's clear why functions that try to
> access the context item, report an error when there is no context item,
> however not when a nodename selection is performed.

Inside user functions the focus is undefined. See 3.1.5 Function Calls step 4:

<quote>
During evaluation of a function body, the focus (context item, context
position, and context size) is undefined, except where it is defined by some
expression inside the function body.
</quote>

I hope I am correct and that it helps.

Cheers,

Frans

XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

2006-08-22T03:25:12Z

XQTS - Test externalcontextitem-1.xq, nodename selection on an undefined context same as on empty sequence

The test externalcontextitem-1.xq performs a nodename selection with no context item. The reference result is the error XPDY0002.

I couldn't find a clear answer in the spec why a node selection on an empty sequence (which implies no context item) return the empty seq. and the node selection with no context item returns an error.

It's clear why functions that try to access the context item, report an error when there is no context item, however not when a nodename selection is performed.

Regards Margaret
... Margaret A. Grün-Kerr
... Quality Assurance Engineer
... Altova GmbH

===================================================================
Altova® accelerates application development and data management
projects with software and solutions that enhance productivity
and maximize results. Uncover why Altova is the preferred choice of
over 2 million developers worldwide! Look into www.altova.com today
XML Suite: XMLSpy MapForce StyleVision SemanticWorks SchemaAgent
Developer Tools: UModel DiffDog FREE: Authentic, AltovaXML engine
NEW in v2006: Advanced standards compliance, XSLT 2.0, XPath 2.0,
XQuery 1.0, Legacy text file parsing, Web Services implementation,
Semantic Web, RDF / OWL editor, VS.Net 2005 & Eclipse 3.1 support
UML 2.1 support, UML Sequence Diagrams, C# code-gen and round-trip
===================================================================

Altova, XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent,
UModel, DiffDog, ACXE, AltovaXML, and Authentic are trademarks
and/or registered trademarks of Altova GmbH in the United States of
America, the European Union, and numerous other countries.
The information transmitted in this message and/or as an attachment
to it is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. Altova GmbH and Altova, Inc. do not
accept legal responsibility for the contents of this message. Any
views or opinions presented are solely those of the author and do
not necessarily represent those of Altova GmbH and Altova, Inc.
unless otherwise specifically stated. Thank you!

Public access to the CVS repository

2006-07-17T13:24:57Z

Hi everyone,

Just in case anyone has missed it:

Public access to the CVS repository do exist, and has done so since the 0.9.4
release. The instructions for this can be found in the section
called "Accessing our Source Files" in this document:

http://www.w3.org/XML/Query/test-suite/

For example, the file PublicPagesStagingArea/XQTS_current.zip contains the
packaging of the tests the task force works with, and is updated regularly.

I know many are aware of this. However, for some it was a surprise so I
thought dropping this note could possibly be useful.

(Personal comment.)

Regards,

Frans

RE: xqts -Schema Import without location hint

2006-07-17T07:02:58Z

RE: xqts -Schema Import without location hint

I found the link from the URI's to the schemas under //sources/schema in the xqtscatalog.xml. I will continue on my path through this test suite (and next time wait till Tuesday before writing about things lost on a Monday).

regards
Margaret

... Margaret A. Grün-Kerr
... Quality Assurance Engineer
... Altova GmbH
_____________________________________________
From: Margaret Grün-Kerr (QA)
Sent:   July 17, 2006 14:10
To:     'public-xqts-comments@...'
Subject:        xqts -Schema Import without location hint

Following test case:
   (: Name: predicates-1:)
    (: Description: Evaluation of a simple predicate with a "true" value (uses "fn:true").:)
    (: insert-start :)
    import schema namespace atomic="http://www.w3.org/XQueryTest";
    declare variable $input-context1 external;
    (: insert-end :)

($input-context1//atomic:integer[fn:true()])

The transform does not provide a name for the imported schema. In the test catalogue I failed to find a further description of where to look. - In this case it should be a [err:XQST0059] if the implementation is not able to process a schema import by finding a valid schema with the specified target namespace."

I suspect that I have missed an essential piece of information about where to look for schemas - can someone help me out?

... Margaret A. Grün-Kerr
... Quality Assurance Engineer
... Altova GmbH

===================================================================
Altova® accelerates application development and data management
projects with software and solutions that enhance productivity
and maximize results. Uncover why Altova is the preferred choice of
over 2 million developers worldwide! Look into www.altova.com today
XML Suite: XMLSpy MapForce StyleVision SemanticWorks SchemaAgent
Developer Tools: UModel DiffDog FREE: Authentic, AltovaXML engine
NEW in v2006: Advanced standards compliance, XSLT 2.0, XPath 2.0,
XQuery 1.0, Legacy text file parsing, Web Services implementation,
Semantic Web, RDF / OWL editor, VS.Net 2005 & Eclipse 3.1 support
UML 2.1 support, UML Sequence Diagrams, C# code-gen and round-trip
===================================================================

Altova, XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent,
UModel, DiffDog, ACXE, AltovaXML, and Authentic are trademarks
and/or registered trademarks of Altova GmbH in the United States of
America, the European Union, and numerous other countries.
The information transmitted in this message and/or as an attachment
to it is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. Altova GmbH and Altova, Inc. do not
accept legal responsibility for the contents of this message. Any
views or opinions presented are solely those of the author and do
not necessarily represent those of Altova GmbH and Altova, Inc.
unless otherwise specifically stated. Thank you!

xqts -Schema Import without location hint

2006-07-17T06:10:10Z

xqts -Schema Import without location hint

($input-context1//atomic:integer[fn:true()])

I suspect that I have missed an essential piece of information about where to look for schemas - can someone help me out?

Re: Schema imports in MinimalConformance

2006-07-15T15:54:41Z

On Jul 15, 2006, at 2:46 PM, David Carlisle wrote:

>
>
> [Note I'm not in the Working Group, just a fellow Test suite user]
>
>> There are still many "import schema" declarations in
>> MinimalConformance
>> tests (around 250, nearly 2%).
>>
>
> In addition to that there are many more which don't explictly import a
> schema but have hidden dependency on schema support as the expected
> result files assume that the input tree has type annotations from
> schema
> validation.
>
> I've argued often that all these schema dependencies should be
> removed.
>
>> These tests will always fail with an implementation that does not
>> support Schema:
>
> This isn't strictly true as the test suite guidelines allow you to
> change the schema import to a namespace declaration before running the
> test. So it is possible to pass some of those tests.
> http://www.w3.org/XML/Query/test-suite/Guidelines%20for%20Running%
> 20the%20XML%20Query%20Test%20Suite.html
>
>> This declaration can be customized in one of the following
>> three ways:
>>
>> 1. Unchanged: use schema import as indicated in the original query
>> 2. Remove the schema import declaration from the query, and add
>> namespace declaration using same name and URI to statically known
>> namespaces before the query is executed.
>> 3. Replace schema import with namespace declaration using same
>> name
>> and URI.
>
>
>
> This licence to change the query text is not particularly helpful
> though,
> and I strongly urge that it be _removed_ from the guidelines.
>
> See bug
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=2666
> for the most recent of several bug reports in this area.
>
> If changing the schema import to a namespace declaration allows the
> test
> to run correctly then the schema dependency is spurious, so the test
> should be changed as distributed just to use a namespace declaration.
>
> If changing the schema import to a namespace declaration causes the
> test to fail (as it requires type or element declarations) then
> suggesting that implementors make this change before running the
> test is
> just misleading and unhelpful. The test needs to be moved to the
> optional schema import section of the test suite.
>
>
> David

Well said, thanks!
Wolfgang.

Re: Schema imports in MinimalConformance

2006-07-15T15:46:30Z

[Note I'm not in the Working Group, just a fellow Test suite user]

> There are still many "import schema" declarations in MinimalConformance
> tests (around 250, nearly 2%).
>

In addition to that there are many more which don't explictly import a
schema but have hidden dependency on schema support as the expected
result files assume that the input tree has type annotations from schema
validation.

I've argued often that all these schema dependencies should be removed.

> These tests will always fail with an implementation that does not
> support Schema:

This isn't strictly true as the test suite guidelines allow you to
change the schema import to a namespace declaration before running the
test. So it is possible to pass some of those tests.
http://www.w3.org/XML/Query/test-suite/Guidelines%20for%20Running%20the%20XML%20Query%20Test%20Suite.html

> This declaration can be customized in one of the following three ways:
>
> 1. Unchanged: use schema import as indicated in the original query
> 2. Remove the schema import declaration from the query, and add
> namespace declaration using same name and URI to statically known
> namespaces before the query is executed.
> 3. Replace schema import with namespace declaration using same name
> and URI.

This licence to change the query text is not particularly helpful though,
and I strongly urge that it be _removed_ from the guidelines.

See bug
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2666
for the most recent of several bug reports in this area.

If changing the schema import to a namespace declaration allows the test
to run correctly then the schema dependency is spurious, so the test
should be changed as distributed just to use a namespace declaration.

If changing the schema import to a namespace declaration causes the
test to fail (as it requires type or element declarations) then
suggesting that implementors make this change before running the test is
just misleading and unhelpful. The test needs to be moved to the
optional schema import section of the test suite.

David

Re: Schema imports in MinimalConformance

2006-07-14T17:26:27Z

On Friday 14 July 2006 23:12, Wolfgang Hoschek wrote:
> What's the rationale for making a 1.0 release if it contains a long
> laundry list of known bugs, going back all the way to 0.8.0? (e.g.
> many unresolved whitespace issues, as of yesterday). 1.0 will be
> interpreted as a call for conformance, and I'd rather not conform to
> a buggy test suite. Why not call it 0.9.5? or 1.0-beta1?

Personally I think your comment has merit. Labeling it 0.9.5 is a whole
different thing compared to 1.0, as outlined.

I can't comment on this as whole(because I don't have insight in the full
scope, such as the impact of changing the road map and dead lines) so I'll
leave this to Andrew for replying.

Thanks for asking "why?"!

(Personal response.)

Frans

Re: Schema imports in MinimalConformance

2006-07-14T17:12:30Z

What's the rationale for making a 1.0 release if it contains a long
laundry list of known bugs, going back all the way to 0.8.0? (e.g.
many unresolved whitespace issues, as of yesterday). 1.0 will be
interpreted as a call for conformance, and I'd rather not conform to
a buggy test suite. Why not call it 0.9.5? or 1.0-beta1?

Wolfgang.

On Jul 14, 2006, at 4:12 PM, Frans Englich wrote:

>
> On Thursday 13 July 2006 22:50, Xavier Franc wrote:
>> Dear XQTS developers,
>>
>> There are still many "import schema" declarations in
>> MinimalConformance
>> tests (around 250, nearly 2%).
>
> Yes, it seems to be this one:
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=2666
>
>> These tests will always fail with an implementation that does not
>> support Schema:
>> "If an XQuery implementation does not support the Schema Import
>> Feature,
>> it MUST raise a static error [err:XQST0009] if it encounters a schema
>> import."
>>
>> IMHO those tests should be moved into the "Optional" part, rather
>> than
>> be adorned with an "expected-error" clause.
>>
>> I am looking forward to seeing this done in the 1.0 version.
>
> Unfortunately I must say it's highly unlikely this will be fixed in
> 1.0. Yes,
> the issue has been open for long, and I would also very much like
> to see it
> fixed.
>
> The reason is that we(the test suite task force) have problem
> getting in
> contact with all our members. Vacations pokes holes in work flow
> this time of
> year.
>
> Hopefully, it will be fixed in a bug fix release that has been
> suggested to
> follow the 1.0 release.
>
>> PS: I intentionally dont add a bug into bugzilla: I am not
>> comfortable
>> with this tool, and I think it is up to the
>> XQTS developers to manage the bug database. Furthermore there are
>> already several reports concerning this topic.
>
> You are of course very welcome to use this list. Many find using
> the bug
> database practical. Let us know if there's any trouble you have so
> we can
> help, if you like. But again, you're welcome to use this list.
>
> (Personal response.)
>
>
> Regards,
>
> Frans
>

Re: Schema imports in MinimalConformance

2006-07-14T17:00:20Z

On Thursday 13 July 2006 22:50, Xavier Franc wrote:
> Dear XQTS developers,
>
> There are still many "import schema" declarations in MinimalConformance
> tests (around 250, nearly 2%).

Yes, it seems to be this one:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2666

> These tests will always fail with an implementation that does not
> support Schema:
> "If an XQuery implementation does not support the Schema Import Feature,
> it MUST raise a static error [err:XQST0009] if it encounters a schema
> import."
>
> IMHO those tests should be moved into the "Optional" part, rather than
> be adorned with an "expected-error" clause.
>
> I am looking forward to seeing this done in the 1.0 version.

Unfortunately I must say it's highly unlikely this will be fixed in 1.0. Yes,
the issue has been open for long, and I would also very much like to see it
fixed.

The reason is that we(the test suite task force) have problem getting in
contact with all our members. Vacations pokes holes in work flow this time of
year.

Hopefully, it will be fixed in a bug fix release that has been suggested to
follow the 1.0 release.

> PS: I intentionally dont add a bug into bugzilla: I am not comfortable
> with this tool, and I think it is up to the
> XQTS developers to manage the bug database. Furthermore there are
> already several reports concerning this topic.

You are of course very welcome to use this list. Many find using the bug
database practical. Let us know if there's any trouble you have so we can
help, if you like. But again, you're welcome to use this list.

(Personal response.)

Regards,

Frans

Re: Xavier's Message to XQTS

2006-07-14T16:22:06Z

On Friday 14 July 2006 22:11, Liam Quin wrote:
> Xavier Franc sent a message that was too large; I forwarded
> it to w3c-archive.

I found this:

http://lists.w3.org/Archives/Member/w3c-archive/2006Jul/0069.html

From what I can tell, that is your mail with Xavier Franc's message body as
attachment to your mail. I don't see any attachment on his mail, or anything
else that would make it large.

Note that Xavier previously posted "Schema imports in MinimalConformance" on
this list, and that post seems rather similar to the one in w3c-archive.

What am I missing?

Cheers,

Frans

Xavier's Message to XQTS

2006-07-14T16:11:21Z

Xavier Franc sent a message that was too large; I forwarded
it to w3c-archive.

Liam

--
Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/
http://www.holoweb.net/~liam/ * http://www.fromoldbooks.org/

Schema imports in MinimalConformance

2006-07-13T16:50:16Z

Dear XQTS developers,

There are still many "import schema" declarations in MinimalConformance
tests (around 250, nearly 2%).

These tests will always fail with an implementation that does not
support Schema:
"If an XQuery implementation does not support the Schema Import Feature,
it MUST raise a static error [err:XQST0009] if it encounters a schema
import."

IMHO those tests should be moved into the "Optional" part, rather than
be adorned with an "expected-error" clause.

I am looking forward to seeing this done in the 1.0 version.

Best regards.

PS: I intentionally dont add a bug into bugzilla: I am not comfortable
with this tool, and I think it is up to the
XQTS developers to manage the bug database. Furthermore there are
already several reports concerning this topic.

Re: Do you plan an 0.9.1 release?

2006-05-02T13:38:56Z

On Tuesday 02 May 2006 19:22, Andrew Eisenberg wrote:
> We are planning an interim release, XQTS 0.9.4, sometime around May 12.
>
> We are still working on providing public CVS access to source files. I
> hope to have this in place when the interim release goes out.

Cool, thanks for the update!

Frans

Re: Do you plan an 0.9.1 release?

2006-05-02T13:22:20Z

We are planning an interim release, XQTS 0.9.4, sometime around May 12.

We are still working on providing public CVS access to source files. I hope to have this in place when the interim release goes out.

-- Andrew

--------------------
Andrew Eisenberg
IBM
4 Technology Park Drive
Westford, MA 01886

andrew.eisenberg@...
Phone: 978-399-5158 Fax: 978-399-7012

Frans Englich <englich@...>
Sent by: public-xqts-comments-request@...

04/30/2006 06:31 PM

To	public-xqts-comments@...
cc
Subject	Do you plan an 0.9.1 release?

Hi, Do you plan a minor bug fix release for 0.9.0? To me there seem to be a relatively big amount of invalid tests, which I think would be a pity if they stayed all until the release of XQTS 1.0. Public CVS access didn't work out? That would otherwise help a lot in nailing test cases. It's quite a heavy machinery to do full XQTS release just to detect some cases are incorrect. For example, I think that many of the invalid encoding tests could have been caught if people had CVS access. Regards, Frans

Do you plan an 0.9.1 release?

2006-04-30T16:19:30Z

Hi,

Do you plan a minor bug fix release for 0.9.0? To me there seem to be a
relatively big amount of invalid tests, which I think would be a pity if they
stayed all until the release of XQTS 1.0.

Public CVS access didn't work out? That would otherwise help a lot in nailing
test cases. It's quite a heavy machinery to do full XQTS release just to
detect some cases are incorrect. For example, I think that many of the
invalid encoding tests could have been caught if people had CVS access.

Regards,

Frans

Re: Inspect/implementation defined order fn-trace-*

2006-04-25T06:50:22Z

Just to be clear, I said

me> Having said that, I think that this interpretation is really justified
me> by the Catalogue markup

But of course meant

Having said that, I think that this interpretation is NOT really justified
^^^
by the Catalogue markup

> As I see it, there is nothing to verify
> since an implementation can do anything it chooses to.

I agree that from a conformance point of view trace() can be a no-op so
that the only thing that should be tested as part of a conformance or
interoperability test is the query result (which can be mechanically
tested with xml comparison). However officially the W3C doesn't go in
for conformance testing of particular systems and the purpose of the
suite as far as getting out of CR is concerned is to show that the
features are implementable, and as a general test of "have I implemented
all features" I don't mind having a few tests that make some calls on
trace() and I check by hand that they end up in the standard error
stream (or wherever I think they should go).

> So, let's say the tests are of type 'Inspect' in order to somehow verify/test
> the trace output, it currently happens at the cost of that the data output is
> not fully verified (well, it depends on inspection).

Yes I agree, it would be better to use XML comparison on the expected
output and have another element <expected-trace> or something which you
could additionally verify by hand, or something....

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Re: Inspect/implementation defined order fn-trace-*

2006-04-25T04:48:13Z

On Tuesday 25 April 2006 10:11, David Carlisle wrote:
> Frans,

David,

> I think (as a non WG member) that the reason these are Inspect is that
> the point of trace() is that you need to _inspect_ the trace output
> (which has gone to some system specific place).
> The actual result returned by the query isn't system dependent, but
> it's for you to look at the log generated by the trace() function and if
> it's empty or if it just says "system error: couldn't write to log file"
> or something else other than the expected trace, it's for you to decide
> whether that constitutes a pass or fail.
>
> Having said that, I think that this interpretation is really justified
> by the Catalogue markup which does, as you say, imply that one should
> manually compare the result output with the supplied result file.
>
> The Catalogue format should probably be extended to allow the Catalogue
> to specify both the Query result (checked by XML comparisopn) and the
> trace log (checked by inspection).

I don't see what the XQTS can do in order to verify interoperability on the
trace. The destination is ·implementation-defined·, the format is
·implementation dependent·, the ordering between multiple invokations is
·implementation dependent·, and not the least that the data "may be directed
to a trace data set". I see nothing which an implementation is required to
do, not even to report anything. As I see it, there is nothing to verify
since an implementation can do anything it chooses to.

So, let's say the tests are of type 'Inspect' in order to somehow verify/test
the trace output, it currently happens at the cost of that the data output is
not fully verified(well, it depends on inspection).

So, the alternatives are to either extend the catalog as you describe, or to
skip anykind of validation of the trace output. I think the latter is the
right one, because trace is implementation defined.

Cheers,

Frans

Re: Inspect/implementation defined order fn-trace-*

2006-04-25T04:11:06Z

Frans,

I think (as a non WG member) that the reason these are Inspect is that
the point of trace() is that you need to _inspect_ the trace output
(which has gone to some system specific place).

The actual result returned by the query isn't system dependent, but
it's for you to look at the log generated by the trace() function and if
it's empty or if it just says "system error: couldn't write to log file"
or something else other than the expected trace, it's for you to decide
whether that constitutes a pass or fail.

Having said that, I think that this interpretation is really justified
by the Catalogue markup which does, as you say, imply that one should
manually compare the result output with the supplied result file.

The Catalogue format should probably be extended to allow the Catalogue
to specify both the Query result (checked by XML comparisopn) and the
trace log (checked by inspection).

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Re: Inspect/implementation defined order fn-trace-*

2006-04-24T14:14:25Z

On Monday 24 April 2006 17:34, Carmelo Montanez wrote:
> Frans:
>
> Thanks of the comment on fn:trace tests. I will ask the task force to
> add this to our telecon this week.

In case you've missed it, I opened a report on it such that it wouldn't get
lost:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3139

Cheers,

Frans