This document is also available in these non-normative formats: XML.
Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document specifies usage scenarios for full-text queries as part of XQuery [XQuery 1.0: An XML Query Language (Second Edition)] and XPath [XML Path Language (XPath) 2.0 (Second Edition)].
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 at http://www.w3.org/TR/.
This is a Working Group Note as described in the Process Document. It has been jointly developed by the W3C XML Query Working Group and the W3C XSL Working Group, each of which is part of the XML Activity. The Working Groups expect to eventually publish this document as a Working Group Note.
This Use Cases document illustrates a number of use cases that guided the development of the XQuery and XPath Full Text 1.0 specification.
This document incorporates changes made against the Last Call Working Draft of 18 May 2007. Changes to this document since the Last Call Working Draft are detailed in C Change Log.
Please report errors in this document using W3C's public Bugzilla system (instructions can be found at http://www.w3.org/XML/2005/04/qt-bugzilla). If access to that system is not feasible, you may send your comments to the W3C XSLT/XPath/XQuery public comments mailing list<EMAIL_ADDRESS>It will be very helpful if you include the string “[FTUC]” in the subject line of your report, whether made in Bugzilla or in email. Please use multiple Bugzilla entries (or, if necessary, multiple email messages) if you have more than one comment to make. Archives of the comments and responses are available at http://lists.w3.org/Archives/Public/public-qt-comments/.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. At the time of publication, work on this document was considered complete and no further revisions are anticipated. It is a stable document and may be used as reference material or cited from another document. However, this document may be updated, replaced, or made obsolete by other documents at any time.
This document was produced by groups operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the XML Query Working Group and also maintains a public list of any patent disclosures made in connection with the deliverables of the XSL Working Group; those pages also include instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
1 Full Text Use Cases:
Preliminaries
1.1 Proper Display
of this Unicode Document
1.2 Introduction
1.3 Presentation of Use Cases
1.4 Schema for
Sample Data
1.5 Sample
Data
2 Use Case "ELEMENT": Queries on XML Elements
with Simple Content
2.1 Description
2.2 Queries and Results
2.2.1 Q1 Word Query in an Element
2.2.2 Q2 Phrase Query in an
Element
2.2.3 Q3 Phrase Query on Chinese Characters
in an Element
2.2.4 Q4 Query in Different Elements
2.2.5 Q5 Query in an Element Returning Different
Elements
2.2.6 Q6 Starts-with Query
2.2.7 Q7 Entire Element Content
Query
3 Use Case "ACROSS": Queries Across XML Element
Boundaries
3.1 Description
3.2 Queries and Results
3.2.1 Q1 Query Across Descendant Elements
(No Element Content)
3.2.2 Q2 Query Across Descendant Elements
(Highlighting Tags)
3.2.3 Q3 Query Across Descendant Elements
(Substantive Tags)
3.2.4 Q4 Query Across Siblings
3.2.5 Q5 Query in Different
Sub-Trees
3.2.6 Q6 Query on Entire Document
4 Use Case "OTHER": Queries on Attribute
Values
4.1 Description
4.2 Queries and Results
4.2.1 Q1 Query on Attribute
4.2.2 Q2 Query on Element and
Attribute
5 Use Case "WILDCARD": Character Wildcard
Queries
5.1 Description
5.2 Queries and Results
5.2.1 Q1 One Character Suffix Wildcard
Query
5.2.2 Q2 Zero or One Character Prefix
Wildcard Query
5.2.3 Q3 Zero or More Character Infix
Wildcard Query
5.2.4 Q4 One or More Character Suffix
Wildcard Query on Part of a Word
5.2.5 Q5 Specified Range of Characters
Suffix Wildcard Query
6 Use Case "STEMMING": Word Stemming
Queries
6.1 Description
6.2 Queries and Results
6.2.1 Q1 Query Stemming on Word
Root
6.2.2 Q2 Query Stemming on Multiple Word
Roots
7 Use Case "THESAURUS": Queries Which Use
Thesauri, Dictionaries, and Taxonomies
7.1 Description
7.2 Queries and Results
7.2.1 Q1 Query on Synonyms Identified by
a Thesaurus
7.2.2 Q2 Query on Narrower Terms
Identified by a Thesaurus
7.2.3 Q3 Query on Broader Terms
Identified by a Thesaurus
7.2.4 Q4 Query on Word Which Sounds Like
Other Words
7.2.5 Q5 Query on Word Spelled Similarly
to Other Words
7.2.6 Q6 Query on Subordinate Terms
Identified by a Taxonomy
8 Use Case "STOP-WORD": Queries on Stop
Words
8.1 Description
8.2 Queries and Results
8.2.1 Q1 Query on Stop Word Treated as a
Stop Word
8.2.2 Q2 Query on Stop Word Not Treated
as a Stop Word
8.2.3 Q3 Query Excluding a Stop Word on a
Stop Word List
9 Use Case "CHARACTER": Queries Specifying
Normalized Forms of Characters and Tokenized Words
9.1 Description
9.2 Queries and Results
9.2.1 Q1 Diacritics Sensitive
Query
9.2.2 Q2 Diacritics Insensitive
Query
9.2.3 Q3 Query on Word with Upper Case
Characters
9.2.4 Q4 Query on Word with Upper Case
and Lower Case Characters
10 Use Case "LOGICAL": Queries with Logical
Expressions (Or, And, and Not Queries)
10.1 Description
10.2 Queries and Results
10.2.1 Q1 Or Query
10.2.2 Q2 And Query
10.2.3 Q3 And Query Ordered
10.2.4 Q4 Unary Not Query
10.2.5 Q5 And Not Query
10.2.6 Q6 And Not Query Where Second Operand
Is a Subset of the First Operand
10.2.7 Q7 Mild Not Query Where Second
Operand Is a Subset of the First Operand
11 Use Case "CARDINALITY": Queries in Same,
Any, Every Instance of an Element, and Occurrence Count
Query
11.1 Description
11.2 Queries and Results
11.2.1 Q1 Query in Same Instance of an
Element
11.2.2 Q2 Query in Any Instance of an
Element (Existential Quantification)
11.2.3 Q3 Query in Every Instance of an
Element (Universal Quantification)
11.2.4 Q4 Occurrence Count
Query
12 Use Case "PROXIMITY": Queries on Proximity
Relationships Including Distance, Window, Sentence, and
Paragraph
12.1 Description
12.2 Queries and Results
12.2.1 Q1 Unordered Distance
Query
12.2.2 Q2 Ordered Distance Query
12.2.3 Q3 Ordered Window Query
12.2.4 Q4 Unordered Within a Sentence
Query
12.2.5 Q5 Unordered Within a Paragraph
Query
13 Use Case "AXES": Queries Using Relative XPath
Axes
13.1 Description
13.2 Queries and Results
13.2.1 Q1 Query on Element and Its
Children
13.2.2 Q2 Query on Element Returning Its First
Two Children
13.2.3 Q3 Query on Element and Its
Ancestors
13.2.4 Q4 Query on Element and Its Right
Siblings
14 Use Case "IGNORE": Queries Ignoring Descendant
Element Content
14.1 Description
14.2 Queries and Results
14.2.1 Q1 Distance Query Ignoring Content of
All Descendant Elements
14.2.2 Q2 Phrase Query Ignoring Content of
Descendant Element Specified by XPath Expression
14.2.3 Q3 Phrase Query Ignoring Content of
Descendant Element Specified by Full-Text Query
14.2.4 Q4 Distance Query Ignoring Content of
Descendant Elements Level by Level
15 Use Case
"FULL-TEXT-COMPOSABILITY": Queries Illustrating Composability of
Full-Text with Itself
15.1 Description
15.2 Queries and
Results
15.2.1 Q1 Query on Words and
Phrases in Two Languages
15.2.2 Q2 Phrase and
Distance Query in an Instance of an Element With Stemming
15.2.3 Q3 Nested Distance
Query with Wildcards, Stemming, and Thesaurus Support
15.2.4 Q4 Window Query with
Wildcards and Stemming Ignoring Content of a Descendant
Element
15.2.5 Q5 Query on Different
Elements in Different Sub-Trees with Conditional Return
16 Use Case
"XQUERY-XPATH-COMPOSABILITY": Queries Illustrating Composability of
Full-Text with Other XQuery and XPath Functionalities
16.1 Description
16.2 Queries and
Results
16.2.1 Q1 Full-Text Query
Constructing New Element
16.2.2 Q2 Full-Text Query
Returning Count of Descendant Element Occurrences
16.2.3 Q3 Full-Text Query
with Conditional Return
16.2.4 Q4 Full-Text Query
with Numeric Value Comparison
16.2.5 Q5 Full-Text Query
with Character String Query
16.2.6 Q6 Full-Text Query
with Conditional Return of Boolean Values
16.2.7 Q7 Full-Text Query
with Date Comparison and Element Occurrence Count
16.2.8 Q8 Query with
XPath Expression Within Full-Text Expression
16.2.9 Q9 Query Using an
XQuery Expression to Determine the Number of Words Allowed in a
Window
17 Use Case "SCORE": All Queries May Be Written
with Score, Queries in this Section Must Be Written with
Score
17.1 Description
17.2 Queries and Results
17.2.1 Q1 Query Returning Scores
17.2.2 Q2 Query Returning Results with Top
Scores
17.2.3 Q3 Query Filtering on Scores
17.2.4 Q4 Query Combining Score and XML
Structure with a Conditional Return
17.2.5 Q5 Query Returning All Books Ordered by
Score
17.2.6 Q6 Query with Weight
Declaration
A Acknowledgements
B References (Non-Normative)
B.1 References
(Primary)
B.2 References
(Background)
C Change Log (Non-Normative)
(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 XML Query Working Group and the XSL Working Group to illustrate important applications of full-text querying within an XML query language. Each use case exercises a specific functionality relevant to full-text querying. An XML Schema and sample input data are provided. Each use case specifies a query applied to the input data, a solution in XQuery, a solution in XPath (when possible), and the expected results.
The document supplements the XML Query Use Cases which can be found in the W3C XML Query Use Cases [XML Query Use Cases]. Use cases for character string querying are included in the XML Query Use Cases, not in this document.
These use cases:
(1) Present some possible functions and features for tokenized text support in XQuery and XPath.
(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 wildcards, 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) [BYR99] [HTK00]. A few, those in Section 17 (SCORE), cannot be written with Boolean full-text predicates. Scoring methodologies will not be defined in this recommendation. Scoring will be implementation-defined. Results are provided in document order, except those in Section 17 (SCORE). Results could be returned ordered differently, such as by relevance (based on implementation-defined scoring) or explicitly by element.
(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 words 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 that may not be written in XPath include those that contain element constructors and that cannot be written without let, where, and order by clauses.
Examples of full-text querying functionalities for XML query languages can be found in [FGR01], [HTK00], [MJK98], [SCH01] and [TWE00].
To make the output more readable, the output of queries has been formatted using whitespace which may not be returned by a query processor. This whitespace should not be considered normative for the correctness of results.
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.
Solution in XQuery:
Solutions illustrating XQuery Full Text syntax appear here. All queries may be written in XQuery. Solutions are written with pure Boolean full-text predicates and not to invoke scoring, except for those in Section 17 (SCORE), however all the queries in the document may be written as scored queries with the addition of a score variable. All queries are written assuming the default function namespace, without the fn: prefix.
Solution in XPath:
Solutions illustrating XPath Full Text syntax appear (when the query may be written in XPath) here. Solutions are written with pure Boolean full-text predicates and not to invoke scoring, except for those in Section 17 (SCORE), however most of the queries in the document may be written as scored queries with the addition of a score variable. All queries are written assuming the default function namespace, without the fn: prefix.
Expected Result:
Results are provided here.
Found words and phrases are highlighted.
For brevity, only the elements and attributes which meet
the conditions specified in the query are displayed. Others are
replaced with ...s.
 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.xml".
<books> <book number="1"> <metadata> <title shortTitle="Improving Web Site Usability">Improving the Usability of a Web Site Through Expert Reviews and Usability Testing</title> <author>Millicent Marigold</author> <author>Montana Marigold</author> <publicationInfo> <place>New York</place> <publisher>Ersatz Publications</publisher> <dateIssued>2001</dateIssued> <dateRevised>2002</dateRevised> </publicationInfo> <price>25.99</price> <subjects xml:lang="en"> <subject>Usability testing</subject> <subject>Web site development</subject> <subject>Heuristic evaluation</subject> <subject>Cognitive walk-through</subject> <subject>Web site usability</subject> </subjects> <subjects xml:lang="fr"> <subject>Tests d'ergonomie</subject> <subject>Développement de site web</subject> <subject>Évaluation heuristique</subject> <subject>Parcours cognitif</subject> <subject>Ergonomie de site web</subject> </subjects> <subjects xml:lang="zh"> <subject>可用性测试</subject> <subject>网站建置</subject> <subject>启发式评价</subject> <subject>认知推演</subject> <subject>网站可用性</subject> </subjects> </metadata> <content> <introduction> <author>Elina Rose</author>
The usability of a Web site is how well the site supports the user in achieving specified goals. A Web site should facilitate learning, and enable efficient and effective task completion, while propagating few errors. Satisfaction with the site is also important. The user must not only be well-served, but must feel well-served.

Expert reviews and usability testing are methods of identifying problems in layout, terminology, and navigation before they frustrate users and drive them away from your site.

The most successful projects employ multiple methods in multiple iterations. As Millicent Marigold remarked during a recent conference, "Don't stop. Iterate, iterate, then iterate again."

This book has been approved by the Web Site Users Association.
 </introduction> <part number="1"> <title>Expert Reviews</title> <introduction>
Expert reviewers identify problems and recommend changes to web sites based on research in human computer interaction and their experience in the field.

Two expert review methods are discussed here. They are heuristic evaluation and cognitive walk-through.

Expert review methods should be initiated early in the development process, as soon as paper prototypes (hand-drawn pictures of Web pages) or wireframes (electronic mockups) are available. They should be conducted using the hardware and software similar to that employed by users.
 </introduction> <chapter> <title>Heuristic Evaluation</title>
Expert reviewers critique an interface to determine conformance with recognized usability principles. <footnote>One of the best known lists of heuristics is <citation url="http://www.useit.com/papers/heuristic /heuristic_list.html">Ten Usability Heuristics by Jacob Nielson</citation>. Another is <citation url="http://usability.gov /guidelines/index.html"> Research-Based Web Design and Usability Guidelines</citation> </footnote>
 </chapter> <chapter> <title>Cognitive Walk-Through</title>
Expert reviewers evaluate Web site understandability and ease of learning while performing specified tasks. They walk through the site answering questions such as "Would a user know by looking at the screen how to complete the first step of the task?" and "If the user completed the first step, would the user know what to do next?," with the goal of identifying any obstacles to completing the task and assessing whether the user would cognitively be aware that he was successful in completing a step in the process.
 </chapter> </part> <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.

Users are asked to complete tasks which measure the success of the information architecture and navigational elements of the site.

Then changes are made to improve service to users.
 </chapter> </part> </content> </book> <book number="2"> <metadata> <title shortTitle="Usability Basics">Usability Basics: How to Plan for and Conduct Usability Tests on Web Site Thereby Improving the Usability of Your Web Site</title> <publicationInfo> <place>New York</place> <publisher>Ersatz Publications</publisher> <publisher>Electronic BookWorks</publisher> <dateIssued>2000</dateIssued> <dateRevised>2001</dateRevised> </publicationInfo> <price>174.00</price> <subjects xml:lang="en"> <subject>Usability testing</subject> <subject>Web site development</subject> <subject>Guides and finding aids</subject> </subjects> <subjects xml:lang="fr"> <subject>Tests d'ergonomie</subject> <subject>Développement de site web</subject> <subject>Guides et outils de recherche</subject> </subjects> <subjects xml:lang="zh"> <subject>可用性测试</subject> <subject>网站建置</subject> <subject>指南和检索工具</subject> </subjects> </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.

This book has not been approved by the Web Site Users Association.
 </introduction> <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title>
Take the following steps to plan usability testing. <step number="1">Clarify and articulate the goal of the usability testing. </step> <step number="2">Identify tasks which are critical for users to be able to complete successfully.</step> <step number="3">Compile a script of questions or instructions which will prompt the user to attempt those tasks.</step> <step number="4">Identify your users and begin recruiting them.</step> <step number="5">Conduct a pretest on a few users. </step> <step number="6">Edit the script based on insights gleaned from the pretest.</step> <step number="7">Resume testing.</step>
 </chapter> </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title>
Users can be tested at any computer workstation <footnote>They may be more comfortable at their own workstation than in a lab.</footnote> or in a lab.

Give the user the script, then assure them that you are testing the Web site, not them. Users are asked to verbalize their thoughts as they complete the tasks. The event is recorded or someone takes notes. It is often preferable to have two testers, <footnote>Usability testing can be done at great expense or on a shoe string, using <testingProcedure>in-house expertise</testingProcedure> or <testingProcedure>contracting with human computer interaction professionals </testingProcedure>.</footnote> one to ask the questions, another to take notes. Testers should offer no guidance or comments to the user. Mouse movements, typing, expressions, and the user's words should be recorded.
 </chapter> <chapter> <title>Evaluating and Implementing Results</title>
Compile the results and review collectively. Make changes to the site to alleviate the problems found in Web site components which were propagating the largest number of or the most devastating errors. Begin new iterations of testing and changes, until users are successful in the accomplishing the tasks.
 </chapter> </part> </content> </book> <book number="3"> <metadata> <title shortTitle="Usabilityguy Manuscript Guide">John Wesley Usabilityguy: A Register of His Papers</title> <author>Millicent Marigold</author> <author>Morty Marigold</author> <publicationInfo> <place>Washington, D.C.</place> <publisher>Ersatz Manuscript Library</publisher> <dateIssued>1998</dateIssued> <dateRevised>2002</dateRevised> </publicationInfo> <price>21.49</price> <subjects xml:lang="en"> <subject>Computers</subject> <subject>Software evaluation</subject> <subject>Usability testing</subject> <subject>Manuscript collections</subject> </subjects> <subjects xml:lang="fr"> <subject>Ordinateurs</subject> <subject>Évaluation de logiciels</subject> <subject>Tests d'ergonomie</subject> <subject>Collections de manuscrits</subject> </subjects> <subjects xml:lang="zh"> <subject>计算机</subject> <subject>软件评价</subject> <subject>可用性测试</subject> <subject>手稿专藏</subject> </subjects> </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> <part number="1"><container type="box">1-12</container> <title>Subject File, <date normalize="1930/1974"> 1930-1974</date></title> <introduction>
Correspondence, telegrams, memoranda, journals, logs, testimony, approved travel orders, invitations, charts, graphs, forms, biographical data, photographs, book drafts, clippings and other printed matter, résumés and miscellaneous material. Organized by name of person or organization, topic, or type of material.
 </introduction> <component><container type="box">1</container> <componentTitle>Computers</componentTitle> <subComponent> <componentTitle>Software, <componentDate normalize="1946/1947">1946-1947 </componentDate> </componentTitle> </subComponent> <subComponent> <componentTitle>Human Computer Interaction research, <componentDate normalize="1945/1952"> 1945-1952</componentDate> </componentTitle> <subsubComponent> <componentTitle>Flow diagram, <componentDate normalize="1950">1950 </componentDate> </componentTitle> </subsubComponent> <subsubComponent> <componentTitle>General, <componentDate normalize="1947/1951">1947-1951 </componentDate> </componentTitle> </subsubComponent> <subsubComponent><container type="box">2</container> <componentTitle>Eye Movement research, <componentDate normalize="1949/1950">1949-1950 </componentDate> </componentTitle> </subsubComponent> <subsubComponent> <componentTitle>User profiling, <componentDate normalize="1950/1959">1950s </componentDate> </componentTitle> </subsubComponent> </subComponent> </component> <component> <componentTitle>Web User Appreciation Award, <componentDate normalize="1956">1956</componentDate> </componentTitle> </component> </part> <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> <introduction>
Correspondence, articles, book drafts, notes, contracts, clippings, and printed matter. Arranged alphabetically by type (articles, books, reports, and miscellaneous) and therein alphabetically by type of material, subject, or title.
 </introduction> <component> <componentTitle>Writings by Usabilityguy </componentTitle> <subComponent> <componentTitle><componentDate normalize="1996"> 1996</componentDate> </componentTitle> <subsubComponent> <componentTitle>"How Many Users Are Enough for User Testing?"</componentTitle> </subsubComponent> <subsubComponent> <componentTitle>"How to Evaluate Results from User Tests."</componentTitle> </subsubComponent> <subsubComponent> <container type="box">5</container> <componentTitle>"When Are You Done Testing?" </componentTitle> </subsubComponent> <subsubComponent> <componentTitle>"Do-It-Yourself User Testing" </componentTitle> </subsubComponent> </subComponent> </component> <component> <componentTitle>Charitable Contributions </componentTitle> <subComponent> <componentTitle>Diseases: AIDS, Hepatitis, Tuberculosis <componentDate normalize= "1990/1999">1990-1999</componentDate> </componentTitle> </subComponent> <subComponent> <componentTitle>Environmental Conservation: Rivers <componentDate normalize="1995">1995 </componentDate> </componentTitle> </subComponent> </component> </part> </content> </book> </books>
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".
Solution in XQuery:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/title[. contains text "usability"]
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/title[. contains text "usability"]
Expected Result:
<title shortTitle="Improving Web Site Usability">Improving the Usability of a Web Site Through Expert Reviews and Usability Testing</title> <title shortTitle="Usability Basics">Usability Basics: How to Plan for and Conduct Usability Tests on Web Site Thereby Improving the Usability of Your Web Site</title>
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.
Solution in XQuery:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/subjects/subject[. contains text "usability testing"]
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/subjects/subject[. contains text "usability testing"]
Expected Result:
<subject>Usability testing</subject> <subject>Usability testing</subject> <subject>Usability testing</subject>
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.
Solution in XQuery:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/subjects/subject[. contains text "网站" using language "zh"]
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/subjects/subject[. contains text "网站" using language "zh"]
Expected Result:
<subject>网站建置</subject> <subject>网站可用性</subject> <subject>网站建置</subject>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $title := $book/(metadata|content/part/chapter)/title where $title contains text "usability tests" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[(metadata|content/part/chapter) /title contains text "usability tests"]
Expected Result:
<book number="2"> <metadata> ... <title shortTitle="Usability Basics">Usability Basics: How to Plan for and Conduct Usability Tests on Web Site Thereby Improving the Usability of Your Web Site</title> ... </metadata> <content> ... <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title> ... </chapter> </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title> ... </chapter> </part> .... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book where $book/metadata/subjects/subject contains text "usability testing" return $book/metadata/(title|author)
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[metadata/subjects/subject contains text "usability testing"]/metadata/(title|author)
Expected Result:
<title shortTitle="Improving Web Site Usability">Improving the Usability of a Web Site Through Expert Reviews and Usability Testing</title> <author>Millicent Marigold</author> <author>Montana Marigold</author> <title shortTitle="Usability Basics">Usability Basics: How to Plan for and Conduct Usability Tests on Web Site Thereby Improving the Usability of Your Web Site</title> <title shortTitle="Usabilityguy Manuscript Guide">John Wesley Usabilityguy: A Register of His Papers</title> <author>Millicent Marigold</author> <author>Morty Marigold</author>
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., Journal of Psychology) in
large library collections. This query does not find Book 2 which
contains the phrase "improving the usability" in the
title
element, because the title
element
does not start with "improving".
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $title := $book/metadata/title where $title contains text "improving" ftand "usability" ordered distance at most 2 words at start return $title
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/title[. contains text "improving" ftand "usability" ordered distance at most 2 words at start]
Expected Result:
<title shortTitle="Improving Web Site Usability">Improving
the Usability of a Web Site Through Expert Reviews and
Usability Testing</title>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $exactTitle := $book/metadata/title where $exactTitle contains text "improv.* the usability of a web site through expert reviews and usability testing" using wildcards entire content return $exactTitle
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book/metadata/title[. contains text "improv.* the usability of a web site through expert reviews and usability testing" using wildcards entire content]
Expected Result:
<title shortTitle="Improving Web Site Usability">Improving
the Usability of a Web Site Through Expert Reviews and
Usability Testing</title>
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.
Find queries in an element which do not query some or all of its descendant elements in Section 14 (IGNORE).
Find queries on attribute values in Section 4 (OTHER).
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 names,
attribute names, and attribute values, have been removed by
tokenization.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $chap := $book//chapter where $chap contains text "one of the best known lists of heuristics is Ten Usability Heuristics" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[.//chapter contains text "one of the best known lists of heuristics is Ten Usability Heuristics"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="1"> ... <chapter> <title>Heuristic Evaluation</title>
Expert reviewers critique an interface to determine conformance with recognized usability principles. <footnote>One of the best known lists of heuristics is <citation url="http://www.useit.com/papers/heuristic /heuristic_list.html"> Ten Usability Heuristics by Jacob Nielson</citation>. Another is <citation url="http://usability.gov /guidelines/index.html"> Research-Based Web Design and Usability Guidelines</citation> </footnote>
 </chapter> ... </part> ... </content> </book>
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 have been removed by
tokenization.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $intro := $book/content/part/introduction where $intro contains text "prototypes" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content/part/introduction contains text "prototypes"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="1"> <introduction>
Expert review methods should be initiated early in the development process, as soon as paper prototypes (hand-drawn pictures of Web pages) or wireframes (electronic mockups) are available. They should be conducted using the hardware and software similar to that employed by users.
 </introduction> ... </part> ... </content> </book>
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 names, attribute names, and attribute
values, have been removed by tokenization, including
part
, chapter
, title
,
p
, component
, subComponent
,
subsubComponent
, and componentTitle
tags.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "tests" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "tests"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.
 ... </chapter> </part> ... </content> </book> <book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.
 ... </introduction> <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title> ... </chapter> </part> ... </content> </book> <book number="3"> <metadata> ... </metadata> <content> ... <component> <componentTitle>Writings by Usabilityguy </componentTitle> <subComponent> <componentTitle><componentDate normalize="1996"> 1996</componentDate> </componentTitle> ... <subsubComponent> <componentTitle>"How to Evaluate Results from User Tests."</componentTitle> </subsubComponent> </subComponent> ... <component> ... </content> </book>
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 names, attribute names, and attribute
values, have been removed by tokenization, including
title
and p
tags.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "usability testing once the problems" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "usability testing once the problems"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.
 ... </chapter> </part> </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $intro := $book/content/(introduction|part/introduction) where $intro [./p contains text "identif.*" using wildcards] return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content/(introduction|part/introduction) contains text "identif.*" using wildcards]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
