- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 10 Jul 2008 15:10:46 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5838
Pat Case <pcase@crs.loc.gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from Pat Case <pcase@crs.loc.gov> 2008-07-10 15:10:45 ---
Christian,
The following changes are being made to the Full Text Use Cases. I am treating
them as editorial changes therefore I am not waiting for Full Text Task Force
approval, but I will ask for their review once published internally.
Corrected 2.2.7 Q7 Entire Element Content Query
Added "with wildcards" to the XQuery and XPath solutions.
Corrected 4.2.1 Q1 Query on Attribute
Moved "with stemming" to after "improve" and added parentheses around
("improve" with stemming ftand "web" ftand "usability") to make the distance
operator applicable to all 3 operands in the XQuery and XPath solutions.
Corrected 5.2.1 Q1 One Character Suffix Wildcard Query
Capitalized the "S" in "Solution in XQuery".
Corrected 16.2.9 Q9 Query Using an XQuery Expression to Determine the Number of
Words Allowed in a Window
Changed the 2nd "for" to "let" in the XQuery solution.
Corrected 17.2.4 Q4 Query Combining Score and XML Structure with a Conditional
Return
Added the "local" prefix to 2 filter functional calls in the XQuery solution.
The changes will appear internally to W3C Members after the next build of the
Use Cases.
The changes will appear to the public in the next public release.
Thank you so much for pointing out these errors.
We will address the other issues: >0 and text case issues separately.
Pat Case, Member XQuery Full Text Task Force
--
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 Thursday, 10 July 2008 15:11:19 UTC