[Bug 6105] New: [FT] Test Suite cont.

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

           Summary: [FT] Test Suite cont.
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery
        AssignedTo: chamberl@almaden.ibm.com
        ReportedBy: christian.gruen@gmail.com
         QAContact: public-qt-comments@w3.org


Hello,

I have encountered some new inconsistencies in the current test suite...


[1] FTPrimary-FTWords-q1.xq
    FTPrimary-FTWords-FTTimes-q1.xq,
    FTPrimary-FTExtensionSelection-q1.xq
    FTPrimary-FTSelection-q1.xq

The child step "/div2" could to be rewritten to "//div2" to match the result
files.


[2] FTPrimary-FTExtensionSelection-q1.xq

As far as I know, the pragma (# exq:classifier with class 'Antonyms' #) cannot
be specified at the current location. Moreover, by using pragmas, it might be
that not all implementations will yield correct results.


[3] FTSelection-Weight-q1a.xq
    FTSelection-Weight-q1b.xq
    ...

Again, the location steps "/div[//a/@id" won't yield any results. The
alternative "//div2[@id=" should suffice.


[5] Examples/2.2.2/ft-222-examples-results-q1.txt

The correct result for "examples-222-q1.xq" should be:

<author>Melton Mowbray</author>


[6] FTPrimary-FTWords-q1_result.xml

Here I get another result as well (it's based on the query rewriting of [1])..

<paragraphs>
  <p>
Note that, along with the syntax rules above, there is an extra-grammatical 
constraint,
<loc xmlns:xlink="http://www.w3.org/1999/xlink"
href="#parse-note-multiple-match-options" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest">multiple-match-options
      </loc>,
which needs to be considered, if multiple match options are specified.
It states that within a single <nt xmlns:xlink="http://www.w3.org/1999/xlink"
def="doc-xquery-FTMatchOptions" xlink:type="simple">FTMatchOptions</nt>
at most one match option of any given 
<termref def="dt-match-option-group">match option group</termref> may
be specified. 
For example, if the <nt xmlns:xlink="http://www.w3.org/1999/xlink"
def="doc-xquery-FTCaseOption" xlink:type="simple">FTCaseOption</nt> "lowercase" 
is specified, then "uppercase" cannot also be specified as part of the same 
<nt xmlns:xlink="http://www.w3.org/1999/xlink" def="doc-xquery-FTMatchOptions"
xlink:type="simple">FTMatchOptions</nt>.
</p>
  <p>
<termdef id="dt-match-option-order" term="match option application order">
The order in which effective match options for an 
<nt xmlns:xlink="http://www.w3.org/1999/xlink" def="doc-xquery-FTWords"
xlink:type="simple">FTWords</nt> are applied 
 is called the <term>match option application order</term>.</termdef>
This order is significant
because match options are not always commutative.
For example,
    synonym(stem(word))
is not always the same as
    stem(synonym(word)).
</p>
</paragraphs>


[7] XQFTTSCatalog.xml

=> "Testsources" -> "TestSources"

=> "FTSelection-Weight-1a.xq" -> "FTSelection-Weight-q1a.xq"
...same operation for all files in this directory

=> Query FTSelection-Weight-q1d
 an <expected-error> element should be added here as implementations can raise
errors for negative values

=> Query ft-34-examples-q2 - ft-342-examples-q4 -> don't exist yet



Thanks,

Christian, BaseX Team 
http://www.basex.org


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 22 September 2008 02:24:48 UTC