Expert reviews and usability testing are methods of identifying problems in layout, terminology, and navigation before they frustrate users and drive them away from your site.
 ... </introduction> <part number="1"> <title>Expert Reviews</title> <introduction>
Expert reviewers identify problems and recommend changes to web sites based on research in human computer interaction and their experience in the field.
 ... </introduction> ... </part> </content> </book>
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: This query 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 names, attribute names, 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.
Solution in XQuery:
doc("http://bstore1.example.com/full-text.xml")[. contains text "mouse"]/books/book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml")[. contains text "mouse"]/books/book
Expected Result:
<book number="1">
<metadata>
...
</metadata>
<content>
...
</content>
</book>
<book number="2">
<metadata>
...
</metadata>
<content>
...
<part number="2">
<chapter>
<title>Conducting Usability Tests</title>
...

Give the user the script, then assure them
that you are testing the Web site, not them.
Users are asked to verbalize their thoughts as
they complete the tasks. The event is recorded
or someone takes notes. It is often preferable
to have two testers, <footnote>Usability
testing can be done at great expense or on a
shoe string, using <testingProcedure>in-house
expertise</testingProcedure> or
<testingProcedure>contracting with human
computer interaction professionals
</testingProcedure>.</footnote> one to ask the
questions, another to take notes. Testers should
offer no guidance or comments to the user. Mouse
movements, typing, expressions, and the user's
words should be recorded.

