Skip to main content
SimilarExport ZIP
100%

This is my example code from our classroom exercise

✓ Published0🌍 Public
CCliffordAnderson
Last edited Jun 13, 2014
Created on Jun 12, 2014

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.

AI-generated description

Similar vizzes

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

Here's the query we started in class today.

This example demonstrates how to extract the title and author from a TEI-encoded XML document stored in a database. It shows the direct retrieval of text content from nested XML elements, returning both pieces of metadata as a sequence. The code uses the XQuery language with the `fn:doc()` function to access the document and XPath expressions to navigate the TEI namespace. It specifically traverses the `teiHeader/fileDesc/titleStmt` structure to pull the title and author values, illustrating a fundamental pattern for querying structured text documents in an XML database environment.

CCliffordAnderson
67% match
Loading thumbnail…

<title>Testing XPath

This example demonstrates how an XML TEI document’s structure can be queried using XPath and represented as an interactive node-link diagram. It displays the document’s hierarchical elements—such as `teiHeader`, `text`, `body`, and `p`—as circles connected by links, with text content visible alongside node labels. The visualization uses D3.js’s `d3.hierarchy` and `d3.tree` layout to calculate positions, while `d3.zoom` enables panning and zooming. The code loads the XML via a local file and parses it with `DOMParser`, then applies XPath expressions via `document.evaluate` to extract elements and text for rendering.

CCliffordAnderson
67% 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
66% 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
66% 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…

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