W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2007

[Bug 4704] [FT] editorial: 3.2 Search Tokens and Phrases

From: <bugzilla@wiggum.w3.org>
Date: Sat, 23 Jun 2007 10:00:07 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1I22PX-0005S9-Uu@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4704

           Summary: [FT] editorial: 3.2 Search Tokens and Phrases
           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.2 Search Tokens and Phrases

[1]
para 3
'The FTWordsValue is converted as though it were an argument to a function
with the expected type of "xs:string*".'
    This sentence belongs in para 5, with some accomodation:
        The following rules specify how an FTWordsValue matches tokens and
        phrases. First, the FTWordsValue is converted to a sequence of
        strings as though it were an argument to a function with the
        expected type of "xs:string*". Then, each of those strings is
        tokenized ...

[2]
any, all
"the sequence of tokens for every string is considered as a phrase,"
    s/every/each/

[3]
any
"If the sequence contains more than one string"
    This might be confusing, because the most recent reference to a
    sequence was a sequence of tokens.
    s/the sequence/the value of the FTWordsValue/

[4]
examples
'/book[@number="1" and ...'
    The examples might be more natural if you left out the @number="1"
    condition.
Received on Saturday, 23 June 2007 10:00:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:33 UTC