</chapter>
...
</part>
</content>
</book>
<book number="3">
<metadata>
...
</metadata>
<content>
...
</content>
</book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book where $book/metadata/title/@shortTitle contains text "improve" using stemming ftand "web" ftand "usability" distance at most 2 words return $book/metadata/title
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[metadata/title/@shortTitle contains text "improve" using stemming ftand "web" ftand "usability" distance at most 2 words]/metadata/title
Expected Result:
<title shortTitle="Improving Web Site Usability">Improving the Usability of a Web Site Through Expert Reviews and Usability Testing</title>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $stitle := $book/metadata/title/@shortTitle let $ctitle := $book//componentTitle where $stitle contains text "manuscript guides" using stemming and $ctitle contains text "user profiling" using stemming return data($stitle)
Solution in XPath: None
Expected Result:
Usabilityguy Manuscript Guide
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "test." using wildcards return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "test." using wildcards]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.
 ... </chapter> </part> </content> </book> <book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.

This book has not been approved by the Web Site Users Association.
 </introduction> <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title> ... </chapter> </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title> ... </chapter> ... </part> ... </content> </book> <book number="3"> <metadata> ... </metadata> <content> ... <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> ... <component> <componentTitle>Writings by Usabilityguy </componentTitle> <subComponent> <componentTitle><componentDate normalize="1996"> 1996</componentDate> </componentTitle> ... <subsubComponent> <componentTitle>"How to Evaluate Results from User Tests."</componentTitle> </subsubComponent> ... </subComponent> ... </component> ... </part> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text ".?way" using wildcards return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text ".?way" using wildcards]
