Skip to main content
SimilarExport ZIP
100%

XQuery Puzzles from Week 1, Day 5, Session 4 of the Advanced Digital Editions NEH Institute at the University of Pittsburgh

✓ Published0🌍 Public
CCliffordAnderson
Last edited Jul 17, 2022
Created on Jul 15, 2022

This gallery example presents a set of XQuery 3.1 puzzle solutions designed to transform data formats. One function converts a textual date like "July 15, 2022" into an `xs:date` value by tokenizing the string and using a `switch` expression to map month names to numbers, while another script processes a sequence of dates with a `for` loop. A third function converts Roman numerals to integers, using `string-to-codepoints` and `codepoints-to-string` to iterate over characters and applying a conditional sum to handle subtractive notation. The code does not use any visualization libraries; the source is a gist by CliffordAnderson.

AI-generated description

Similar vizzes

Loading thumbnail…

Xquery for Unit Dates

This example demonstrates a preprocessing step for visualizing dates in archival finding aids, extracting four-digit years from `<unitdate>` elements in a single EAD XML document. The XQuery script uses the XQuery 3.0 `copy` and `modify` expressions to insert a `normal` attribute containing the extracted year onto each unitdate node. It leverages a namespace declaration for the EAD standard and the `fn:doc` and `fn:replace` functions to fetch the remote XML file from GitHub and parse the date text via regular expressions. The output is the modified XML nodes, ready for downstream temporal analysis or charting.

CCliffordAnderson
68% match
Loading thumbnail…

Sample switch expression for Topics in Digital Humanities

This example demonstrates a simple XQuery switch expression that maps numeric day values (1 through 7) to weekday names, with a fallback for invalid inputs. The code iterates over a hardcoded sequence of integers using a `for` loop, and for each value, the `switch` statement evaluates the matching `case` to return the corresponding string literal. No external visualization libraries are involved; the logic is purely functional, relying on XQuery's built-in control flow. The data source is the literal range `(1 to 7)`, and the output is a sequence of day names, illustrating pattern matching in a query language context.

CCliffordAnderson
67% match
Loading thumbnail…

Playing with Higher Order Functions in XQuery

This example demonstrates how higher-order functions in XQuery 3.1 enable function composition for transforming numeric sequences. It shows a square function (`$map-sqr`) that uses the simple map operator (`!`) with `math:pow`, which is then fed into a reversal function (`$pow-rev`) via the `=>` arrow operator. The code applies `fn:reverse` to the input sequence before passing it to the squared map, returning the squares of the reversed order. The rendered output is computed in-memory with no external data source, purely exercising the language’s functional capabilities.

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

Simple examples of higher-order functions and partial function application in XQuery

This example demonstrates higher-order functions and partial application in XQuery 3.0, using code tested with Saxon and Zorba. It shows functions that accept or return other functions, such as `local:pow` returning a function, and the `math:pow#2` built-in being partially applied with `?`. The code also illustrates fold operations (`fold-left`, `fold-right`) and sequence functions (`for-each`, `for-each-pair`, `filter`), applied to string and integer sequences. These snippets highlight how XQuery 3.0 supports functional programming patterns.

CCliffordAnderson
60% match
Loading thumbnail…

XQuery Blue Mountain Project - Part III

This example shows a pipeline for transforming a single TEI XML document from the Blue Mountain Project—a digitized 1920 issue of the French journal *Action*—into clean, article-level TEI files. The first script removes facsimile elements, end-hyphenation markers, and line breaks, replacing `<lb>` elements with spaces. A second script extracts metadata and article content into a fresh TEI template, while a third builds individual TEI files for each article. The code uses XQuery 3.1 with the `fn:doc` API for document access and node operations like `copy`, `modify`, and `replace node`.

CCliffordAnderson
60% match
Loading thumbnail…

XQuery Working Group Challenge

This example transforms the PROIEL treebank’s Latin New Testament XML into a sequence of verse elements, each tagged with its citation and concatenated token forms. It fetches the remote XML via `fn:doc`, extracts distinct citation parts, and filters tokens by matching `@citation-part` to build structured verses. The code uses XQuery 3.1’s element constructors and `fn:data` to output text, demonstrating a direct pipeline from hierarchical treebank data to flat verse-like text.

CCliffordAnderson
59% match
Loading thumbnail…

For Zach Johnson

This example transforms a raw XML extract of the Jesse Wills finding aid into structured archival units using XQuery 3.1. The code loads a source document from a GitHub gist, then uses a tumbling window to pair adjacent XML elements into `c02` records. It tokensizes `unittitle` text by semicolons and periods, classifies segments as folder containers or dates, and constructs `did` elements with normalized `unitdate` and `unittitle` values. The result is a cleaned, hierarchical data structure suitable for downstream visualization, though no rendering library is invoked here.

CCliffordAnderson
59% match