XQuery and XPath Full Text 3.0 Requirements and Use Cases /**/ /* from xsl:query.xsl (C) */ 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; } /* from xsl:query.xsl (D) */ 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; }
/* from xsl-query.xsl (B) */ 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/2015/NOTE-xpath-full-text-30-requirements-use-cases-20151210/ Latest version: http://www.w3.org/TR/xpath-full-text-30-requirements-use-cases/ Previous versions: http://www.w3.org/TR/2015/WD-xpath-full-text-30-requirements-use-cases-20150312/ http://www.w3.org/TR/2012/WD-xpath-full-text-30-requirements-use-cases-20120327/ Editor: Pat Case, Library of Congress Copyright W3C ® MIT ERCIM Keio Beihang liability trademark document use This document specifies requirements and use cases for Full-Text Search for use in XQuery 3.0 [XQuery 3.0: An XML Query Language] [XML Path Language (XPath) 3.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 XSLT Working Group XQuery and XPath Full Text 3.0 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 This document is governed by the 1 September 2015 W3C Process Document 1 Goals Requirements Terminology General Requirements Backward compatibility Extension compatibility Full Text Search Functionality Language Identifiers Editorial Changes Irrevocable Stop Words Use Cases A References Non-Normative The goal of XQuery and XPath Full Text 3.0 is to extend XQuery and XPath Full Text 1.0 with additional functionality in response to requests from users and implementors. 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 XQuery and XPath Full Text 3.0 MUST Every valid XQuery and XPath Full Text 1.0 expression MUST MUST Status: XQuery and XPath Full Text 3.0 MUST XML Query Working Group XSL Working Group Status: XQuery and XPath Full Text 3.0 MUST Status: XQuery and XPath Full Text 3.0 MUST Status: There are no use cases provided in this edition of the Requirements and Use Cases document. XQuery and XPath Data Model (XDM) 3.0 latest version XQuery 3.0: An XML Query Language latest version XML Path Language (XPath) 3.0 latest version XQuery 3.0 Requirements 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, referenced in e.g. "SQL Multimedia and Application Packages (SQL/MM)"