Expected Result:
<book number="1">
<metadata>
...
</metadata>
<content>
<introduction>
...

Expert reviews and usability testing are
methods of identifying problems in layout,
terminology, and navigation before they frustrate
users and drive them away from your site.

...
</introduction>
...
</content>
</book>
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: concat(./@number, ", ", ./metadata/title)
Comments: This query finds the word "service" and would find the word "serve" if it existed in the sample data. It does not find the word "served" which exists in the sample data.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "serv.*e" using wildcards return (concat($book/@number, ", ", $book/metadata/title))
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "serv.*e" using wildcards] /concat(@number, ", " , metadata/title)
Expected Result:
1, Improving the Usability of a Web Site Through Expert Reviews and Usability Testing
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: concat(./@number, ", ", ./metadata/title)
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 find linguistic variants of a word or the root of a word, wildcards may be applied to any part of a word and will find all character combinations found.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "us.+ testing" using wildcards return (concat($book/@number, ", ", $book/metadata/title))
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "us.+ testing" using wildcards]/concat(@number, ", ", metadata/title)
Expected Result:
1, Improving the Usability of a Web Site Through Expert Reviews and Usability Testing 2, Usability Basics: How to Plan for and Conduct Usability Tests on Web Site Thereby Improving the Usability of Your Web Site 3, John Wesley Usabilityguy: A Register of His Papers
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: .
Comments: This query allows any three or four character suffix. It finds "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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "test.{3,4}" using wildcards return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "test.{3,4}" using wildcards]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
Expert reviews and usability testing are methods of identifying problems in layout, terminology, and navigation before they frustrate users and drive them away from your site.
 ... </introduction> ... <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.
 ... </chapter> </part> </content> </book> <book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.
 ... </introduction> <part number="1"> <chapter>
