This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
All done and checked in (see http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-10/html/Overview.html#ftmatchoptions ).
Re [4]: rather than making the suggested change in para 7 (before the two constraints), you made a change in para 8 (after the constraints), which results in some unnecessary repetition between the two paras. I still prefer my original suggestion.
Thanks for catching this... I haven't read carefully. Now fixed.
Thanks! Closing now.