This is a public W3C Working Draft for review by W3C Members and other interested parties. Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This is the fourth version of this document. Some query solutions have been changed based on implementer feedback and Task Force decisions. The most significant change is to the score syntax. See Appendix D
This document has been produced following the procedures set out for the W3C Process. This document was produced through the joint efforts of the W3C
Public comments on this document and its open issues are invited.
Comments should be entered into the issue tracking system for this
specification (instructions can be found at
The patent policy for this document is specified in the
This document specifies usage scenarios for full-text
queries as part of XML Query
(1) Use a current operating system and browser.
(2) If necessary, set the character encoding in the browser manually to Unicode or UTF-8. Often this setting may be changed from the View menu.
(3) If after setting the character encoding to Unicode, the Chinese characters in the subject elements of the sample data still do not display, it is likely that the browser cannot locate a font that contains Chinese characters in Unicode encoding. It might be necessary to add a Unicode font, preferably Arial Unicode MS.
The use cases listed below were created by the
The document supplements the XML Query Use Cases which can be found in the W3C
XML Query Use Cases
The full-text queries in the following use cases are performed on text which has been tokenized, i.e., broken into a sequence of words, units of punctuation, and spaces.
A word is defined as any character, n-gram, or sequence of characters returned by a tokenizer as a basic unit to be queried. Each instance of a word consists of zero or more consecutive characters. Beyond that words are implementation-defined. Note that consecutive words need not be separated by either punctuation or space, and words may overlap. A phrase is an ordered list of words. A phrase may contain any number of words.
Tokenization enables functions and operators which work with the relative positioning of words (e.g., proximity operators). Tokenization also enables functions and operators which operate on a part or the root of the word (e.g., wildcards, stemming).
These use cases:
(1) Present some possible functions and features for tokenized text support in XQuery and XPath. None are yet available in XQuery or XPath. Please comment on these use cases and recommend others.
(2) Illustrate simple and complex queries. The more complex queries would normally only be constructed by programmers, librarians, and other expert users. Sometimes they may be provided for novice users via saved queries and graphical user interfaces. Each query illustrates a single functionality. Queries may overlap in their functionalities (e.g., phrases and ordered distance queries allowing no intervening words). Overlapping and similar functionalities are noted in the comments on query behavior.
(3) Draw from sample data which are almost entirely in English. Use cases in other languages are solicited, especially where they illustrate language-specific implementations of functions and features. Among the most sought after are use cases for queries using prefix and infix wild cards, proximity queries, and operators and queries requiring functionality which may not have Western language equivalents.
(4) Include queries which in most instances can be written with pure Boolean full-text predicates or
with scoring (e.g., scoring on the number of occurrences of a word or phrase,
scoring on how close words are to one another within a distance
query, scoring on how similar a word is to the one being
stemmed)
(5) Query element content. See Section 4 (OTHER) for explicit queries on attribute values.
(6) Include queries which are case-insensitive. When returning a paragraph, the text is returned as it occurs in the data model. This approach was chosen to keep the sample data short and the expected results meaningful. It would have been equally valid to return only the character queried. A case-sensitive query is found in Section 9 (CHARACTER).
(7) Include queries which when they target XML elements are understood, unless otherwise stated, to query text within any text node descendant of the element.
(8) Include queries which return only elements and attributes which meet all the conditions specified in the query. In particular, pure Boolean full-text predicate queries return results where the Boolean conditions in the query are satisfied, i.e., are used to select what is being returned to users.
Query results may be returned in different ways. From a query for books containing the word "usability", users might be interested in returning, for each book containing the word "usability", its number and its entire content. In another situation for the same query, users might be interested in returning, for each book containing the word "usability", its number and only the elements and attributes in the content which contain the word "usability". As in this second situation, the queries in these use cases return only elements and attributes which meet all the conditions specified in the query.
The Return clause may also include additional or different elements and attributes if specified, and may construct new elements.
(9) Include queries which provide some of the basic functionality of fuzzy match querying (e.g., wildcards, stemming, thesaurus support, proximity).
(10) Provide highlighting of found words and phrases in the expected results of queries as an aid to users. The presence of highlighting says nothing about whether highlighting will be a feature of XQuery or XPath full-text querying.
(11) Display query solutions in XQuery and when possible in XPath. Queries which may not be written in XPath include those which contain element constructors, and cannot be written without let and order by clauses.
Examples of full-text querying functionalities for XML query languages
can be found in
To make the output more readable, the output of queries has been formatted using white space which may not be returned by a query processor. This white space should not be considered normative for the correctness of results.
These use cases represent a snapshot of an ongoing work. Some
important operators and features are not yet adequately covered by a
use case. The XML Query and XSL Working Groups reserve the right to
add, delete, or modify individual queries or whole use cases as the
work progresses. The presence of a query in this set of use cases does
not necessarily indicate that the query will be expressible in XQuery
The queries in these use cases are presented in the following format:
Query number Query title
User statement of query
Statement of functionality illustrated by query
Operands: Parts of words, words, phrases
Functionality: Operators, functions, collations, other functionality
Data context: One XPath expression locating the data being queried.
Query context: One or more XPath expressions locating the elements and attributes to be queried. The context of elements and attributes used in the Query context is relative to the Data context defined above.
Return: One or more XPath expressions which are returned only if the conditions specified in the query are met. Returned elements or attributes may differ from those specified in the Query context. Newly constructed elements might be returned. As in the Query context, the context of elements and attributes in Return statements is relative to the Data context defined above.
Comments: Comments on query behavior in general, and against the sample data in particular, plus the rationale for including this query in the use cases.
See Issue 1
The example queries in these use cases are based on a collection with the following XML Schema:
The data consists of a collection of three books. Two are primarily instructive text. The third is a guide to a manuscript collection. All contain metadata and full text.
The sample data binds to this URL: "http://bstore1.example.com/full-text.html".
These use cases query words and phrases in XML elements with simple content.
These use cases begin with the simplest queries possible. They query a word or phrase in an element with simple content and no descendants. One of these queries is on Chinese characters. Some queries return additional or different elements than were queried. A query queries and returns the full document. Others find a phrase only when it starts an element and find a exact phrase when it is the entire content of an element, allowing full-text variations, such as case, diacritics, and wildcards.
Find all book titles containing the word "usability".
This query finds a word in an element.
Operands: "usability"
Functionality: word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title
Return: ./metadata/title
Comments: This is the simplest query possible, a query on a word in an element. This query does not employ wildcards, stemming, or thesaurus support. While this query finds useful results in the sample data, many queries such as one on the word "test" would not. A query on the word "test" would return no results, missing the word variants which exist in the sample data: "pretest", "tested", "testers", "testimony", "testing", and "tests".
Find all book subjects containing the phrase "usability testing".
This query finds a phrase in an element.
Operands: "usability testing"
Functionality: phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject
Return: ./metadata/subjects/subject
Comments: This is a simple query on a phrase in an element. Like an ordered distance query allowing no intervening words, the words in this phrase query must be adjacent to each other and must appear in the order specified. While this query finds useful results in the sample data, many queries such as one on "software developer" would not. A query on the phrase "software developer" would return no results, missing "developer of software" which exists in the sample data.
Find all book subjects containing the phrase (n-gram) "网站".
This query finds a phrase (n-gram) in an element.
Operands: "网站"
Functionality: phrase query, language qualifier
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject
Return: ./metadata/subjects/subject
Comments: This query finds a phrase (n-gram) consisting of two Chinese characters. It assumes a specific language dependent tokenization.
Find all books with "usability tests" in book or chapter titles.
This query finds a phrase in different elements.
Operands: "usability tests"
Functionality: phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title, ./content/part/chapter/title
Return: .
Comments: This query is an example of a query in two different elements.
Find all books with the phrase "usability testing" in some subject.
This query finds a phrase in an element and returns different elements from the same document.
Operands: "usability testing"
Functionality: phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject
Return: ./metadata/title, ./metadata/author
Comments: This query queries the subject element, but does not return it. It returns two different elements.
Find all book titles which start with "improving" followed within 2 words by "usability".
This query finds an element which starts with specific words.
Operands: "improving" "usability"
Functionality: word queries, ordered distance (0 to 2 intervening words), starts-with functionality
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title
Return: ./metadata/title
Comments: The starts-with functionality restricts the query to the first words or phrase in an element. It is especially useful in querying journal
titles (e.g., title element, because the title element does not start with "improving" followed within 2 words by "usability".
Find all books with the entire title "improve the usability of a web site through expert reviews and usability testing", allowing any form of the word "improve".
This query finds the phrase when it is the entire content of an element.
Operands: "improve the usability of a web site through expert reviews and usability testing"
Functionality: phrase query, character wildcard (suffix) (0 or more), entire element content functionality
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title
Return: ./metadata/title
Comments: This query insists that the element contains the entire phrase being queried, no more and no less. It allows full-text variations, such as case, diacritics, and wildcards.
These use cases by default query across XML element boundaries.
Boundaries include XML tags: Start-Tags, End-Tags, and Empty-Element Tags. Descendant XML tags and attribute values are removed from the string to be queried by tokenization before the query. At the XQuery Data Model level tags are a syntactic element.
Find queries in an element which do not query some or all of its descendant elements in Section 14 (IGNORE).
Find all book chapters containing the phrase "one of the best known lists of heuristics is Ten Usability Heuristics".
This query crosses element boundaries.
Operands: "one of the best known lists of heuristics is Ten Usability Heuristics"
Functionality: phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/chapter
Return: .
Comments: Querying across element boundaries is similar to an XQuery and XPath character string function converting the sub-tree
under an element into a string by removing all markup. The citation element tags, including element name and attribute values, have been removed by tokenization.
Find all part introductions containing the word "prototypes".
This query crosses element boundaries.
Operands: "prototypes"
Functionality: word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/introduction
Return: .
Comments: Querying across element boundaries is similar to an XQuery and XPath character string function converting the sub-tree
under an element into a string by removing all markup. The bold element tags, including element name, have been removed by tokenization.
Find all book text with the word "tests".
This query finds a word in an element and its descendants.
Operands: "tests"
Functionality: word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: Querying across element boundaries is similar to an XQuery and XPath character string function converting the sub-tree
under an element into a string by removing all markup. Element tags, including element name and attribute values, have been removed by tokenization, including part,
chapter, title, p, component, and componentTitle tags.
Find all book text with the phrase "usability testing once the problems".
This query finds a phrase which begins in one element and ends in a sibling.
Operands: "usability testing once the problems"
Functionality: phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: Querying across element boundaries is similar to an XQuery and XPath character string function converting the sub-tree
under an element into a string by removing all markup. Element tags, including element name and attribute values, have been removed by tokenization, including title and p tags.
Find all books with word "identify" in book introductions or part introductions.
This query finds a word in an element in different sub-trees.
Operands: "identify"
Functionality: word query, character wildcard (suffix) (0 or more)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/introduction, ./content/part/introduction
Return: .
Comments: This query looks for a word in multiple instances of the introduction element which appear as children
of the content or part elements.
Find all books if any one contains the word "mouse".
This query finds a word in a document (anywhere in the document), crossing all element boundaries
Operands: "mouse"
Functionality: word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books
Query context: .
Return: .
Comments: It queries the root element and all its descendants. Querying across element boundaries is similar to an XQuery and XPath character string function converting the sub-tree under an element into a string by removing all markup. Element tags, including element name and attribute values, have been removed by tokenization. This query looks for a word inside an entire document and returns the entire document if the word exists. It does not employ wildcards, stemming, or thesaurus support. It is similar to search engine queries that search a collection of documents and return a subset of the searched collection.
Unlike all the other use cases in this document which query element content implicitly, these use cases query XML attribute values. Attribute values are not queried implicitly; they are queried explicitly.
Find all books with "improve" "web" "usability" in the short title.
This query finds multiple words in an attribute allowing word variants and allowing the words in any order with up to a specified number of intervening words.
Operands: "improve" "web" "usability"
Functionality: word queries, stemming, unordered distance (0 to 2 intervening words)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title/@shortTitle
Return: ./metadata/title
Comments: This query illustrates full-text querying in an attribute.
Find all books with the phrase "manuscript guides" in the short title and the phrase "user profiling" in a component title.
This query finds a phrase in an attribute and a phrase in an element.
Operands: "manuscript guides" "user profiling"
Functionality: phrase queries, stemming, and query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title/@shortTitle, ./componentTitle
Return: ./metadata/title/@shortTitle/text()
Comments: This query combines querying in an element with querying in an attribute.
These use cases illustrate queries which use wildcards to append or insert a character or sequence of characters to a word or a part of a word. Character wildcards may be prefix (appended before the first character), infix (inserted into a word), or suffix (appended after the last character).
Find all books with the word "test" with a one character suffix in the text.
This query finds a word with a one character suffix (one character after the last character).
Operands: "test"
Functionality: word query, character wildcard (suffix) (1)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query finds "tests", but not "pretest, "tested", "testers", "testimony", and "testing" which also appear in the sample data. There is no "test" in the sample data, but if there was, this query would not have found it.
Find all books with the word "way" with no prefix or a one character prefix in the text.
This query finds a word with no prefix or a one character prefix (zero or one character before the first character).
Operands: "way"
Functionality: word query, character wildcard (prefix) (0 or 1)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: There is no "way" in the sample data but if there was, this query would have found it.
Find all books with the words "serve" or "service" in the text.
This query finds words with no infix character or any number of infix characters (zero or more characters inserted in the middle of a word).
Operands: "serv", "e"
Functionality: word query, character wildcard (infix) (0 or more)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: ./@number, ./metadata/title/text(), ./content
Comments: This query returns the word "service" and would return the word "serve" if it existed in the sample data. It does not return the word "served" which exists in the sample data.
Find all books with the phrases "usability testing" or "user testing" in the text.
This query finds a phrase allowing a suffix of one or more characters (one or more characters after the last character) on a part of one of the words.
Operands: "us testing"
Functionality: phrase query, character wildcard (suffix) (1 or more)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: ./@number, ./metadata/title/text(), ./content
Comments: This is a suffix query on a part of a word "us" which is not one of the words or one of the roots of the words desired in the results. The query on "us" will find "usability" and "user". Where stemmed queries (Section 6 (STEMMING)) attempt to return linguistic variants of a word or the root of a word, wildcards may be applied to any part of a word and will return all character combinations found.
Find all books with the word "test" with a three to four character suffix in the text.
This query finds a word with a number of characters within a specified range in a suffix (specified range of characters after the last character).
Operands: "test"
Functionality: word query, character wildcard (suffix) (3 to 4)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: ./@number, ./content
Comments: This query allows any three or four character suffix. It returns "testers" and "testing", but not "pretest" "tests" and "tested" which also appear in the sample data. There is no "test" in the sample data, but if there was, this query would not have found it.
These use cases invoke a stemming algorithm (e.g., Porter) which returns noun, verb, adjective, and adverb forms of a word or root of a word in singular and plural.
Find all books with the word "test" in the text.
This query finds a word and its variants applying a stemming algorithm.
Operands: "test"
Functionality: word query, stemming
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: Unlike the wildcard queries in Section 5 (WILDCARD) which allow any suffix, this query will not return the word "testimony" which occurs in the sample data.
Find all books with the phrases "usability testing" or "user testing" in the text.
This query finds phrases applying a stemming algorithm to selected words within the phrases.
Operands: "usability testing" "use testing"
Functionality: phrase queries, stemming
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: ./@number, ./metadata/title/text(), ./content
Comments: This query applies stemming to one word in a phrase. Unlike the wildcard queries in Section 5 (WILDCARD) which allow any suffix, a stemmed query on "us" will not
return "user" and "usability", because they do not share the share root. This query uses an or query introduced in Section 10 (LOGICAL).
These use cases illustrate queries which return synonyms or related words identified by thesauri, dictionaries, and taxonomies.
Find all introductions which quote someone.
This query finds words and phrases using a thesaurus to return synonyms.
Operands: "quote"
Functionality: word query, thesaurus support
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .//introduction
Return: .
Comments: This query uses thesaurus support to identify synonyms for the word "quote" via preferred and used for terms: "said", "says", "stated", "states", "spoke", "speaks", "replied", "replies", "reply", "remarks", "remarked", "responded", "response", "reports", "reported", "quotes", "quoted", "according to", "commented", "discussed", "expressed", and "told". These words and phrases become additional operands.
Find all books with text on improving "web site components".
This query finds words using a thesaurus to identify narrower terms.
Operands: "web site components"
Functionality: phrase query, thesaurus support
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query employs a thesaurus to identify web site components via narrower terms: "layout", "terminology", "graphics", "menus", and "navigation". These words become additional operands.
Are there any "letters" or "holiday cards" in John Wesley Usabilityguy's papers?
This query finds words and phrases using a thesaurus to identify broader terms.
Operands: "letters" "holiday cards"
Functionality: word query, phrase query, thesaurus support
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book[@number="3"]
Query context: ./content
Return: .
Comments: This query employs a thesaurus to identify the broader term "correspondence". It becomes an additional operand.
Find all books with words which sound like "Merrygould".
This query finds words using a dictionary of words which sound like the word queried.
Operands: "Merrygould"
Functionality: word query, sounds-like dictionary support
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: .
Comments: This query uses sounds-like support to identify words which sound like the word "Merrygould". It returns the word "Marigold". Examples of how this query is implemented include keeping a list of similar words (akin to a thesaurus) or using a system based on phonetic similarity.
Find all books which contain words that are close in spelling to "sucessfull".
This query finds words using a dictionary of words that are spelled similarly.
Operands: "sucessfull"
Functionality: word query, similarly spelled dictionary support
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: .
Comments: This query uses support for similarly spelled words to identify words close in spelling to "sucessfull". It returns the word "successful". Examples of how this query is implemented include keeping a list of similar words (akin to a thesaurus) or using a system based on spelling similarities.
Find out whether John Wesley Usabilityguy included research on "AIDS" and "other infectious diseases" among the charities he supported.
This query finds words using a taxonomy to identify subordinate terms.
Operands: "AIDS"
Functionality: word query, case-sensitivity (limited to upper case), taxonomy support
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book[@number="3"]
Query context: ./content/part/component
Return: .
Comments: This query uses a taxonomy to identify other infectious diseases: "Hepatitis" and "Tuberculosis". These words become additional operands.
These use cases query a phrase, one word of which has been identified as a stop word via a stop word list. The first treats the stop word as a stop word. The second does not, making it available again for querying.
Words identified as stop words may be routinely eliminated from queries, allowing any word to be substituted.
Find all books with the phrase "planning then conducting" in the text where "then" is treated as a stop word.
This query finds a phrase substituting any word for a word which has been identified as a stop word via a stop word list.
Operands: "planning then conducting"
Functionality: stop word (then), phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: Once the stop word "then" has been identified via the stop word list at http://bstore1.example.com/StopWordList.xml, this query is reduced to a query on the phrase "planning" any word "conducting", allowing any word as a substitute for the stop word. It finds both "planning and conducting" and "planning then conducting" in the sample data.
Find all books with the phrase "planning then conducting" in the text where "then" is not treated as a stop word.
This query does not eliminate a word from the query even though it has been identified as a stop word in the stop word list, making it available again for querying.
Operands: "planning then conducting"
Functionality: stop word (then), phrase query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: Even though the word "then" has been identified as a stop word, this query makes it available again for querying. It finds only "planning then conducting" in the sample data.
These use cases illustrate queries on words entered with diacritics sometimes finding the same; other times finding words with and without diacritics. They query words entered in upper case sometimes finding the same; other times finding words in both upper and lower case.
Verify the existence of a "résumé" in the papers of John Wesley Usabilityguy.
This query finds a word only when diacritics are present.
Operands: "résumé"
Functionality: word query, functionality requiring presence of characters with diacritics, character wildcard (suffix) (1)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: The desired results include only the words "résumé" and "résumés" with diacritics, not the more often used words "resume" (which is present in the sample data) and "resumes".
Verify the existence of a résumé in the papers of John Wesley Usabilityguy.
This query finds a word whether its diacritics are present or not.
Operands: "resume"
Functionality: word query, functionality allowing substitution of characters with and without diacritics, character wildcard (suffix) (1)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: The desired results include either the words "résumé" or "résumés" with diacritics or the words "resume" or "resumes" without diacritics. The user wants to find résumé, but has entered resume possibly because the system does not allow the entry of diacritics, the user does not know how to enter diacritics, or the user did not want to take the time to enter them.
Find out whether John Wesley Usabilityguy included research on "AIDS" among the charities he supported.
This query finds a word in upper case characters.
Operands: "AIDS"
Functionality: case-sensitivity (limited to upper case), word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: .
Comments: This query does not return the word "aids" with lower case characters which exists in the sample data.
Find out whether John Wesley Usabilityguy included research on "AIDS" among the charities he supported.
This query finds a word with upper or lower case characters.
Operands: "AIDS"
Functionality: word query, case-insensitivity
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: .
Comments: This query returns the word "aids" with characters in upper or lower case.
These use cases include queries containing logical expressions: or, and, the unary not,
and not, and mild not.
Find all books with the words "web" or "software" in the text.
This query finds any or all of the words.
Operands: "web" "software"
Functionality: word query, or query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comment: The or query returns any or all of words queried.
Find all books with the words "web" "software" in the text.
This query finds all of the words.
Operands: "web" "software"
Functionality: word queries, and query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: The and query finds all the words.
Find all book text containing the words "goal" "obstacles" "task" in this order.
This query finds multiple words in the order queried.
Operands: "goal" "obstacles" "task"
Functionality: ordered word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query finds multiple words in a specified order. It is more permissive than a phrase query. It is comparable to an ordered distance query where the number of intervening words is zero or more.
Find all books which do not belong in a collection on "usability testing".
This query finds books which do not contain a phrase in an element and its descendants.
Operands: "usability testing"
Functionality: phrase query, character wildcard (suffix) (0 or more), unary not query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: .
Comments: Unlike the and not query below, the unary not query
requires only one operand. This query has value for information architects and data managers
who will use it for checks such as this one: to find nonconforming data in a document or a
collection.
Find all books with the word "usability" and not the word "plan" in the metadata.
This query finds a word only when another is not found in an element or its descendants.
Operands: "usability" "plan"
Functionality: word query, and not query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata
Return: .
Comments: The and not query is also called a but, but not, and
without query. Unlike the unary not query above,this query requires two operands. Book 2
which contains the words "usability" and "plan" in the metadata is not returned.
Find all books with listings for "résumés", "drafts", or "correspondence", and not "book drafts" in the text.
This query finds books with multiple words and not a phrase containing one of those words.
Operands: "résumés" "drafts" "correspondence" "book drafts"
Functionality: word queries, or query, phrase query, and not query,
functionality requiring presence of diacritics
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query will not return a result the user wants because that result also includes what the user does not want, "book drafts".
Find all books with listings for "résumés", "drafts", or "correspondence", and not "book drafts", in the metadata or text.
This query finds books with multiple words and not a phrase which contains one of the words, while not eliminating a result if it contains the phrase as well as one of the words searched.
Operands: "résumés" "drafts" "correspondence" "book drafts"
Functionality: word queries, or query, phrase query, mild not query,
functionality requiring presence of diacritics
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query will return a result the user wants even though it contains the phrase the user deprecated via the mild not, "book drafts". The user will not lose results which contain what he wants when that book also contains what he does not want. Books containing instances of "book drafts" (a subset of "drafts") are not excluded, merely not considered.
These use cases illustrate instance queries and occurrence count queries. They query words within the same, any, and every instance of an element. Another query finds a phrase only if it occurs over a specified number of times in a book.
Find all books with the phrase "web site" and the word "usability" in the same subject.
This query finds a word and a phrase in the same instance of an element.
Operands: "web site" "usability"
Functionality: phrase query, word query, and query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject
Return: .
Comments: This query finds a word and a phrase in an instance of an element, not allowing one
of the operands to be found in an instance of the element and the other operand in a different instance of
the element. This query does not find Book 2 which has "usability" and "web site" in different instances of the subject element.
Find all books with the phrase "web site" and the word "usability" in any subject.
This query finds a word and a phrase in any instance of an element across the siblings of the same element. The word and the phrase may be in different elements.
Operands: "web site" "usability"
Functionality: phrase query, word query, and query, existential quantification
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject
Return: .
Comments: This query returns words and phrases in any instance of an element, allowing one of the operands to be found in one sibling and the other operand in a different sibling of the same element name.
Find all books with the words "ersatz" and "publications" in every publisher name.
This query finds two words in every instance of an element.
Operands: "ersatz" "publications"
Functionality: word query, and query, universal quantification
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/publicationInfo/publisher
Return: .
Comments: This query does not return a book if at least one of its publishers does not contain the words "ersatz" and
"publications". Book 1 is returned because it has an instance of the publisher element which satisfies the full-text conditions (contains both "Ersatz" and
"Publications"). Book 2 is not returned because even though it has a publisher that satisfies the full-text conditions, it also has a publisher that
does not satisfy it. Book 3 is not returned because it has an instance of the publisher element which
does not satisfy the query (contains "Ersatz" but not "Publications").
Find all books which repeat the phrase "expert review methods" in the text at least two times.
This query finds a phrase which is repeated a specified number of times.
Operands: "expert review methods"
Functionality: phrase query, at least functionality
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query excludes books with only minor (single occurrence) references to "expert review methods".
These use cases illustrate unordered and ordered distance queries which find sequences of words allowing up to a specified number of intervening words. They also include a query to find words within a window, within a sentence, and within a paragraph.
Find all books with information on "software developers".
This query finds multiple words in any order allowing up to a specified number of intervening words.
Operands: "software" "developer"
Functionality: word queries, stemming, unordered distance (0 to 3 intervening words)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query returns "developer of software", which occurs in the sample data.
Find all books with information on "efficient task completion".
This query finds multiple words in the order queried allowing up to a specified number of intervening words.
Operands: "efficient" "task" "completion"
Functionality: word queries, ordered distance (0 to 10 intervening words)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query is more permissive than an phrase query on "efficient task completion" which would return no results.
Find all books about "users feeling well-served".
This query finds books with multiple words within an ordered window of up to a specified number of words.
Operands: "users" "feeling" "well served" "well-served"
Functionality: word queries, ordered window (0 to 15 words)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query opens a window on the first found word (which must be the first word queried) and counts a specified number of words from that first word within which it may find the remaining word or words, finding them in the order queried.
Find all books which discuss "questions asked during cognitive walk-throughs".
This query finds books with multiple words in any order within a sentence.
Operands: "users" "would" "know" "step"
Functionality: word queries, stemming, unordered sentence query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query expects an implementation-defined tokenized sentence or a sentence element.
Find all paragraphs which define what "Web site usability" is.
This query finds books with multiple words and phrases in any order within a paragraph.
Operands: "usability" "web site" "efficiency" "satisfaction"
Functionality: word queries, phrase query, unordered paragraph query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query expects an implementation-defined tokenized paragraph or a paragraph element.
These use cases illustrate queries traversing relative XPath axes.
Find all books with paragraphs containing the phrase "computer workstation" and footnotes within those paragraphs containing the word "comfortable".
This query finds a phrase in an element, then finds a word in a child element.
Operands: "computer workstation" "comfortable"
Functionality: phrase query, word query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .//p, .//p/footnote
Return: ./metadata/title, .//p
Comments: This query combines phrase and word search in different elements which have a parent-child relationship.
Find the first two steps in chapters on "conducting usability tests."
This query finds words in an element, then returns its first two children elements.
Operands: "usability", "test"
Functionality: word queries, stemming
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/chapter/p
Return: ./metadata/title ./content/part/chapter/p/step[1], ./content/part/chapter/p/step[2]
Comments: This query finds words in a p element and uses XPath to return the first two children
of the element.
Are there any "flow diagrams" of "human computer interaction" scenarios in John Wesley Usabilityguy's papers?
This query finds a phrase in an element, then finds another phrase in an ancestor element.
Operands: "flow diagrams" "human computer interaction"
Functionality: phrase queries, character wildcard (suffix) (0 or one)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book[@number="3"]
Query context: ./content/part/component/subcomponent/componentTitle, ./content/part/component/subcomponent/subsubcomponent/componentTitle
Return: ./metadata/title, ./content
Comments: This query looks for a phrase in an element and a different phrase in its ancestor elements.
Find all book chapters with paragraphs on "usability testing" followed by paragraphs on "information architecture".
This query finds a phrase in an element, then finds another phrase in one of its right siblings.
Operands: "usability testing" "information architecture"
Functionality: phrase queries
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/chapter/p
Return: ./metadata/title, .//content
Comments: This query returns book chapters if they contain paragraphs following each other as specified in the query.
These phrase and proximity queries cross element boundaries ignoring the content of descendant elements. One query ignores the content of a complete sub-tree. Other queries ignore only the content of specified descendant elements.
Find advice on whether the observer should "correct" or provide "guidance" to the user during usability "testing".
This query ignores the content of all descendant elements.
Operands: "testing" "correct" "guidance"
Functionality: phrase query, word queries, or query, ordered distance query (0 to 60 intervening words), ignore content of descendant elements
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .//p
Return: .
Comments: This query ignores the content of all the descendant elements of the p element, so it ignores the footnote and testingProcedure elements. If the descendant elements were not ignored, the words searched would be too distant from each other to have been returned.
Find all book chapters containing "users can be tested at any computer workstation or in a lab" ignoring footnotes.
This query finds book chapters containing the phrase "users can be tested at any computer workstation or in a lab" ignoring the content of a descendant element explicitly specified by an XPath expression.
Operands: "users can be tested at any computer workstation or in a lab"
Functionality: phrase query, ignore content of footnote element
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/chapter
Return: ./metadata/title, ./content/part/chapter
Comments: This query ignores the content of a descendant element, the footnote element.
Find all book chapters containing the phrase "at any computer workstation or in a lab" ignoring footnotes on workstations.
This query ignores the content of a descendant element specified by a full-text query.
Operands: "at any computer workstation or in a lab", "workstations"
Functionality: phrase query, character wildcard (suffix) (1), ignore content of a descendant element found by a full-text query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/chapter
Return: ./metadata/title, ./content/part/chapter
Comments: This query ignores the content of a descendant element identified dynamically by a full-text query.
The use cases illustrate a multi-lingual query and queries which use multiple full-text functionalities in conjunction with other XQuery and XPath functionalities.
Find all books with the subject "网站可用性", with an introduction written by "Elina Rose", which mention the name of the usability expert "Millicent Marigold".
This query finds words and a phrase in more than one language.
Operands: "网站可用性" "Elina" "Rose" "Millicent" "Marigold"
Functionality: phrase query, word queries, and query, unordered distance (0 to 3 intervening words), capacity to enter, query, and return multiple languages
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject, ./content/introduction/author, ./content
Return: ./@number, ./metadata/title, ./metadata/subjects/subject, ./content/introduction/author, ./content
Comments: This query accepts multiple languages as input and returns multiple languages as output.
Find all paragraphs in books which discuss the role of "task performance" in "expert review methods".
This query finds multiple words close to each other and a phrase in one instance of an element.
Operands: "task" "performance" "expert review"
Functionality: word queries, stemming, phrase query, unordered distance (0 to 3 intervening words between "task" and "performance")
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content//p
Return: ./metadata/title, ./content//p
Comments: This query combines functionalities introduced in previous sections.
Find all books on "usability testing" which "quote" "Millicent Marigold" on the value of multiple "iterations".
This query finds multiple words in three nested levels of distance queries. It uses wildcards, stemming, and thesaurus support.
Operands: "usability testing" "quote" "millicent" "marigold" "iterations"
Functionality: phrase query, character wildcard (suffix) (0-5), word queries, thesaurus support, stemming, ordered distance (0 to 3 intervening words between "millicent" and "marigold"), unordered distance (0 to 3 intervening words between ("millicent ... marigold" and (one of the following from stemming: "quote", "quoted", "quotes", "quotation", "quotations" or one of the following from thesaurus support: "said", "says", "stated", "states", "statement", "spoke", "speaks", "replied', "replies", "reply", "remarks", "remarked", "responded", "response", "reports ", "reported", "quotes", "quoted", "according", "commented", "discussed", "expressed", "told"), unordered distance (0 to 50 intervening words between ("millicent ... marigold" ... ("quote" or any of its wildcard- or thesaurus-derived substitutes) and ("usability testing" and "iterations")).
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
Comments: This query combines functionalities introduced in previous sections.
Find advice on whether an observer in a "usability test" should "correct" or provide "guidance" to the user in a book not authored by Montana Marigold.
This query uses synonyms supplied by the user, uses the unary not, nests a Boolean query and a phrase query within a window query, and ignores the tags and content of a descendant element.
Operands: "usability testing" "correct" "comment" "guidance" "help" "assistance" "montana" "marigold"
Functionality: phrase query, word queries, character wildcard (suffix) (0 or more), synonyms for "correct" and "guidance" provided by the user ("comment" or "assistance" or "help"), stemming, or query ("correct" or "comment" or "guidance" or "assistance" or "help"), and query ("montana" and "marigold"), unary not query (not "montana" and "marigold"),
unordered window (0 to 70 words within a window of "usability testing" and ("correct" or "comment" or "guidance" or "assistance" or "help"). Ignores content of descendant elements.
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/author, ./content
Return: ./@number, ./metadata/title, ./content
Comments: This query combines functionalities introduced in previous sections.
For each book with a title containing the word "usability", a book introduction containing the word "satisfaction", and a part introduction containing the phrase "identify problems", return the book title and the authors if it has authors. Return the book title and publisher, if it has no authors. Always return the content surrounding the found words.
This query finds words and a phrase in different elements in different sub-trees. It also contains a conditional return.
Operands: "usability" "satisfaction" "identify problems"
Functionality: word queries, phrase query, conditional query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title, ./content/introduction, ./content/part/introduction
Return: ./@number, ./metadata/title, ./metadata/author, ./metadata/publicationInfo/publisher, ./content/introduction, ./content/part/introduction
Comments: This query combines functionalities introduced in previous sections.
These queries combine full-text queries with other XQuery and XPath functionalities.
For books with "usability" in the title create a flat list of all title-author pairs, with each pair enclosed in a newly constructed element.
This query finds a word in an element and returns the element and another wrapped in a new element.
Operands: "usability"
Functionality: word query, construction of new element
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title
Return: result (constructed element), ./metadata/title, ./metadata/author
Comments: This query finds the word "usability" in the title of a book and building title-author pairs for those books returning them wrapped in a newly constructed result element.
Find all books with a chapter title on "usability tests". Return book title, chapter title, and the number of steps in chapters.
This query finds words then returns among other elements a constructed element reporting the number of occurrences of a descendant element.
Operands: "usability" "test"
Functionality: word queries, and query, stemming, count(), construction of new element
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part/chapter/title, ./content/part/chapter/p/step
Return: ./@number, ./metadata/title, ./content/part/chapter/title, number-of-steps (constructed element)
Comments: This query finds the word "usability" and stemmed forms of the word "test" in the titles of
book chapters. It returns chapter titles along with an occurrence count of descendant step elements. The query returns a number of steps equal to
0 if the chapter is on usability testing but does not specify any steps (e.g., there are not descendant step elements).
For each book with "usability" in the book title, return the book title and a second element. Return the book title and a third element if the second element does not exist.
This query finds a word and contains a conditional return.
Operands: "usability"
Functionality: word query, conditional expression
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title
Return: ./@number, ./metadata/title, ./metadata/author, ./metadata/publicationInfo/publisher
Comments: This query finds the word "usability" in the title of a book, then returns title-author pairs
for those books when there are author elements. If there are no author elements, it returns publisher elements.
For each book with "usability" in the book title, return its book title and the round number of its suggested price if the price exceeds $25.
This query finds a word and contains a conditional return based on a function on a numeric value.
Operands: "usability"
Functionality: word query, round(), numeric value comparison, conditional expression
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title, ./metadata/price
Return: ./@number, ./metadata/title, ./metadata/price
Comments: This query finds the word "usability" in the title of a book, then returns the round number of its price if the price exceeds a specified value.
Find all introductions in books, published in "Washington, D.C.", which include listings for "résumés", "drafts", and "correspondence".
This query finds words and a character string.
Operands: "résumés" "drafts" "correspondence" character string "Washington, D.C."
Functionality: word query, functionality requiring presence of characters with diacritics, and query, character string query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/introduction, ./metadata/publicationInfo/place
Return: ./@number, ./metadata/title, ./content//introduction
Comments: This query performs a full-text query when it needs to find word variants in full text and performs a character string query when word variants are not possible.
For each book on "usability" return the book title and a new has-publishers element with value true if the book has more than 1 publisher. Return the title and a new has-publishers element with value false if the book does not have more than one publisher.
This query finds a word, then returns Boolean values based on the number of occurrences of an element.
Operands: "usability"
Functionality: word query, construction of new Boolean values, construction of new element, count, >, conditional expression
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title
Return: ./@number, ./metadata/title, has-publishers (constructed element)
Comments: This query finds "usability" in the title of a book, then returns the title and Boolean values showing whether the book has more than one publisher or not.
Find all books about conducting "usability tests" which have more than one author and are published after "2000".
This query finds a phrase, counts the number of occurrences of an element, runs a greater than comparison on dates, and combines the results.
Operands: "usability testing", "2000"
Functionality: phrase query, character wildcard (suffix) (0 or more), count, >
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/subjects/subject, ./metadata/author, ./metadata/publicationInfo/dateIssued|dateRevised
Return: ./@number, ./metadata/title, ./metadata/author, ./metadata/subjects/subject
Comments: This is a full-text query on the phrase "usability testing" using a wildcard on the word "test", restricted to the subject element. The query
counts the number of author elements, and runs a greater than comparison on dates.
Find all books published after "2001" which share a subject with the book with the short title "Usability Basics".
This query finds words using an XQuery expression to identify the words queried and looks for a publication date after the one specified.
Operands: "Usability Basics", "2001"
Functionality: phrase query, and query, date comparisons, XQuery expression to identify the words queried.
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title/@shortTitle, ./metadata/subjects/subject, ./metadata/publicationInfo/dateIssued|dateRevised
Return: ./metadata/title, ./metadata/author
Comments: This query returns a book if its last date of publication is after 2001 and one of its subjects is the same as a subject of the book with the short title "Usability Basics". This query uses an XQuery expression to dynamically find the subjects of books.
All the queries in these Use Cases may be written with or without score. The Use Cases in this section are merely a small subset that focuses on score.
These queries exploit score and can not be written as queries with pure Boolean full-text predicates. Among these queries are a query that computes and returns only scores, a query which returns only results over a specified threshold, a query which filters by score, and a query which returns all the documents ordered.
Scoring methodologies will not be defined in this recommendation. Scoring is implementation-defined.
Find all books which mention "usability" in the title or the text. Return book titles and scores.
This query performs a word query and returns scores, highest scores first.
Operands: "usability"
Functionality: word query, implementation-defined scoring, returns score, construction of new element
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./metadata/title, ./content
Return: ./@number, ./metadata/title, score (constructed element)
Comments: This query is only possible as a scored query. Scores are included between 0 and 1. The scoring methodology in this use case is for illustrative purposes only. Scoring methodologies will be implementation-defined. This query returns the same results as a query with a pure Boolean full-text predicate. The difference is that the results are scored and the results are returned displaying the score and ranked by score.
Find the best two books on "usability".
This query performs a word query and returns only the results with the two top scores.
Operands: "usability"
Functionality: word query, implementation-defined scoring, returns books with the top two scores, conditional expression
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: ./@number, ./metadata/title
Comments: This query returns results only for the two books with the highest scores. This query is only possible as a scored query. The scoring methodology in this use case is for illustrative purposes only. Scoring methodologies will be implementation-defined. This query returns the same results as a query with a pure Boolean full-text predicate. The difference is that the results are scored and through the introduction of a third variable only the two results with the highest scores are returned.
Find all books that focus on "usability".
This query performs a word query and filters on scores.
Operands: "usability"
Functionality: word query, implementation-defined scoring, filters on scores (accepts only those with score over 0.1)
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: ./@number, ./metadata/title
Comments: This query is only possible as a scored query. The scoring methodology in this use case is for illustrative purposes only. Scoring methodologies will be implementation-defined. This query returns the same results as a query with a pure Boolean full-text predicate. The difference is that the results are scored and then filtered on the scores.
Find all books with parts about "usability testing".
This query finds books which contain parts about usability testing, returning entire books, but without part elements identified as irrelevant via score.
Operands: "usability testing"
Functionality: phrase query, character wildcard (suffix) (0 or more), implementation-defined scoring, filters on scores (under .05), conditional return
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content/part
Return: ./@number, ./metadata/title, ./content/part/@number, ./content/part//title, ./content/part/p
Comments: This query is only meaningful as a scored query. The scoring methodology in this use case is for illustrative purposes only. Scoring methodologies will be implementation-defined. This query returns the same results as a query with a pure Boolean full-text predicate. The difference is that this query filters the part elements. They are included or excluded from the results depending on their score.
Return all books, listing books with text on "software" first.
This query performs a word query, returns all the documents in the database, and orders them returning those with found word first, those without last.
Operands: "software"
Functionality: word query, implementation-defined scoring
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: .
Return: ./@number, ./metadata/title, .
Comments: This query is only meaningful as a scored query. The scoring methodology in this use case is for illustrative purposes only. Scoring methodologies will be implementation-defined. This query returns the more results than a parallel query with a pure Boolean full-text predicate. In a parallel query with a pure Boolean full-text predicate, the last result would have a Boolean value of false and would not be returned. In this scored query the last result receives a score and is returned.
The editors thank the members of the Full-Text Task Force of the XML Query and XSL Working Groups, which produced the material in this document. Special thanks to Stephen Buxton for contributing the first version of the schema.
The editors thank the following staff at the Library of Congress for providing and improving sample data and queries: Ardith Bausenbach, Caroline Arms, Marla Banks, Susan David, Ray Denenberg, Louis Drummond, Bohdan Kantor, Mary A. Lacy, Joe Pagano, Betsy Reifsnyder, Belinda D. Urquiza, and Anne Washington.
Thanks also to Bohdan Kantor, Foster Zhang, François Yergeau, and Michel Biezunski for assistance in translating the subjects in the sample data into Chinese and French.
The editors also wish to thank the members of the W3C Internationalization Working Group for their assistance.
The following references are some of the works considered by the Working Groups in deriving its use cases.
The queries in the Full-Text Use Cases have not yet been tested to ensure they do not cause static errors, such as cardinality errors.
Raised by Michael Rys, Full-Text Redwood Shores meeting, March 30.
None.
| Pat Case | 2003-06-18 | Added a Change Log | |
| Pat Case | 2003-06-18 | Statements of Functionality Illustrated by Query Modified | Added a Data Context to the Statement of Functionality Illustrated by Query for each query. Made XPath expressions in Query Context and Return relative to the XPath expression in Data Context. |
| Sihem Amer-Yahia | 2003-06-18 | Schema Modified | Replaced schema with a shorter one which defines more shared types. |
| Sihem Amer-Yahia | 2003-06-18 | New Use Cases Added | Added the following Use Cases: 3.2.11 Q11 Query on Entire Document, 14.2.11 Q11 Phrase Query Ignoring Explicit List of Tags and Content of Descendant Elements. |
| Pat Case | 2003-06-23 | New Use Case Added | Added the following Use Case: 16.2.7 Q7 Query on Full-Text Combined with Conditional on Date and Full-Text. |
| Pat Case | 2004-02-24 | Solutions in XQuery Added | Added Solutions in XQuery authored by Full Text Task Force Members. |
| Pat Case | 2004-02-24 | Use Case Removed | Removed the following Use Case: 2.2.3 Q3 Single Phrase Query on Long Text Excerpt. |
| Pat Case | 2004-02-24 | Switched Use of Proximity and Distance | Proximity is now the broader term, distance (proximity counting intervening words) and window are the narrower terms. |
| Pat Case | 2004-02-24 | Added Definition of the Word "Tag" | Added definition of the word "tag" to the introduction to the Ignore Section (subsequently moved to the Across Element Boundaries Section). |
| Pat Case | 2004-03-15 | Edited Solutions in XQuery | Made changes such as removing operators and unnecessary parentheses, made stopwords stop words, etc. |
| Pat Case | 2004-03-15 | Query Statements and Expected Results Changed | Made extensive changes to statements of query functionality and expected results to correlate with the new solutions. |
| Pat Case | 2004-04-26 | Use Cases Removed | Removed the following use cases: 3.2.1 Q1 Query on Element, 4.2.1 Q1 Query on Word Ignoring Single Stop Word, 4.2.3 Q3 Query on Phrase Word, 4.2.4 Q4 Query on Phrase Ignoring Multiple Stop Words, 4.2.5 Q5 Query on Phrase Overriding Multiple Stop Words, 6.2.3 Q3 Single Infix Character Wildcard Query, 6.2.5 Q5 0 or More Suffix Character Wildcard Query, 6.2.9 Q9 Word Wildcard Query, 6.2.10 Q10 Specified Range Word Wildcard Query, 9.2.2 Q2 Or Query on More Than Two Words, 9.2.3 Q3 Or Query on Phrases, 9.2.5 Q5 And Query on More Than Two Words, 9.2.6 Q6 And Query on Phrases, 10.2.3 Q3 Unordered Window Query, 10.2.5 Q5 Unordered Within a Sentence Query, 10.2.7 Q7 Unordered Within a Paragraph Query, 12.2.1 Q1 Multiple Word Query, 12.2.2 Q2 Phrase Word Query, 13.2.3 Q3 Query on Element and Its Descendants, 13.2.4 Q4 Query on Element and Its Parent, 13.2.7 Q7 Query on Element and Its Siblings, 13.2.8 Q8 Query on Same Element in Different Sub-Trees, 14.2.2 Q2 Query Ignoring ! Tags Within Multiple Words, 14.2.4 Q4 Phrase Query Ignoring Explicit List of Tags of Descendant Elements, 14.2.8 Q8 Phrase Query Ignoring Tags and Content of Descendant Elements Identified by an XPath Query, 14.2.10 Q10 Distance Query Ignoring All Tags and Content of Descendant Elements, 14.2.11 Q11 Phrase Query Ignoring Explicit List of Tags and Content of Descendant Elements. |
| Pat Case | 2004-04-26 | Reorganized sections, moved and reworked numerous use cases. | Removed the Querying Words and Phrases Section and the Advanced Word and Phrase Query Section. Added sections for Querying Across XML Element Boundaries, Querying on Attribute Values, and Querying Instances of Elements. Reorganized the sections so functionality is introduced before it is used. Revised titles of sections and titles of queries. |
| Pat Case | 2004-04-26 | Use Cases Added | Added the following Use Cases:13.2.6 Q6 Query Combining Score and XML Structure with a Conditional Return, 16.2.8 Q8 Query with an XQuery Expression Within the Full-Text Expression. |
| Pat Case | 2004-04-26 | <authors> Elements Removed | Removed the unnecessary <authors> elements from the sample data, schema, and use cases. |
| Pat Case | 2004-04-26 | Solutions in XPath Added | Added Solutions in XPath authored by Full Text Task Force Members. |
| Pat Case | 2004-04-26 | Query Statements and Expected Results Changed | Made extensive changes to statements of query functionality and expected results to correlate with the new solutions. |
| Pat Case | 2004-05-19 | Renamed and Reversed Order of Sections | The INSTANCE Section was renamed CARDINALITY. The COMPOSABILITY Section was renamed XQUERY-XPATH-COMPOSABILITY and the COMPLEX Section was renamed FULL-TEXT-COMPOSABILITY, and their order in the document was reversed. |
| Pat Case | 2004-09-17 | Removed Version Statements | Removed the "For consideration in v.1" and "For consideration after v.1 version" statements from the Statements of functionality illustrated by query. |
| Pat Case | 2004-09-17 | Changed queries | Changed query statements, solutions, and results based on implementer feedback and Task Force decisions in the following use cases: Use case 14.2.1. Q1 Distance Query Ignoring Content of All Descendant Elements (changed the element whose descendants are ignored to one with content; without content keywords must be followed by an Exp so to ignore all of the descendants added *), Use Case 16.2.8 Q8 Query with XQuery Expression Within Full-Text Expression (changed all to any), Use Case 10.2.5 Q5 And Not Query (added Book 3 as a result), Use Case 15.2.5 Q5 Query on Different Elements in Different Sub-Trees with Conditional Return (added an "s" to problems in a let statement, corrected the $i(s) to $in(s), corrected the book number on the result to 1), Use Case 16.2.4 Q4 Full-Text Query with Numeric Value Comparison (added missing curly brace in element constructor), Use Case 16.2.5 Q5 Full-Text Query with Character String Query (changed metadata for Book 3 and the query to look for Washington, D.C. to make the result valid), Use Case 16.2.8 Q8 Query with XQuery Expression Within Full-Text Expression (Changed the query statement to search the book short title, improved the query and the comment statement), Use Case 13.2.4 Q4 Query on Element and Its Right Siblings (improved query). |
| Pat Case | 2004-09-18 | Added FTUnit to window function | Added the FTUnit "word" to query solutions using the window function. |
| Pat Case | 2004-09-22 | Changed query in XQUERY-XPATH-COMPOSABILITY Section | Changed query statements, solutions, and results based on implementer feedback and Task Force decisions in Use Case 16.2.8 Q8 Query with XQuery Expression Within Full-Text Expression. (made it search any document not only $book, collapsed where clauses). |
| Pat Case | 2005-01-17 | Changed score functionality | Changed the score functions (ft:score) to score clauses in the SCORE Section. |
| Pat Case | 2005-01-17 | Removed use cases from CHARACTER Section | Removed 9.2.5 Query on Word with Special Character and 9.2.6 Query on Word with Special Character or Phrase with Space from the CHARACTER Section. |
| Pat Case | 2005-01-17 | Updated syntax | Updated the syntax for wildcards, stop words, starts-with, entire content, and thesauri. |
| Pat Case | 2005-02-01 | Added XPath example of score functionality | Added XPath example of score clauses in the SCORE Section Q3 Filtering on Scores. |
| Pat Case | 2005-02-02 | Removed explicit unordered | Removed the "unordered" keyword from unordered queries. The default is unordered; the presence of the "ordered" keyword overrides the default. |
| Pat Case | 2005-02-10 | Updated distance and window syntax | Updated distance queries removing the no longer acceptable "with" keyword. Updated window queries removing the no longer acceptable "within" keyword. |
| Pat Case | 2005-03-09 | Updated FTTimes syntax | Updated the FTTimes syntax from "at least 2 occurrences" to "occurs at least 2 times". |
| Pat Case | 2005-03-09 | Added syntax for embedded XQuery | Added syntax (curly braces "{}") around XQuery expressions embedded in XQuery Full-Text expressions. |
| Pat Case | 2005-03-09 | Reformatted URLs in solutions | Reformatted URLs in solutions to enable automatic parsing. |
| Pat Case | 2005-03-09 | Updated thesaurus and stop words syntax | Updated thesaurus and stop words syntax to include the keyword "at" before URLs. |
| Pat Case | 2005-08-08 | Changed FTMildNegation syntax | Changed "mild not" to "not in" in 10.27 Q7 Mild Not Query Where Second Operand Is a Subset of the First Operand. |
| Pat Case | 2005-08-08 | Changed FTIgnore | Edited introductory text to remove level by level ignore which has been postponed until VNext. Deleted 14.2.4 Q4 Distance Query Ignoring Content of Descendant Elements Level by Level. |
| Pat Case | 2005-08-25 | Changed score syntax | Changed to new scoring syntaxes in Section 17. Use cases 1-4 illustrate scored queries returning the same results as a parallel pure Boolean full-text predicate query. 17.2.5 Q5 Query Returning All Books Ordered by Score illustrates a scored query returning more results than a parallel pure Boolean full-text predicate query. |
| Pat Case | 2005-08-25 | Corrected 15.2.4 Q4 | Changed the title of 15.2.4 Q4 Distance and Boolean Queries Ignoring Content of a Descendant Element with Wildcards and Stemming to 15.2.4 Q4 Window Query with Wildcards and Stemming Ignoring Content of a Descendant Element. Rewrote the query. |
| Pat Case | 2005-08-25 | Changed window syntax | Changed to new window syntax, removing FTRange. Changed the syntax in 12.2.3 Q3 Ordered Window Query and 15.2.4 Q4 Window Query with Wildcards and Stemming Ignoring Content of a Descendant Element. |