Take the following steps to plan usability testing. <step number="1">Clarify and articulate the goal of the >usability testing. <step number="1">Clarify and articulate the goal of the usability testing. </step> <step number="2">Identify tasks which are critical for users to be able to complete successfully.</step> <step number="3">Compile a script of questions or instructions which will prompt the user to attempt those tasks.</step> <step number="4">Identify your users and begin recruiting them.</step> <step number="5">Conduct a pretest on a few users. </step> <step number="6">Edit the script based on insights gleaned from the pretest.</step> <step number="7">Resume testing.</step>
 </chapter> </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title> ...
Give the user the script, then assure them that you are testing the Web site, not them. Users are asked to verbalize their thoughts as they complete the tasks. The event is recorded or someone takes notes. It is often preferable to have two testers, <footnote>Usability testing can be done at great expense or on a shoe string, using <testingProcedure>in-house expertise</testingProcedure> or <testingProcedure>contracting with human computer interaction professionals </testingProcedure>.</footnote> one to ask the questions, another to take notes. Testers should offer no guidance or comments to the user. Mouse movements, typing, expressions, and the user's words should be recorded.
 </chapter> <chapter> <title>Evaluating and Implementing Results</title>
Compile the results and review collectively. Make changes to the site to alleviate the problems found in Web site components which were propagating the largest number of or the most devastating errors. Begin new iterations of testing and changes, until users are successful in the accomplishing the tasks.
 </chapter> </part> </content> </book> <book number="3"> <metadata> ... </metadata> <content> ... <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> ... <component> <componentTitle>Writings by Usabilityguy </componentTitle> <subComponent> <componentTitle><componentDate normalize="1996"> 1996</componentDate> </componentTitle> <subsubComponent> <componentTitle>"How Many Users Are Enough for User Testing?"</componentTitle> </subsubComponent> ... <subsubComponent> <componentTitle>"When Are You Done Testing?" </componentTitle> </subsubComponent> <subsubComponent> <componentTitle>"Do-It-Yourself User Testing" </componentTitle> </subsubComponent> </subComponent> </component> ... </part> </content> </book>
These use cases invoke a stemming algorithm (e.g., Porter) which finds 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "test" using stemming return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "test" using stemming]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
Expert reviews and usability testing are methods of identifying problems in layout, terminology, and navigation before they frustrate users and drive them away from your site.
 ... </introduction> ... <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.
 ... </chapter> </part> </content> </book> <book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.
 ... </introduction> <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title>
Take the following steps to plan usability testing. <step number="1">Clarify and articulate the goal of the usability testing. </step> <step number="2">Identify tasks which are critical for users to be able to complete successfully.</step> <step number="3">Compile a script of questions or instructions which will prompt the user to attempt those tasks.</step> <step number="4">Identify your users and begin recruiting them.</step> <step number="5">Conduct a pretest on a few users. </step> <step number="6">Edit the script based on insights gleaned from the pretest.</step> <step number="7">Resume testing.</step>
 </chapter> </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title>
Users can be tested at any computer workstation <footnote>They may be more comfortable at their own workstation than in a lab.</footnote> or in a lab.

Give the user the script, then assure them that you are testing the Web site, not them. Users are asked to verbalize their thoughts as they complete the tasks. The event is recorded or someone takes notes. It is often preferable to have two testers, <footnote>Usability testing can be done at great expense or on a shoe string, using <testingProcedure>in-house expertise</testingProcedure> or <testingProcedure>contracting with human computer interaction professionals </testingProcedure>.</footnote> one to ask the questions, another to take notes. Testers should offer no guidance or comments to the user. Mouse movements, typing, expressions, and the user's words should be recorded.
 </chapter> <chapter> <title>Evaluating and Implementing Results</title>
Compile the results and review collectively. Make changes to the site to alleviate the problems found in Web site components which were propagating the largest number of or the most devastating errors. Begin new iterations of testing and changes, until users are successful in the accomplishing the tasks.
 </chapter> </part> </content> </book> <book number="3"> <metadata> ... </metadata> <content> ... <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> ... <component> <componentTitle>Writings by Usabilityguy </componentTitle> <subComponent> <componentTitle><componentDate normalize="1996"> 1996</componentDate> </componentTitle> <subsubComponent> <componentTitle>"How Many Users Are Enough for User Testing?"</componentTitle> </subsubComponent> <subsubComponent> <componentTitle>"How to Evaluate Results from User Tests."</componentTitle> </subsubComponent> <subsubComponent> <container type="box">5</container> <componentTitle>"When Are You Done Testing? </componentTitle> </subsubComponent> <subsubComponent> <componentTitle>"Do-It-Yourself User Testing" </componentTitle> </subsubComponent> </subComponent> </component> ... </part> </content> </book>
Find all books with the phrases "usability testing" or "users testing" in the text.
This query finds phrases applying a stemming algorithm to selected words within the phrases.
Operands: "usability testing" "users testing"
Functionality: phrase queries, stemming
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: .
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 find "user" and
"usability", because they do not share the same root. This query
uses an ftor
query introduced in Section 10
(LOGICAL).
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text ("usability" using stemming ftand "testing" phrase) ftor ("users" using stemming ftand "testing" phrase) return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text ("usability" using stemming ftand "testing" phrase) ftor ("users" using stemming ftand "testing" phrase)]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
Expert reviews and usability testing are methods of identifying problems in layout, terminology, and navigation before they frustrate users and drive them away from your site.
 ... </introduction> ... <part number="2"> <chapter> <title>Usability Testing</title>
Once the problems identified by expert reviews have been corrected, it is time to conduct some tests of the site with your unique audience or audiences by conducting usability testing.
 ... </chapter> </part> </content> </book> <book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.
 ... </introduction> <part number="1"> <chapter>
Take the following steps to plan usability testing. <step number="1">Clarify and articulate the goal of the usability testing. <step number="1">Clarify and articulate the goal of the usability testing. </step> <step number="2">Identify tasks which are critical for users to be able to complete successfully.</step> <step number="3">Compile a script of questions or instructions which will prompt the user to attempt those tasks.</step> <step number="4">Identify your users and begin recruiting them.</step> <step number="5">Conduct a pretest on a few users. </step> <step number="6">Edit the script based on insights gleaned from the pretest.</step> <step number="7">Resume testing.</step>
 </chapter> </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title> ...
Give the user the script, then assure them that you are testing the Web site, not them. Users are asked to verbalize their thoughts as they complete the tasks. The event is recorded or someone takes notes. It is often preferable to have two testers, <footnote>Usability testing can be done at great expense or on a shoe string, using <testingProcedure>in-house expertise</testingProcedure> or <testingProcedure>contracting with human computer interaction professionals </testingProcedure>.</footnote> one to ask the questions, another to take notes. Testers should offer no guidance or comments to the user. Mouse movements, typing, expressions, and the user's words should be recorded.
 </chapter> ... </part> </content> </book> <book number="3"> <metadata> ... </metadata> <content> ... <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> ... <component> <componentTitle>Writings by Usabilityguy </componentTitle> <subComponent> <componentTitle><componentDate normalize="1996"> 1996</componentDate> </componentTitle> <subsubComponent> <componentTitle>"How Many Users Are Enough for User Testing?"</componentTitle> </subsubComponent> ... <subsubComponent> <subsubComponent><componentTitle>"Do-It- Yourself User Testing" </componentTitle> </subsubComponent> </subComponent> </component> ... </part> </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $intro := $book//introduction where $intro contains text "quote" using thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml" relationship "synonyms" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[.//introduction contains text "quote" using thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml" relationship "synonyms"]
Expected Result:
<book number="1">
<metadata>
...
</metadata>
<content>
...
<introduction>
...

