W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2011

[Bug 11931] New: [FT] ft-3.4.3-expressions-q4 expected result wrong

From: <bugzilla@jessica.w3.org>
Date: Tue, 01 Feb 2011 00:28:26 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-11931-523@http.www.w3.org/Bugs/Public/>

           Summary: [FT] ft-3.4.3-expressions-q4 expected result wrong
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: Full Text 1.0
        AssignedTo: jim.melton@acm.org
        ReportedBy: paul@lucasmail.org
         QAContact: public-qt-comments@w3.org

This test:

for $book in $input-context/books/book
  let $cont := $book//content
  where $cont contains text "program"
    using thesaurus at "http://bstore1.example.com/TechnicalThesaurus.xml"
relationship "UF"
return $book

has the thesaurus URI resolve to an intentionally missing thesaurus XML file
and an expected result of error of FTST0018: It is a static error if, during
the static analysis phase, the query is found to contain a thesaurus option
that refers to a thesaurus that is not found in the statically known thesauri.

IMHO, there's a difference between "known" and "missing".  Suppose, for a
different query that makes use of the UsabilityThesaurus.xml (which resolves to
usability.xml), I accidentally delete the usability.xml file.

The URI resolution is just the same as before in that it will correctly resolve
to the usability.xml file (hence, the referred-to thesaurus URI is just as
"known" as it was before), it's just that the file doesn't exist.  An XQuery
implementation should give some kind of "file not found" error that's a lot
more specific.

It's a lot more helpful to distinguish the two cases especially if you were
some poor person whose pager went off at 3am because a running XQuery server
emitted an error.  It would be a lot more helpful have said person look
immediately for a missing file rather than having to check to see it the URI
resolution is correct.  It's a "quality of implementation" issue.

If you really want this test to have an expected result of FTST0018, then the
catalog should have *no* mapping at all for TechnicalThesaurus.xml -- then it
wouldn't be "known".

The severity on this bug is higher than normal for those of us who have
automated test suites and who want to pass all the tests.

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 Tuesday, 1 February 2011 00:28:29 UTC

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