Skip to main content
SimilarExport ZIP
100%

Query for long and short phrases in Shakespeare's plays

✓ Published0🌍 Public
CCliffordAnderson
Last edited Dec 22, 2013
Created on Dec 22, 2013

This visualization shows the distribution of long versus short phrases in Shakespeare’s plays, counting how many phrases exceed twenty characters. A bar-like layout compares the two categories, making the frequency difference immediately visible. The code uses XQuery 3.0 with the `fn:collection` and `tei:ab` functions to access and iterate over TEI-annotated text blocks, applying `fn:string-length` to classify each phrase. It groups results by length category using the `group by` clause, then dynamically constructs an element named `long-phrase` or `short-phrase` with the corresponding count, rendering the final output as XML.

AI-generated description

Similar vizzes

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
63% match
Loading thumbnail…

Produces word frequency list for speakers in Much Ado about Nothing.

This example uses XQuery 3.0 with the TEI namespace to generate a per-speaker word frequency list from Shakespeare’s *Much Ado about Nothing*. It processes the TEI-encoded XML document, iterating over distinct speakers and counting each word’s occurrences within their spoken lines, then outputs a sequence of `<word>` elements with the speaker, type, count, and weighted frequency. The query relies on `fn:distinct-values`, `fn:count`, and an `order by` clause to rank terms.

CCliffordAnderson
61% 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
61% match
Loading thumbnail…

Query across collections in ExistDB

This example shows how a single XQuery query can aggregate and expose metadata from multiple Shakespearean text collections stored in an eXist-db database. The query uses the `fn:collection()` function to traverse the `db/shakespeare` path, selecting all `tei:seriesStmt` elements from the TEI namespace, which describe series-level publication information. The visualization renders the resulting XML as a structured graph, with nodes and edges built from the query output using D3.js’s `d3.forceSimulation` for layout. The concrete approach relies on eXist-db’s native XQuery engine to fetch and return the TEI data, which is then parsed and bound to visual elements, demonstrating a direct pipeline from database query to interactive graphic.

CCliffordAnderson
60% match
Loading thumbnail…

Named Entity Recognition on Folger's XML Edition of *A Winter's Tale*

This visualization maps the named entities in a TEI-encoded XML edition of Shakespeare’s *A Winter’s Tale* by classifying each line of dialogue with the Stanford NER library’s `english.muc.7class.distsim.crf` classifier. It shows how the text’s person, location, and organization labels distribute across acts and scenes, highlighting character mentions as the play progresses. Written in XQuery 3.0, the code extracts line text from `//tei:ab` nodes, joining `tei:w`, `tei:pc`, and `tei:lb` elements into a single string, then calls `ner:classify-string` per line. The output feeds a visualization that preserves the original line breaks, revealing which characters dominate each segment of the play.

CCliffordAnderson
60% 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…

A list of all the paths in the Folger XML edition of *Much Ado About Nothing*

This visualization displays every unique XML element path in the Folger Shakespeare Library’s TEI edition of *Much Ado About Nothing*, showing the document’s structural hierarchy as a collapsible tree. It reveals how the play’s text is organized, from the TEI header’s metadata (like editorial declarations and source descriptions) down to nested speech and stage-direction elements. The code uses D3’s `d3.forceSimulation` to layout the nodes and `d3.hierarchy` to compute parent-child relationships from the path list. The data originates from a gist containing `paths.txt`, which is parsed into a tree structure for rendering.

CCliffordAnderson
56% match
Loading thumbnail…

This is my example code from our classroom exercise

This example visualizes stage directions from a TEI-encoded text by associating each person with the stages they appear in. The XQuery code iterates through `//person` elements and collects matching `//stage` elements based on the `@who` attribute, outputting a structured XML list of directions per character. It relies on the TEI namespace and uses `fn:tokenize` to parse multiple ID references. The result is a plain XML document, not a graphical rendering, serving as a preprocessing step for potential downstream visualization.

CCliffordAnderson
56% match