1 Goals
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.
2
Requirements
2.1 Terminology
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:
- MUST
-
This word means that the item is an absolute requirement.
- SHOULD
-
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.
- MAY
-
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, or MAY are used in this technical sense, they
occur as a hyperlink to these definitions. These words will also be
used with their conventional English meaning, in which case there
is no hyperlink. For instance, the phrase "the full implications
should be understood" uses the word "should" in its conventional
English sense, and therefore occurs without the hyperlink.
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
-
This indicates that the requirement, according to
its original formulation, has been completely met. Optional
clarificatory text may follow.
- "Yellow" status
-
This indicates that the requirement has been
partially met according to its original formulation. When this
happens, explanatory text is provided to better clarify the current
scope of the requirement.
- "Red" status
-
This indicates that the requirement, according to
its original formulation, has not been met. If this is the case,
explanatory text is provided.
2.2 General Requirements
2.2.1 Backward compatibility
-
XQuery and XPath Full Text 3.0 MUST be backward compatible.
Every valid XQuery and XPath Full Text 1.0 expression MUST be valid in XQuery and XPath Full Text
3.0 and it MUST evaluate to the
same result.
Status: this requirement has been
met.
2.2.2 Extension compatibility
-
XQuery and XPath Full Text 3.0 MUST be compatible with XQuery and XPath
3.0 extensions developed by the XML Query Working Group and the
XSL Working Group.
Status: this requirement has been
met.
2.3 Full Text Search
Functionality
2.3.1 Language
Identifiers
-
XQuery and XPath Full Text 3.0 MUST specify in the Language Option how to
handle multiple language identifiers for the same language,
including languages represented by both two- and three- letter
identifiers.
Status: this requirement has been
met.
2.4
Editorial Changes
2.4.1 Irrevocable Stop
Words
-
XQuery and XPath Full Text 3.0 MUST specify in the Stop Word Option that
implementations may apply stop word lists during indexing and be
unable to comply with query-time requests to not apply those stop
words.
Status: this requirement has been
met.
3 Use Cases
There are no use cases provided in this edition of the
Requirements and Use Cases document.