Skip to main content
SimilarExport ZIP
100%

Looking up words in the OED with XQuery

✓ Published0🌍 Public
CCliffordAnderson
Last edited Jan 13, 2017
Created on Jan 13, 2017

This example demonstrates a playful text-rewriting process where each word in a sentence is replaced by a synonym retrieved from the Oxford Dictionaries API. It begins by sending two HTTP requests to the Oxford Dictionaries API endpoints for word definitions and synonyms, then defines a custom XQuery function that isolates the first synonym for a given word. The main logic tokenizes the input sentence and applies this synonym-lookup function iteratively, finally rejoining the substituted words into a new sentence. The visualization relies on XQuery’s HTTP client capabilities for API interaction and string manipulation functions to process the text, with no graphical rendering involved.

AI-generated description

Similar vizzes

Loading thumbnail…

A little playful XQuery

This playful XQuery example transforms a user’s phrase by replacing each word with a random antonym fetched from the Oxford Dictionaries API. It demonstrates a game-like text manipulation, showing the original sentiment inverted. The code uses XQuery 3.1, the `http:send-request` and `random:integer` functions, and the MarkLogic HTTP client to query the Oxford entry endpoint. For each word, it retrieves antonym sets, picks one randomly, and falls back to the original word when no antonym exists.

CCliffordAnderson
75% match
Loading thumbnail…

Oxford Dictionary API, Part III

This example demonstrates how to query the Oxford Dictionary API using XQuery, first retrieving definitions for a specified word and then fetching a list of rare art-related terms. The code uses the `http:send-request` function with custom `http:request` and `http:header` elements to authenticate and call the API endpoints. It relies on XQuery 3.1 features, including local functions and the `fn:data()` function to extract definition text, numbering each result sequentially. The data source is the live Oxford Dictionaries API, accessed via its REST endpoints.

CCliffordAnderson
74% match
Loading thumbnail…

For XQuery4Humanists

This example visualizes the frequency and distribution of words extracted from a TEI-encoded poem, processing the text to remove punctuation, normalize case, and tokenize it into a list. The visualization shows the resulting word list as a simple textual display, highlighting the raw output of the XQuery processing pipeline. The code uses XQuery 3.0 functions like `fn:tokenize`, `fn:lower-case`, and `fn:replace` to clean the data, pulling the source directly from a remote XML file hosted on GitHub. The rendering relies solely on the XQuery return, with no additional JavaScript or charting libraries involved.

CCliffordAnderson
65% match
Loading thumbnail…

Code snippets for XQuery Working Group (Text Mining at Scale)

This example demonstrates a text-mining workflow for querying the Victorian Women Writers Project corpus stored in a BaseX database, using XQuery and XPath Full Text 1.0. It walks through creating structured records from TEI XML, saving them to a new database, and running full-text searches with scoring, stemming, and thesaurus-based matching. The code exercises functions like `db:replace`, `ft:mark`, and `ft:extract` to highlight matching text, while also showing stop-word filtering and boolean operators for queries.

CCliffordAnderson
61% match
Loading thumbnail…

A simple Shakespeare search tool in eXist-db

This example shows a simple full-text search interface for Shakespeare’s plays, returning matching lines from a TEI-encoded corpus. The page uses an XQuery script that queries an eXist-db database via the `ft:query` function, which performs full-text search on `<tei:l>` elements. A plain HTML form submits a query parameter, and the results are rendered as `<p>` elements. The code relies on eXist-db’s request and collection APIs, along with the `output` serialization options for HTML5, but does not use any client-side JavaScript libraries or advanced rendering techniques.

CCliffordAnderson
59% match
Loading thumbnail…

Produces word frequences for any given sequence of text nodes

This visualization shows word frequencies extracted from a sequence of text nodes, displaying each unique word with its frequency count. The XQuery code collects text from the TEI-encoded source document, normalizes tokens by removing punctuation and lowercasing, then counts occurrences of each distinct word. It returns an ordered dictionary element with word-frequency pairs sorted in descending order. The example uses the XQuery 3.0 specification, including functions like `fn:tokenize`, `fn:distinct-values`, and `fn:count`, to process the remote XML data.

CCliffordAnderson
59% match
Loading thumbnail…

This example of recursive descent in XQuery is adapted from Joe Wicentowski (https://gist.github.com/joewiz/2331558#file-typeswitch-skeleton-xq). It rather naively formats scenes from the Folger Library Shakespeare TEI editions for display in HTML. This example is intended for the demonstration of the concept, not actual use.

This example shows recursive descent in XQuery rendering scenes from a Folger Library Shakespeare TEI edition into HTML. It demonstrates how a typeswitch pattern matches distinct TEI elements—such as `tei:head`, `tei:w`, `tei:stage`, and `tei:speaker`—to produce formatted output like headings, stage directions, and speaker labels. The code relies on XQuery 3.0’s built-in `typeswitch` and function recursion, using `local:render` and `local:recurse` to traverse the XML tree. It serializes to XHTML via `exist:serialize`, pulling the source document from `/db/shakespeare/JC.xml` without external libraries.

CCliffordAnderson
58% match
Loading thumbnail…

{$title}

This example demonstrates a minimal XQuery web application for the Corpus Baudelaire project, serving static XHTML pages and dynamic poem routes. It shows how RESTXQ annotations declare endpoints for the root path, an about page, a credits page, and a parameterized poem URL, with each route returning a simple HTML document via a shared display function. The code relies on the RESTXQ API for request routing and the XQuery standard library for string concatenation and element construction, though it renders no actual data visualization.

CCliffordAnderson
58% match