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 3013 - requirement of separating query tokeninfos and regular tokeninfos
Summary: requirement of separating query tokeninfos and regular tokeninfos
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: Sihem Amer-Yahia
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL: http://lists.w3.org/Archives/Member/m...
Whiteboard:
Keywords: needsAgreement
Depends on:
Blocks:
 
Reported: 2006-03-17 18:21 UTC by Joaquin Delgado
Modified: 2006-04-07 21:07 UTC (History)
0 users

See Also:

Attachments

Description Joaquin Delgado 2006-03-17 18:21:10 UTC 
Jochen has introduced the requirement of separating query tokeninfos and regular tokeninfos.

Specifically he introduces a new type in message 
http://lists.w3.org/Archives/Member/member-query-fttf/2006Mar/0036.html

Namely:
1.  Types: I introduce a type fts:SearchItem to model the sequence of 
search tokens of a single search string. I assume fts:SearchTokenInfo to 
be provided by the implementation.
Comment 1 Joaquin Delgado 2006-03-28 00:00:12 UTC 
This is directly related to the proposal that Mary sent about eliminating getTokenInfo and the fact that in the current schema for the search string (xml) the query is already tokenized. Jochen sent a proposal (http://lists.w3.org/Archives/Member/member-query-fttf/2006Feb/0013.html) to solve this isuue.
Comment 2 Jochen Doerre 2006-04-07 21:06:43 UTC 
TokenInfos representing interval are no longer an adequate representation for search tokens. The complete proposal of the change is contained here:
(W3C-internal)
http://lists.w3.org/Archives/Member/member-query-fttf/2006Apr/0002.html