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 4969 - [FTUseCase] Use Case "XQuery-XPath-Composability"
Summary: [FTUseCase] Use Case "XQuery-XPath-Composability"
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: 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:17 UTC by Chavdar Botev
Modified: 2008-02-11 20:01 UTC (History)
0 users

See Also:

Attachments

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

2) Use Case "XQuery-XPath-Composability"*

Q9: the query contains "window at most (count(./contents/part/chapter) *3) words", but the EBNF defines window expressions like this "window AdditiveExpression FTUnit"
Suggestion: write "window (count(./contents/part/chapter) * 3) words"
Comment 1 Pat Case 2007-10-02 12:54:09 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 a use case for FTRange in a window query even though we had removed it from the spec. FTRange is still available elsewhere (in distance) but not in window.

The Full Text Task Force agreed to modifiy the use case cited below to remove the "at most". This modification has 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.