A list of all the TEI element leaves in the Folger Shakespeare edition of *Much Ado about Nothing*

100%

A list of all the TEI element leaves in the Folger Shakespeare edition of Much Ado about Nothing

✓ Published0🌍 Public

Last edited Dec 29, 2013

Created on Dec 29, 2013

This visualization lists all TEI element leaves found in the Folger Shakespeare edition of *Much Ado about Nothing*, showing the raw hierarchical vocabulary of the text’s markup. It displays each unique leaf tag—such as `<w>`, `<pb>`, and `<stage>`—in a simple ordered list, making the document’s structural diversity immediately visible. The page is built with plain HTML and CSS, relying on the browser’s native DOM parsing to render the static list from the precomputed data. No JavaScript libraries or dynamic rendering are used; the source data comes from a gist authored by CliffordAnderson, presenting the tags exactly as extracted from the TEI-encoded play.

AI-generated description

Similar vizzes

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

80% 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

64% 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

64% match

Loading thumbnail…

For Arne

This example visualizes the structure of a single TEI-encoded article by extracting metadata from an XML source and rendering it as a document-tree diagram. It shows the hierarchical relationships between the article’s title, author, issue, and page-range fields, emphasizing how the original bibliographic data maps onto the TEI structure. The visualization uses an XQuery script with XPath queries to pull specific values, such as the issue and article numbers via regular-expression replacement, and the starting/ending pages from the `biblScope`. The rendering then relies on a force-directed layout (via `d3.forceSimulation`) to position nodes, with each node representing a TEI element and links showing parent–child dependencies. The data source is the gist’s embedded TEI file, and the output is a static SVG generated client-side, reflecting the parsed metadata without additional interaction.

CCliffordAnderson

64% match

Loading thumbnail…

Render module for search namespace

This example shows how TEI-encoded play texts can be rendered into a formatted HTML view, using the `render:render` and `render:recurse` functions to map XML elements like `tei:head`, `tei:speaker`, and `tei:stage` to headings, bold labels, and paragraphs. It relies on XQuery’s `typeswitch` and recursion to process the document tree, while the `render:titles` function generates a hyperlinked table of contents from a list of play elements. The code directly uses the XQuery 3.0 module system and the `declare function` syntax, with no external JavaScript libraries.

CCliffordAnderson

63% 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

61% 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

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

60% match