This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4968 - [FTUseCase] Use Case "Character", Use Case "Logical", Use Case "XQuery-XPath-Composability"*
Summary: [FTUseCase] Use Case "Character", Use Case "Logical", Use Case "XQuery-XPath-...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Working drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Pat Case
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-20 17:15 UTC by Chavdar Botev
Modified: 2008-02-11 20:01 UTC (History)
0 users

See Also:


Attachments

Description Chavdar Botev 2007-08-20 17:15:40 UTC
See http://lists.w3.org/Archives/Member/member-query-fttf/2007Aug/0018.html

1) Use Case "Character", Use Case "Logical", Use Case "XQuery-XPath-Composability"*

Character
Q1: the query contains "with diacritics", but the grammar requires "with diacritics /sensitive/" or "with diacritics /insensitive/"
Suggestion: write "with diacritics sensitive" instead of "with diacritics"

Logical
Q6: And Not Query Where Second Operand Is a Subset of the First Operand
Q7: Mild Not Query Where Second Operand Is a Subset of the First Operand

XQuery-XPath-Composability
Q5: Full-Text Query with Character String Query
Comment 1 Pat Case 2007-10-02 12:48:40 UTC
As Use Case editor I thank the submitters for this and other bugs submitted addressing the FT Use Cases. Your careful review is greatly appreciated. 

This bug correctly states that we still had use cases for "with diacritics"
and "without diacritics" in the Last Call version of the FT Use Cases. These are no longer FTDiacritics options. 

The Full Text Task Force agreed to modifiy the use cases cited below plus Character Use Case 9.2.2 Q2 to use the two remaining FTDiacritics options: "diacritics sensitive" and "diacritics insensitive". These modifications have been made in the October 1 internal version and will appear in the next public version. If the submitters agree with the modification, please mark this bug closed.