The most successful projects employ multiple
methods in multiple iterations. As Millicent
Marigold remarked during a recent conference,
"Don't stop. Iterate, iterate, then iterate
again."

...
</introduction>
</content>
</book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "web site components" using thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml" relationship "narrower term" at most 2 levels return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "web site components" using thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml" relationship "narrower term" at most 2 levels]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
Expert reviews and usability testing are methods of identifying problems in layout, terminology, and navigation before they frustrate users and drive them away from your site.
 ... </introduction> ... </content> </book> <book number="2"> <metadata> ... </metadata> <content> ... <part number="2"> ... <chapter> <title>Evaluating and Implementing Results</title>
Compile the results and review collectively. Make changes to the site to alleviate the problems found in Web site components which were propagating the largest number of or the most devastating errors. Begin new iterations of testing and changes, until users are successful in the accomplishing the tasks.
 </chapter> </part> </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book[@number="3"] let $cont := $book/content where $cont contains text ("letters" ftor "holiday cards") using thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml" relationship "BT" exactly 1 levels return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text ("letters" ftor "holiday cards") using thesaurus at "http://bstore1.example.com/UsabilityThesaurus.xml" relationship "BT" exactly 1 levels]
Expected Result:
<book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> <part number="1"><container type="box">1-12</container> <title>Subject File, <date normalize="1930/1974"> 1930-1974</date></title> <introduction>
Correspondence, telegrams, memoranda, journals, logs, testimony, approved travel orders, invitations, charts, graphs, forms, biographical data, photographs, book drafts, clippings and other printed matter, résumés and miscellaneous material. Organized by name of person or organization, topic, or type of material.
 </introduction> </part> <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> <introduction>
Correspondence, articles, book drafts, notes, contracts, clippings, and printed matter. Arranged alphabetically by type (articles, books, reports, and miscellaneous) and therein alphabetically by type of material, subject, or title.
 </introduction> ... </part> </content> </book>
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 finds 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text "Merrygould" using thesaurus at "http://bstore1.example.com/UsabilitySoundex.xml" relationship "sounds like"] return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text "Merrygould" using thesaurus at "http://bstore1.example.com/UsabilitySoundex.xml" relationship "sounds like"]
Expected Result:
<book number="1"> <metadata> <title shortTitle="Improving Web Site Usability">Improving the Usability of a Web Site Through Expert Reviews and Usability Testing</title> <author>Millicent Marigold</author> <author>Montana Marigold</author> ... </metadata> <content> <introduction> ...
The most successful projects employ multiple methods in multiple iterations. As Millicent Marigold remarked during a recent conference, "Don't stop. Iterate, iterate, then iterate again."
 ... </introduction> </content> </book> <book number="3"> <metadata> <title shortTitle="Usabilityguy Manuscript Guide">John Wesley Usabilityguy: A Register of His Papers</title> <author>Millicent Marigold</author> <author>Morty Marigold</author> ... </metadata> <content> ... </content> </book>
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 finds 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text "sucessfull" using thesaurus at "http://bstore1.example.com/spellcheck.xml" relationship "misspelling of"] return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text "sucessfull" using thesaurus at "http://bstore1.example.com/spellcheck.xml" relationship "misspelling of"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <introduction> ...
The most successful projects employ multiple methods in multiple iterations. As Millicent Marigold remarked during a recent conference, "Don't stop. Iterate, iterate, then iterate again."
 ... </introduction> <part number="1"> <title>Expert Reviews</title> ... <chapter> <title>Cognitive Walk-Through</title>
Expert reviewers evaluate Web site understandability and ease of learning while performing specified tasks. They walk through the site answering questions such as "Would a user know by looking at the screen how to complete the first step of the task?" and "If the user completed the first step, would the user know what to do next?," with the goal of identifying any obstacles to completing the task and assessing whether the user would cognitively be aware that he was successful in completing a step in the process.
 </chapter> </part> ... </content> </book> <book number="2"> <metadata> ... </metadata> <content> ... <part number="2"> ... <chapter> <title>Evaluating and Implementing Results</title>
Compile the results and review collectively. Make changes to the site to alleviate the problems found in Web site components which were propagating the largest number of or the most devastating errors. Begin new iterations of testing and changes, until users are successful in the accomplishing the tasks.
 </chapter> </part> </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book[@number="3"] let $comp := $book//component where $comp contains text "AIDS" using uppercase using thesaurus at "http://bstore1.example.com/OurTaxonomy.xml" relationship "disease in this category" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[@number="3" and .//component contains text "AIDS" using uppercase using thesaurus at "http://bstore1.example.com/OurTaxonomy.xml" relationship "disease in this category"]
Expected Result:
<book number="3"> <metadata> ... </metadata> <content> ... <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> ... <component> <componentTitle>Charitable Contributions </componentTitle> <subComponent> <componentTitle>Diseases: AIDS, Hepatitis, Tuberculosis<componentDate normalize= "1990/1999">1990-1999</componentDate> </componentTitle> </subComponent> <subComponent> <componentTitle>Environmental Conservation: Rivers <componentDate normalize="1995">1995 </componentDate> </componentTitle> </subComponent> </component> </part> </content> </book>
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. Another query calls a stop word list then excludes a word on the list making that word available 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "planning then conducting" using stop words at "http://bstore1.example.com/StopWordList.xml" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "planning then conducting" using stop words at "http://bstore1.example.com/StopWordList.xml"]
Expected Result:
<book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.

This book has not been approved by the Web Site Users Association.
 </introduction> <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title> ... </chapter> </part> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "planning then conducting" using no stop words return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "planning then conducting" using no stop words]
Expected Result:
<book number="2">
<metadata>
...
</metadata>
<content>
...
<part number="1">
<chapter>
<title>Planning then Conducting Usability
Tests</title>
...
</chapter>
</part>
...
</content>
</book>
Find books with the phrase "not been approved" in the text.
This query finds a phrase substituting any words for words which have been identified as stop words via a stop word list, removing the word "not" temporarily from the stop word list.
Operands: "not been approved"
Functionality: phrase query, stop word list (not, been), the stop word "not" is excluded from the list and used in the query
Data context: doc("http://bstore1.example.com/full-text.xml")/books/book
Query context: ./content
Return: ./metadata/title, ./content
Comments: The stop words "not" and "been" are identified via a stop word list, however the stop word "not" is removed temporarily from the stop word list and used as an operand in the query. The query becomes a query on the phrase "not" [any word] "approved", allowing any word as a substitute for the stop word "been". It does not return books with the word "approved" in the phrases "been approved" and "approved travel orders" in the sample data.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "not been approved" using stop words at "http://bstore1.example.com/StopWordList.xml" except ("not") return ($book/metadata/title, $cont)
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "not been approved" using stop words at "http://bstore1.example.com/StopWordList.xml" except ("not")]/(metadata/title, content)
Expected Result:
<title shortTitle="Usability Basics">Usability
Basics: How to Plan for and Conduct
Usability Tests on Web Site Thereby Improving the
Usability of Your Web Site</title>
<content>
...

This book has not been approved by the Web Site
Users Association

...
</content>
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 if it contains the diacritics as written in the query.
Operands: "résumé"
Functionality: word query, functionality requiring presence of diacritics as written in the query, 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 as written in the query, not the more often used words "resume" (which is present in the sample data) and "resumes".
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "résumé.?" using wildcards using diacritics sensitive return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "résumé.?" using wildcards using diacritics sensitive]
Expected Result:
<book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> <part number="1"><container type="box">1-12</container> <title>Subject File, <date normalize="1930/1974"> 1930-1974</date></title> <introduction>
Correspondence, telegrams, memoranda, journals, logs, testimony, approved travel orders, invitations, charts, graphs, forms, biographical data, photographs, book drafts, clippings and other printed matter, résumés and miscellaneous material. Organized by name of person or organization, topic, or type of material.
 </introduction> ... </part> ... </content> </book>
