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 5879 - [FT] query in extension selection of xquery full text doc is NOT correct
Summary: [FT] query in extension selection of xquery full text doc is NOT correct
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-18 16:23 UTC by zhen hua liu
Modified: 2008-08-26 18:30 UTC (History)
0 users

See Also:


Attachments

Description zhen hua liu 2008-07-18 16:23:18 UTC
The following two queries in http://www.w3.org/TR/xpath-full-text-10/#id-extension-selections are NOT correct and have syntax errors.
Q1:
declare namespace exq = "http://example.org/XQueryImplementation";
/books/book[.//p ftcontains (# exq:distance #) { "web site"
ftand "usability" distance at most 1 words] } 
Q2:
declare namespace exq = "http://example.org/XQueryImplementation";
//city[. ftcontains (# exq:classifier with class 'Animals' #) 
       {"animal" with thesaurus at "http://example.org/thesaurus.xml" 
        relationship "RT"}

It should be revised below with syntax problem corrected.
Q1:
declare namespace exq = "http://example.org/XQueryImplementation";
/books/book[.//p ftcontains (# exq:distance #) { "web site"
ftand "usability" distance at most 1 words }]

Q2:
declare namespace exq = "http://example.org/XQueryImplementation";

//city[. ftcontains (# exq:classifier with class 'Animals' #) 
       {"animal" with thesaurus at "http://example.org/thesaurus.xml" 
        relationship "RT"} ]
Comment 1 Jim Melton 2008-08-26 18:30:17 UTC
The Full-Text Task Force has discussed the problem and determined that the
solution provided with the bug report is correct. Those changes have been made to the internal draft of the FT spec.  We are therefore marking this bug FIXED. 

Because you were present when the decision was made, we presume that you are
satisfied and are also marking the bug CLOSED.