<title>Testing XPath

100%

<title>Testing XPath

✓ Published0🌍 Public

Last edited Feb 6, 2014

Created on Jan 28, 2014

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.

AI-generated description

Similar vizzes

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

82% match

Loading thumbnail…

XPath Examples - Mellon Institute

This example demonstrates how XPath queries navigate and extract specific content from a TEI-encoded document of the Mellon Institute at Vanderbilt. It shows the progression from simple absolute paths to descendant-or-self axes, then to predicate-based filtering, and finally to more complex relational paths. The code uses the XPath API to select titles, names, sex attributes, and speaker-related paragraphs, referencing the updated TEI Guidelines for the sex element. The example is presented as a gist authored by CliffordAnderson, with the source data being the structured XML markup of the institute’s records, illustrating query patterns for text extraction and attribute matching.

CCliffordAnderson

75% match

Loading thumbnail…

Practice XPath expressions for USC

This example demonstrates XPath expression practice through a visual interface, showing how distinct values and hierarchical navigation can be explored interactively. It uses the USC document structure to highlight element names and path syntax, including `self::element()` for text-bearing nodes and child-axis selectors like `/child::usc:uscDoc/child::usc:main`. The visualization is driven by a gist from CliffordAnderson, with the code relying on XQuery (implied via the `.xqy` file) to compute distinct names and parent-child relationships. The rendering approach is not explicitly shown, but the focus remains on illustrating XPath’s filtering and traversal capabilities against a sample XML document.

CCliffordAnderson

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

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

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

68% match

Loading thumbnail…

Force-Directed Layout from XML

This example visualizes a hierarchical XML document as a force-directed network, where each XML element becomes a draggable circle and parent-child relationships appear as links. The circle size reflects the numeric text content of each element, scaled using `d3.scaleSqrt`. The code uses `d3.forceSimulation` with link, charge, and centering forces, and loads the XML via `d3.xml`. It parses the document with native DOM queries, then renders the network as SVG with interactive dragging enabled through `d3.drag`.

Mmbostock

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

67% match