[Bug 6223] [XQFTTS] cont.

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





--- Comment #12 from Pat Case <pcase@crs.loc.gov>  2009-02-03 20:14:57 ---
Hi Christian,

Sorry to be so long in responding. 

This response concerns the test cases produced from the score examples in the
Full Text Use Cases document. While many of these score examples make great use
cases, I agree some make loosey test cases. 

The Full Text Task Force however wants all the uses cases in test suite to
avoid questions about completeness of the test suite. 

So realizing that scoring is implementation-dependent and that any of these
examples could theoretically return almost any result set, I have provided a
few alternative results for each such query, but more importantly, have set the
compare parameter to Inspect and noted in the test description that any result
is acceptable.

I did this to all 6 score use case queries.

I also:

[20] RESULT score-queries-results-q1.txt

OLD: ... </book><book> ...
NEW: ... </book>, <book> ...
no commas between <book> elements. and, more important, as long as
no reference scoring model is defined, it might better to avoid score
values in the test result, as was done here

--I must have removed commas between book elements previously. I don't see them
now.

[21] QUERY score-queries-results-q2.xq

OLD: ... >$result/metadata/title</
NEW: ... >{ $result/metadata/title }</
...missing brackets. next, the order of the results will once more
be implementation dependent, so it might be recommendable to omit
the "order" clause

--Added the missing brackets.

[22] RESULT score-queries-results-q3.txt

...once more different results, dep. on the implementation, and same
problem for nearly all scoring queries. Is something like a default
scoring model planned for XQFT or the test suitesTS?

I am hoping this addresses items 20-22. 

Please let me know if you disagree.

Thanks again for helping us make the test suite better.

Pat


-- 
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, 3 February 2009 20:15:07 UTC