- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 23 Jun 2007 10:03:22 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4709
Summary: [FT] editorial: 3.3.5 Stop Word Option
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P2
Component: Full Text
AssignedTo: jim.melton@acm.org
ReportedBy: jmdyck@ibiblio.org
QAContact: public-qt-comments@w3.org
3.3.5 Stop Word Option
[1]
'[173] FTRefOrList ::= ...'
The name "RefOrList" is fairly generic. Perhaps "FTStopWords"?
[2]
'[174] FTInclExclStringLiteral ::= ("union" | "except") FTRefOrList'
The "StringLiteral" in the name doesn't really make sense.
Perhaps "FTStopwordInclExcl" ?
[3]
para 2
"they are used as they occur in the sequence."
There's no antecedent for "the sequence".
[4]
Note
"If applied during indexing asking for stop words to not be used during a
query, will have no effect."
[4a]
After "indexing", insert comma.
[4b]
Except for the fact that it's a Note, this appears to be a license for
a Full-Text processor to behave non-conformantly. Surely if an
implementation does some pre-emptive computation assuming certain
options, and a query uses conflicting options, then the implementation
is obliged to ignore the prepared results and do what it takes to give
the correct answer.
[5]
examples
I think it would be instructive if you had an example like
... p ftcontains "supports users" with stop words ("the")
As I understand it, the result is false (despite the fact that the
text contains "supports the users"), which might not be what people
expect.
[6]
'contains the "then"'
Change to 'contains "the" and "then"' ?
[7]
'except ("the then")'
Are you sure? Supposedly, no tokenization is performed on "the then".
I think you mean 'except ("the", "then")', or else you need to clarify
how string literals are handled here.
Received on Saturday, 23 June 2007 10:03:24 UTC