Re: [FT] FTThesaurusOption

Andrew,
 
At our last face-to-face meeting we improved FTThesaurusOption,
changing the productions as follows:
 
[152]    FTThesaurusOption   ::=    (<"with" "thesaurus"> FTThesaurusID

("," FTThesaurusID)*) | (<"with" "default" "thesaurus"> (","
FTThesaurusID)*) | <"without" "thesaurus">

[152']   FTThesaurusID ::= <"at" StringLiteral> (<"relationship"
StringLiteral>)? 
(FTRange "levels")?)
 
The intent is to enable the user to call multiple thesauri. We think
the production is clearer now. It makes the correct associations
between
each thesaurus and the relationships and levels to be applied when
searching it. The "at" makes it clear that a URL is expected and not
words or phrases.
 
These changes will be reflected in the next public working draft
 
Pat Case for the XQuery and XPath Full-Text Task Force.


>>> andrewc <andrew.cao@cisra.canon.com.au> 6/8/2005 11:32 PM >>>


Dear editors,

According to FT grammar, FTThesaurusOption (with user defined
thesaurus) 
can have two forms:
Form 1: /book ftcontains "quote" with thesaurus at 
"http://bstore1.example.com/UsabilityThesaurus.xml" relationship
"synonym"
Form 2: /book ftcontains "quote" with thesaurus ( "string literal 1", 
"string literal 2", "string literal 3", "string literal 4")
relationship 
"synonym"
When should user issue the second form of query?

Thanks,