Verify the existence of a résumé in the papers of John Wesley Usabilityguy.
This query finds a word whether diacritics are present or not.
Operands: "resume"
Functionality: word query, functionality finding words 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. Whether diacritics are written in the query or not is not considered.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "resume.?" using wildcards using diacritics insensitive return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "resume.?" using wildcards using diacritics insensitive]
Expected Result:
<book number="2"> <metadata> ... </metadata> <content> ... <part number="1"> <chapter> <title>Planning then Conducting Usability Tests</title>
Take the following steps to plan usability testing. <step number="1">Clarify and articulate the goal of the usability testing. </step> <step number="2">Identify tasks which are critical for users to be able to complete successfully.</step> <step number="3">Compile a script of questions or instructions which will prompt the user to attempt those tasks.</step> <step number="4">Identify your users and begin recruiting them.</step> <step number="5">Conduct a pretest on a few users. </step> <step number="6">Edit the script based on insights gleaned from the pretest.</step> <step number="7">Resume testing.</step>
 </chapter> </part> ... </content> </book> <book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> <part number="1"><container type="box">1-12</container> <title>Subject File, <date normalize="1930/1974"> 1930-1974</date></title> <introduction>
Correspondence, telegrams, memoranda, journals, logs, testimony, approved travel orders, invitations, charts, graphs, forms, biographical data, photographs, book drafts, clippings and other printed matter, résumés and miscellaneous material. Organized by name of person or organization, topic, or type of material.
 </introduction> ... </part> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book where $book[. contains text "AIDS" using uppercase] return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text "AIDS" using uppercase]
Expected Result:
<book number="3">
<metadata>
...
</metadata>
<content>
...
<part number="2"><container type="box">3-5</container>
<title>Writings File,
<date normalize="1985/1999">1985-1999</date>
</title>
...
<component>
<componentTitle>Charitable Contributions
</componentTitle>
<subComponent>
<componentTitle>Diseases: AIDS, Hepatitis,
Tuberculosis <componentDate normalize=
"1990/1999">1990-1999</componentDate>
</componentTitle>
</subComponent>
...
</component>
</part>
</content>
</book>
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 finds the word "aids" with characters in upper or lower case.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book where $book contains text "AIDS" using case insensitive return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text "AIDS" using case insensitive]
Expected Result:
<book number="2"> <metadata> ... <subjects xml:lang="en"> <subject>Usability testing</subject> <subject>Web site development</subject> <subject>Guides and finding aids</subject> </subjects> ... </metadata> <content> ... </content> </book> <book number="3"> <metadata> ... </metadata> <content> ... <part number="2"><container type="box">3-5</container> <title>Writings File, <date normalize="1985/1999">1985-1999</date> </title> ... <component> <componentTitle>Charitable Contributions </componentTitle> <subComponent> <componentTitle>Diseases: AIDS, Hepatitis, Tuberculosis <componentDate normalize= "1990/1999">1990-1999</componentDate> </componentTitle> </subComponent> ... </component> </part> </content> </book>
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 finds any or all of words
queried.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "web" ftor "software" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "web" ftor "software"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
The usability of a Web site is how well the site supports the user in achieving specified goals. A Web site should facilitate learning, and enable efficient and effective task completion, while propagating few errors. Satisfaction with the site is also important. The user must not only be well-served, but must feel well-served.
 ...
This book has been approved by the Web Site Users Association.
 </introduction> <part number="1"> <title>Expert Reviews</title> <introduction>
Expert reviewers identify problems and recommend changes to web sites based on research in human computer interaction and their experience in the field.
 ...
Expert review methods should be initiated early in the development process, as soon as paper prototypes (hand-drawn pictures of Web pages) or wireframes (electronic mockups) are available. They should be conducted using the hardware and software similar to that employed by users.
 </introduction> <chapter> <title>Heuristic Evaluation</title>
Expert reviewers critique an interface to determine conformance with recognized usability principles. <footnote>One of the best known lists of heuristics is <citation url="http://www.useit.com/papers/heuristic /heuristic_list.html">Ten Usability Heuristics by Jacob Nielson</citation>. Another is <citation url="http://usability.gov /guidelines/index.html"> Research-Based Web Design and Usability Guidelines</citation> </footnote>
 </chapter> <chapter> <title>Cognitive Walk-Through</title>
Expert reviewers evaluate Web site understandability and ease of learning while performing specified tasks. They walk through the site answering questions such as "Would a user know by looking at the screen how to complete the first step of the task?" and "If the user completed the first step, would the user know what to do next?," with the goal of identifying any obstacles to completing the task and assessing whether the user would cognitively be aware that he was successful in completing a step in the process.
 </chapter> </part> ... </content> </book> <book number="2"> <metadata> ... </metadata> <content> <introduction>
This is a basic handbook for planning and conducting usability tests on Web sites. Usability testing should be used in conjunction with other expert review methods.

This book has not been approved by the Web Site Users Association.
 </introduction> <part number="1"> ... </part> <part number="2"> <chapter> <title>Conducting Usability Tests</title> ...
Give the user the script, then assure them that you are testing the Web site, not them. Users are asked to verbalize their thoughts as they complete the tasks. The event is recorded or someone takes notes. It is often preferable to have two testers, <footnote>Usability testing can be done at great expense or on a shoe string, using <testingProcedure>in-house expertise</testingProcedure> or <testingProcedure>contracting with human computer interaction professionals </testingProcedure>.</footnote> one to ask the questions, another to take notes. Testers should offer no guidance or comments to the user. Mouse movements, typing, expressions, and the user's words should be recorded.
 </chapter> <chapter> <title>Evaluating and Implementing Results</title>
Compile the results and review collectively. Make changes to the site to alleviate the problems found in Web site components which were propagating the largest number of or the most devastating errors. Begin new iterations of testing and changes, until users are successful in the accomplishing the tasks.
 </chapter> </part> </content> </book> <book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> <part number="1"><container type="box">1-12</container> <title>Subject File, <date normalize="1930/1974"> 1930-1974</date></title> ... <component><container type="box">1</container> <componentTitle>Computers</componentTitle> <subComponent> <componentTitle>Software, <componentDate normalize="1946/1947">1946-1947 </componentDate> </componentTitle> </subComponent> ... </component> <component> <componentTitle>Web User Appreciation Award, <componentDate normalize="1956">1956</componentDate> </componentTitle> </component> ... </part> </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "web" ftand "software" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "web" ftand "software"]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> <author>Elina Rose</author>
The usability of a Web site is how well the site supports the user in achieving specified goals. A Web site should facilitate learning, and enable efficient and effective task completion, while propagating few errors. Satisfaction with the site is also important. The user must not only be well-served, but must feel well-served.
 ...
This book has been approved by the Web Site Users Association.
 </introduction> <part number="1"> <title>Expert Reviews</title> <introduction>
Expert reviewers identify problems and recommend changes to web sites based on research in human computer interaction and their experience in the field.
 ...
Expert review methods should be initiated early in the development process, as soon as paper prototypes (hand-drawn pictures of Web pages) or wireframes (electronic mockups) are available. They should be conducted using the hardware and software similar to that employed by users.
 </introduction> <chapter> <title>Heuristic Evaluation</title>
Expert reviewers critique an interface to determine conformance with recognized usability principles. <footnote>One of the best known lists of heuristics is <citation url="http://www.useit.com/papers/heuristic /heuristic_list.html">Ten Usability Heuristics by Jacob Nielson</citation>. Another is <citation url="http://usability.gov /guidelines/index.html"> Research-Based Web Design and Usability Guidelines</citation> </footnote>
 </chapter> <chapter> <title>Cognitive Walk-Through</title>
