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

[Bug 4723] [FT] editorial: 4.1.2 Representations of Tokenized Text and Matching

From: <bugzilla@wiggum.w3.org>
Date: Sat, 23 Jun 2007 10:11:14 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1I22aI-0005ty-0b@wiggum.w3.org>

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

           Summary: [FT] editorial: 4.1.2 Representations of Tokenized Text
                    and Matching
           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


4.1.2 Representations of Tokenized Text and Matching

[1]
paras 2-4
"A [Definition: ..."
    Put the "A" inside the definition.

[2]
para 3
"relative position of the search string in the query in document order"
    There's no such thing as document order for things in the query.

[3]
bullets
    It'd be a bit easier to read if you put the name of the property at
    the start of the bullet-blurb, rather than the end.

[4]
startPos & endPos
"a unique identifier that captures the relative position..."
    [4a]
    The other properties just say "the relative position...". What's the
    significance of this difference?

    [4b]
    "unique":
    Not really helpful unless you specify the arena over which it's
    unique. E.g., "Within the results of a single tokenization, the
    startPos of any two distinct TokenInfos are distinct."

    [4c]
    "identifier"
    s/identifier/integer/, given the way it's used and given the schema in
    4.2.1.3.
    For that matter, at "Each TokenInfo is associated with", you could
    append "six integer-valued properties".
Received on Saturday, 23 June 2007 10:11:18 UTC

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