4971 2007-08-20 17:21:33 +0000 [FTUseCase] incorrect FLWOR expression in multiple use cases 2008-02-11 20:00:41 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Working drafts PC Windows XP CLOSED FIXED P2 normal --- 1 cbotev pcase public-qt-comments oldest_to_newest 16228 0 cbotev 2007-08-20 17:21:33 +0000 See http://lists.w3.org/Archives/Member/member-query-fttf/2007Aug/0018.html *4) Use Case "Wildcard", Use Case "Stemming", Use Case "Stopword", Use Case "Axes", Use Case "Ignore", Use Case"Full-text Composability", Use Case "XQuery-XPath Composability", Use Case "Store"* , in the return of the FLWOR expression opens a new scope. Suggestion: use (,) instead. Wildcard: Q3 Zero or More Character Infix Wildcard Query Q4 One or More Character Suffix Wildcard Query on Part of a Word Q5 Specified Range of Characters Suffix Wildcard Query Stemming Q2 Query Stemming on Multiple Word Roots Stopword Q3 Query Excluding a Stop Word on a Stop Word List Axes Q1 Query on Element and Its Children Q2 Query on Element Returning Its First Two Children Q3 Query on Element and Its Ancestors Q4 Query on Element and Its Right Siblings Ignore Q2 Phrase Query Ignoring Content of Descendant Element Specified by XPath Expression Q3 Phrase Query Ignoring Content of Descendant Element Specified by Full-Text Query Q4 Distance Query Ignoring Content of Descendant Elements Level by Level Full-Text Composability Q2 Phrase and Distance Query in an Instance of an Element with Stemming XQuery-XPath Composability Q9 Query Using an XQuery Expression to Determine the Number of Words Allowed in a Window Score Q6 Query with Weight Declaration 16989 1 pcase 2007-10-02 13:02:02 +0000 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 should add parentheses around return statements containing multiple elements separated by commas. The Full Text Task Force agreed to modify the use cases cited below as recommended. 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 modifications, please mark this bug closed.