Expert reviewers evaluate Web site understandability and ease of learning while performing specified tasks. They walk through the site answering questions such as "Would a user know by looking at the screen how to complete the first step of the task?" and "If the user completed the first step, would the user know what to do next?," with the goal of identifying any obstacles to completing the task and assessing whether the user would cognitively be aware that he was successful in completing a step in the process.
 </chapter> </part> ... </content> </book> <book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> <part number="1"><container type="box">1-12</container> <title>Subject File, <date normalize="1930/1974"> 1930-1974</date></title> ... <component><container type="box">1</container> <componentTitle>Computers</componentTitle> <subComponent> <componentTitle>Software, <componentDate normalize="1946/1947">1946-1947 </componentDate> </componentTitle> </subComponent> ... </component> <component> <componentTitle>Web User Appreciation Award, <componentDate normalize="1956">1956</componentDate> </componentTitle> </component> ... </part> </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "goal" ftand "obstacles" ftand "task" ordered return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "goal" ftand "obstacles" ftand "task" ordered]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="1"> <chapter>
Expert reviewers evaluate Web site understandability and ease of learning while performing specified tasks. They walk through the site answering questions such as "Would a user know by looking at the screen how to complete the first step of the task?" and "If the user completed the first step, would the user know what to do next?," with the goal of identifying any obstacles to completing the task and assessing whether the user would cognitively be aware that he was successful in completing a step in the process.
 </chapter> </part> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book where $book contains text ftnot "us.* testing" using wildcards return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[. contains text ftnot "us.* testing" using wildcards]
Expected Result: No results returned.
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, 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $up := $book/metadata where $up contains text "usability" ftand ftnot "plan" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[./metadata contains text "usability" ftand ftnot "plan"]
Expected Result:
<book number="1"> <metadata> <title shortTitle="Improving Web Site Usability">Improving the Usability of a Web Site Through Expert Reviews and Usability Testing</title> ... </metadata> <content> ... </content> </book> <book number="3"> <metadata> ... <subjects xml:lang="en"> ... <subject>Usability Testing</subject> ... </subjects> ... </metadata> <content> ... </content> </book>
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, with diacritics as written in
the query
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".
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text ("résumés" using diacritics sensitive ftor "drafts" ftor "correspondence") ftand ftnot "book drafts" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[./content contains text ("résumés" using diacritics sensitive ftor "drafts" ftor "correspondence") ftand ftnot "book drafts"]
Expected Result: No results returned.
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, with diacritics as written in
the query
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 automatically excluded. Instead the "book drafts" instances are not considered when determing whether or not to include books in the result set.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text ("résumés" using diacritics sensitive ftor "drafts" ftor "correspondence") not in "book drafts" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text ("résumés" using diacritics sensitive ftor "drafts" ftor "correspondence") not in "book drafts"]
Expected Result:
<book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $subj := $book/metadata/subjects/subject where $subj contains text "web site" ftand "usability" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[metadata/subjects/subject contains text "web site" ftand "usability"]
Expected Result:
<book number="1"> <metadata> ... <subjects xml:lang="en"> <subject>Usability testing</subject> <subject>Web site development</subject> <subject>Heuristic evaluation</subject> <subject>Cognitive walk-through</subject> <subject>Web site usability</subject> </subjects> ... </metadata> <content> ... </content> </book>
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 finds 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $subj := $book/metadata/subjects/subject where (some $s1 in $subj satisfies $s1 contains text "web site") and (some $s2 in $subj satisfies $s2 contains text "usability") return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[(some $s1 in ./metadata/subjects/subject satisfies $s1 contains text "web site") and (some $s2 in ./metadata/subjects/subject satisfies $s2 contains text "usability")]
Expected Result:
<book number="1"> <metadata> ... <subjects xml:lang="en"> <subject>Usability testing</subject> <subject>Web site development</subject> <subject>Heuristic evaluation</subject> <subject>Cognitive walk-through</subject> <subject>Web site usability</subject> </subjects> ... </metadata> <content> ... </content> </book> <book number="2"> <metadata> ... <subjects xml:lang="en"> <subject>Usability testing</subject> <subject>Web site development</subject> <subject>Guides and finding aids</subject> </subjects> ... </metadata> <content> ... </content> </book>
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").
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book where every $pub in $book//publisher satisfies $pub contains text "ersatz" ftand "publications" return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[every $pub in .//publisher satisfies $pub contains text "ersatz" ftand "publications"]
Expected Result:
<book number="1">
<metadata>
...
<publicationInfo>
<publisher>Ersatz Publications</publisher>
</publicationInfo>
...
</metadata>
<content>
...
</content>
</book>
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".
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "expert review methods" occurs at least 2 times return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "expert review methods" occurs at least 2 times]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="1"> <title>Expert Reviews</title> <introduction> ...
Two expert review methods are discussed here. They are heuristic evaluation and cognitive walk-through.

Expert review methods should be initiated early in the development process, as soon as paper prototypes (hand-drawn pictures of Web pages) or wireframes (electronic mockups) are available. They should be conducted using the hardware and software similar to that employed by users.
 </introduction> ... </part> </content> </book>
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 finds "developer of software", which occurs in the sample data.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "software" ftand "developer" using stemming distance at most 3 words return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "software" ftand "developer" using stemming distance at most 3 words]
Expected Result:
<book number="3"> <metadata> ... </metadata> <content> <introduction>
The papers of John Wesley Usabilityguy span the years 1946-2001, with the bulk of the items concentrated in the period from 1985 to 2001. The papers feature his career as a developer of software applications and usability specialist. The collection consists of correspondence, memoranda, journals, speeches, article drafts, book drafts, notes, charts, graphs, family papers, clippings, printed matter, photographs, résumés and other materials.
 </introduction> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "efficient" ftand "task" ftand "completion" ordered distance at most 10 words return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "efficient" ftand "task" ftand "completion" ordered distance at most 10 words]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <content> <introduction> ...
The usability of a Web site is how well the site supports the user in achieving specified goals. A Web site should facilitate learning, and enable efficient and effective task completion, while propagating few errors. Satisfaction with the site is also important. The user must not only be well-served, but must feel well-served.
 ... </introduction> ... </content> </book>
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 because of the ordered
operator 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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text ("users" ftand "feeling") using stemming ftand "well served" ftor "well-served" ordered window 15 words return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text ("users" ftand "feeling") using stemming ftand "well served" ftor "well-served" ordered window 15 words]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <introduction> ...
The usability of a Web site is how well the site supports the user in achieving specified goals. A Web site should facilitate learning, and enable efficient and effective task completion, while propagating few errors. Satisfaction with the site is also important. The user must not only be well-served, but must feel well-served.
 ... </introduction> ... </content> </book>
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.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text ("users" ftand "would" ftand "know" ftand "step" same sentence) using stemming return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text ("users" ftand "would" ftand "know" ftand "step" same sentence) using stemming]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> ... <part number="1"> <chapter>
Expert reviewers evaluate Web site understandability and ease of learning while performing specified tasks. They walk through the site answering questions such as "Would a user know by looking at the screen how to complete the first step of the task?" and "If the user completed the first step, would the user know what to do next?," with the goal of identifying any obstacles to completing the task and assessing whether the user would cognitively be aware that he was successful in completing a step in the process.
 </chapter> </part> ... </content> </book>
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. Depending on the
implementation, this query might return no result instead of the
Expected Result presented.
Solution in XQuery:
for $book in doc("http://bstore1.example.com/full-text.xml") /books/book let $cont := $book/content where $cont contains text "usability" ftand "web site" ftand "efficiency" ftand "satisfaction" same paragraph return $book
Solution in XPath:
doc("http://bstore1.example.com/full-text.xml") /books/book[content contains text "usability" ftand "web site" ftand "efficiency" ftand "satisfaction" same paragraph]
Expected Result:
<book number="1"> <metadata> ... </metadata> <content> <content> <introduction> ...
The usability of a Web site is how well the site supports the user in achieving specified goals. A Web site should facilitate learning, and enable efficient and effective task completion, while propagating few errors. Satisfaction with the site is also important.. The user must not only be well-served, but must feel well-served.
 ... </introduction> ... </content> </book>
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