W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2011

[Bug 11821] New: [FT] Thesaurus option RangeExpr

From: <bugzilla@jessica.w3.org>
Date: Thu, 20 Jan 2011 10:33:38 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-11821-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11821

           Summary: [FT] Thesaurus option RangeExpr
           Product: XPath / XQuery / XSLT
           Version: Proposed Recommendation
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Full Text 1.0
        AssignedTo: jim.melton@acm.org
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org


I apologize for bringing this up rather late in the day.

The rules:

[172]        FTThesaurusID        ::=        "at" URILiteral ("relationship"
StringLiteral)? (FTRange "levels")?

[157]        FTRange        ::=        ("exactly" AdditiveExpr)
| ("at" "least" AdditiveExpr)
| ("at" "most" AdditiveExpr)
| ("from" AdditiveExpr "to" AdditiveExpr)

permit queries such as:

doc("http://bstore1.example.com/full-text.xml")
/books/book[./content contains text "people" using
thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml"
relationship "NT" at most ./content/@levels levels]

i.e. that the number of levels can be dynamic.

All other match options are static - either string literals or URI literals.

Why is this part of one match option dynamic?

The static nature of other match options makes life easier with regard to
pre-indexing.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 20 January 2011 10:33:41 UTC

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