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.

100%

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.

✓ Published0🌍 Public

Last edited Jan 2, 2014

Created on Jan 2, 2014

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.

AI-generated description

Similar vizzes

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

74% match

Loading thumbnail…

<title>Testing XPath

This example demonstrates how XPath and the XQuery `typeswitch` expression can be used to selectively process different node types in an XML document. It shows a TEI-encoded text where comments, text nodes, and `<p>` elements are handled distinctly, with element attributes joined into a space-separated string. The code relies on the XQuery 3.0 standard library functions `fn:string` and `fn:string-join`, operating on the TEI namespace declared in the document. The visualization is static, with no graphical rendering; instead, it highlights the programmatic traversal and conditional branching over the XML tree structure.

CCliffordAnderson

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

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

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

65% match

Loading thumbnail…

{$title || " - "}

This example displays a list of EAD (Encoded Archival Description) titles sorted alphabetically from a collection of finalized XML files, rendered as plain paragraph elements in an XHTML page. It uses XQuery 3.1 with the `fn:collection` function to gather titles from `titleproper[@type="filing"]` nodes, and a local template function `local:template` constructs the HTML output, setting a dynamic heading level and tab title. The code demonstrates a server-side, XML-to-HTML transformation pipeline without client-side JavaScript libraries or interactive visualization components.

CCliffordAnderson

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

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