- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 23 Jun 2007 10:00:41 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4705
Summary: [FT] editorial: 3.3 Match Options
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 Match Options
[1]
para 6
"and at each FTPrimary the locally"
s/FTPrimary/FTPrimaryWithOptions/
[2]
"the locally (like postfix operators) specified"
I think the parenthetical is clunky there. Just delete it.
[3]
para 7
"The order in which effective match options for an FTWords are applied is
subject to some constraints:"
In the production for FTMatchOption, the order of nonterminals in the
right-hand side respects the constraints, which is nice. It would be
good if the subsections of 3.3 were also in this order.
[4]
para 8
"[Definition: This order is called the match option application order.]"
This is not a good standalone definition. Instead, at para 7:
[Definition: The order in which effective match options for an
FTWords are applied is called the match option application order.]
This order is subject to some constraints:
[5]
example 2
'/book/title ftcontains "usability" case insensitive ...'
This example might be more helpful if it put each option on a separate
line.
Received on Saturday, 23 June 2007 10:00:45 UTC