W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2009

[Bug 8403] New: Several issues on use cases, including consistency with XQFTTS

From: <bugzilla@wiggum.w3.org>
Date: Mon, 30 Nov 2009 17:09:07 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-8403-523@http.www.w3.org/Bugs/Public/>

           Summary: Several issues on use cases, including consistency with
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Full Text 1.0 Use Cases
        AssignedTo: pcase@crs.loc.gov
        ReportedBy: peter.fischer@inf.ethz.ch
         QAContact: public-qt-comments@w3.org

I've run into a number of issues with the FT use cases when testing the MXQuery
implementation against the test suite:

- The use case document and the test suite seem to be out of sync for the
ignore (14.2) cases:
1) 14.2.1: Test Suite expects empty results, document non-empty. 

2) 14.2.2: Queries in document specify to include all chapters, not just the
ones containing the search terms. The expected result in both the UC document
and the suite list only the chapter containing the terms, not all.
ignore-queries-q2 (XQuery solution in suite) is different from UC document (and
the XPath solution), lists all books, not just the one with the relevant

3) 14.2.3: The same discrepancy between XQuery and XPath solution as in 2)
shows up in the UC document and the test suite, so all titles are listed for
the XQuery case (and just the relevant chapter), while the matching books with
all chapters are in the XPath case

4) 14.2.4: Same error as in 2) in 3) present in the test suite, but corrected
in the UC document

- In 15.2.4 Q4, two issues are present
1) the ignore part of the second FTContains uses  .//footnote, even though no
expression before has not set a context item (unless FTContains sets a context
item, which seems to contradict the description and a number of other test
2) $au contains text fnot should not become true for book number=2, since $au
is () there, and the description of the FTContains semantics (4.3 in FT CR) 
seems to imply that an empty search context always yields false. Several tests
in the test suite support this 

- In 16.2.9 Q9 (xquery-xpath-composability-queries-results-q9a/9b), the
keywords "succesfully", "completing" and "tasks" are queried using stemming,
and within an unordered window of 4*#chapters in a book. The MXQuery
implementation uses a Porter-based stemmer and turns these keywords into the
stems "success", "complet" and "task". As a result, the following paragraph
also matches this query:

<p>Users are asked to complete tasks which 
            measure the success of the information 
            architecture and navigational elements of the 

(less than 12 words, unordered)

which in turn means that the book with shortTitle "Improving Web Site
Usability" is part of the generated result. If there is no error in my
reasoning (and implementation), I'd suggest fixing the use case either by 
+ requesting "ordered" or 
+ not using stemming or
+ adding the second book to the result

- In 17.2.6 Q6 the boolean output of a FTContains is again queried using a
FTContains, and part of the result:

let $booktext := $book/content contains text ...
let score $s := $booktext contains text ...
return ($book/metadata/title, $booktext)

Probably the correct query is 

let $booktext := $book/content [. contains text ... ]
let score $s := $booktext contains text ...
return ($book/metadata/title, $booktext)

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, 30 November 2009 17:09:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:29 UTC