XQuery and XPath Full Text 1.0 Requirements /**/ code { font-family: monospace; }
div.constraint, div.issue, div.note, div.notice { margin-left: 2em; }
div.issue p.title { margin-left: -2em; }
ol.enumar { list-style-type: decimal; } ol.enumla { list-style-type: lower-alpha; } ol.enumlr { list-style-type: lower-roman; } ol.enumua { list-style-type: upper-alpha; } ol.enumur { list-style-type: upper-roman; }
li p { margin-top: 0.3em; margin-bottom: 0.3em; }
sup small { font-style: italic; color: #8F8F8F; } div.exampleInner pre { margin-left: 1em; margin-top: 0em; margin-bottom: 0em} div.exampleOuter {border: 4px double gray; margin: 0em; padding: 0em} div.exampleInner { background-color: #d5dee3; border-top-width: 4px; border-top-style: double; border-top-color: #d3d3d3; border-bottom-width: 4px; border-bottom-style: double; border-bottom-color: #d3d3d3; padding: 4px; margin: 0em } div.exampleWrapper { margin: 4px } div.exampleHeader { font-weight: bold; margin: 4px}
div.issue { border-bottom-color: black; border-bottom-style: solid; border-bottom-width: 1pt; margin-bottom: 20pt; }
th.issue-toc-head { border-bottom-color: black; border-bottom-style: solid; border-bottom-width: 1pt; }
table.small { font-size: x-small; } a.judgment:visited, a.judgment:link { font-family: sans-serif; color: black; text-decoration: none } a.processing:visited, a.processing:link { color: black; text-decoration: none } a.env:visited, a.env:link { color: black; text-decoration: none } /**/ This version: http://www.w3.org/TR/2011/NOTE-xpath-full-text-10-requirements-20110125/ Latest version: http://www.w3.org/TR/xpath-full-text-10-requirements/ Previous version: http://www.w3.org/TR/2008/WD-xpath-full-text-10-requirements-20080516/ Editors: Stephen Buxton, Oracle Corp Pat Case, Library of Congress Michael Rys, Microsoft Copyright W3C ® MIT ERCIM Keio liability trademark document use The document specifies requirements for Full-Text Search for use in XQuery [XQuery 1.0: An XML Query Language] [XML Path Language (XPath) 2.0] This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index This is a Working Group Note Process Document XML Query Working Group XSL Working Group XML Activity Working Group Note XQuery and XPath Full Text 1.0 This document includes, for each requirement, a corresponding status, indicating the current situation of the requirement in XQuery and XPath Full Text 1.0 No substantive changes have been made to this specification since its publication as a Last Call Working Draft. Please report errors in this document using W3C's public Bugzilla system http://www.w3.org/XML/2005/04/qt-bugzilla [email protected] http://lists.w3.org/Archives/Public/public-qt-comments/ Publication as a Working Group Note This document was produced by groups operating under the 5 February 2004 W3C Patent Policy public list of any patent disclosures public list of any patent disclosures Essential Claim(s) section 6 of the W3C Patent Policy 1 Introduction Terminology Terminology SCORE Full-Text Search Language Design The Data Model Side-effects on the data Score Function and Full-Text Predicates Predicate and Score Independence Score language Score algorithm Return Score Sort by Score Type, Range of Score Score Statistics Semantics of Score Combined score Score Combination Score algorithm vendor-provided Score algorithm overridable Score influence Extensibility Extensible by vendors Extensible by users First, Future Versions End user language Searchable query Universality Integration XPath Extensibility Mechanisms Integration into XQuery/XPath XQuery and XPath Full Text 1.0 Extensibility Composability Human-readable XML syntax Implementation Declarativity Functionality and Scope Functionality Search Scope Search within arbitrary structure Constructed Structures Return Arbitrary Nodes Parts of Search Tree Attributes Search within attributes Search across attributes and content Markup Element Boundaries Search across element boundaries Element as a token boundary Score Score accessible Implicit ordering Score extendable A References Non-Normative Change Log "Full-Text Search" (FTS) is a large field which covers a vast array of functionality. In addition, there are many different ways one could combine FTS capabilities with XQuery and XPath. The requirements are written without reference to any particular solution. The following key words are used throughout the document to specify the extent to which an item is a requirement for the work of the XML Query Working Group: This word means that the item is an absolute requirement. This word means that there may exist valid reasons not to treat this item as a requirement, but the full implications should be understood and the case carefully weighed before discarding this item. This word means that an item deserves attention, but further study is needed to determine whether the item should be treated as a requirement. When the words MUST SHOULD MAY Each requirement also includes a status section, indicating its current situation in the XML-Query family of specifications. Three status levels are available: "Green" status "Yellow" status "Red" status [ Definition SCORE [ Definition Full-Text Search This section covers requirements for XQuery and XPath Full Text language design that are independent from, but related to, integration and scoping requirements. XQuery and XPath Full Text 1.0 functions MUST [XQuery 1.0 and XPath 2.0 Data Model] Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST SCORE Status: XQuery and XPath Full Text 1.0 MUST use the same language for full-text predicates and SCORE or use a language for full-text predicates that is a proper subset of the language for SCORE Status: XQuery and XPath Full Text 1.0 MUST SCORE Status: XQuery and XPath Full Text 1.0 MUST SCORE Status: XQuery and XPath Full Text 1.0 MUST SCORE SCORE SHOULD Status: XQuery and XPath Full Text 1.0 MUST SCORE Status: XQuery and XPath Full Text 1.0 MAY SCORE Status: XQuery and XPath Full Text 1.0 MUST SCORE Status: The algorithm to produce combined SCORE MUST Status: The algorithm to produce combined SCORE SHOULD Status: Users MUST Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MAY Status: The first version of XQuery and XPath Full Text 1.0 MUST Status: It is not a requirement that XQuery and XPath Full Text 1.0 be designed as an end-user UI language. Status: It SHOULD Status: XQuery and XPath Full Text 1.0 SHOULD MUST Status: This section specifies requirements for the integration of XQuery and XPath Full Text 1.0 with XQuery and XPath. Part, but not necessarily all, of XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 SHOULD Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST SHOULD Status: XQuery and XPath Full Text 1.0 may have more than one syntax binding. One query language syntax must be convenient for humans to read and write. See [XML Query (XQuery) Requirements] Status: XQuery and XPath Full Text 1.0 MAY MUST [XML Query (XQuery) Requirements] Status: XQuery and XPath Full Text 1.0 MUST MUST Status: This section defines requirements for the functionality in XQuery and XPath Full Text 1.0, and the scope of XQuery and XPath Full Text 1.0 queries. XQuery and XPath Full Text 1.0 MUST single-word search phrase search support for stop words single character suffix 0 or more character suffix 0 or more character prefix 0 or more character infix proximity searching (unit: words) specification of order in proximity searching combination using AND combination using OR combination using NOT word normalization, diacritics ranking, relevance Status: Additional functionality represented in the [XQuery and XPath Full Text 1.0 Use Cases] MUST Status: Additional functionality from other Full-Text Search contexts such as [SQL/MM Full-Text] MUST SHOULD Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MAY Status: If XQuery and XPath Full Text 1.0 supports search within names of elements and attributes, then it MUST element content and attribute values and names of elements and attributes in any search. Status: XQuery and XPath Full Text 1.0 MUST Status: XQuery and XPath Full Text 1.0 MUST MAY Status: SCORE MUST Status: SCORE SHOULD Status: SCORE MAY Status: XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition) et. al. latest version XQuery 1.0: An XML Query Language (Second Edition) et. al. latest version XML Path Language (XPath) 2.0 (Second Edition) et. al. latest version XML Query (XQuery) Requirements latest version XQuery and XPath Full Text 1.0 Use Cases latest version ISO/IEC 13249-2:2000, Information technology — Database languages — SQL Multimedia and Application Packages — Part 2: Full-Text, International Organization For Standardization, 2000, available from http://www.iso.org/ Author Date Action Description Stephen Buxton 2003-03-19 Added a Change Log Stephen Buxton 2003-03-19 Terminology definition changes Switched the definitions of SHOULD MAY [XML Query (XQuery) Requirements] [XML Query (XQuery) Requirements] Stephen Buxton 2003-04-18 Change XML Query Requirements link to external URI Changed links in the document body to point to external latest copy of XML Query Requirements. Pat Case 2006-11-17 Recorded that requirements were met Recorded that the XQuery and XPath Full Text 1.0 Requirements have been met (fully or paritially). Pat Case 2007-12-04 Title Updated title and title references to remove 1.0, 2.0, and the hyphen. Pat Case 2008-04-04 Requirement 4.2.1 Changed the status on 4.2.1 from green to yellow with an explanation.