W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2008

[Bug 6223] [XQFTTS] cont.

From: <bugzilla@wiggum.w3.org>
Date: Tue, 23 Dec 2008 01:05:50 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LEviY-0006qR-7w@farnsworth.w3.org>


Jim Melton <jim.melton@acm.org> changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED

--- Comment #9 from Jim Melton <jim.melton@acm.org>  2008-12-23 01:05:49 ---
[1] I agree with your your argument in
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6105#2 and have revised the
result in ft-222-examples-results-q1.txt to remove the "Heavy Rain" author

[3] I agree that there is a problem with the test ft-3.3-examples-q1, but I
don't agree with your proposed fix.  You proposed:
   OLD: ...at least 2 times]/@number
   NEW: ...at least 2 times]
However, the purpose of the query, as stated in Section 3.3 Cardinality
Selection, is "The following expression returns the example book element's
number...".  Therefore, the result currently provided as ft-3.3-examples-q1.xml
is incorrect -- it should not contain the <book> element, but merely the value
of the number attribute.  I have replaced ft-3.3-examples-q1.xml with
ft-3.3-examples-q1.txt (containing the single character "1") and updated the
catalog accordingly. 

[7] We had previously discovered this error and corrected it in the files we
use to generate the Full Text spec.  I have now taken the additional step of
copying the corrected file into the test suite space. 

[8] I agree and have made the appropriate change to the result file. 

[9] I agree and have made the appropriate change to the result file. 

[10] I agree and have made the proposed change to the queries. 

[11] I agree to the part of the comment about the use of // and have made that
change to the queries.  I agree that, in the queries that use the variable,
there is a spelling discrepancy between the variable declaration and its use
and have made appropriate changes to the queries to correct that. 

[12] By "too many results", do you mean "several results that differ only in
the relative placement of the attributes"?  If so, then (a)eliminating
namespaces won't make a difference and (b)I'm pretty sure (but haven't
confirmed) that the XML comparison (compare="XML") "normalizes" the attributes
to avoid this problem.  If you mean something else, I would be grateful for an

Until you respond to my question in [12], I am not marking this bug report
RESOLVED.  However, I believe that all other items have been resolved. 

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, 23 December 2008 01:06:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:38 UTC