fn:analyze-string results

100%

fn:analyze-string results

✓ Published0🌍 Public

Last edited Nov 16, 2015

Created on Nov 16, 2015

This example demonstrates the results of an XQuery transformation that uses the XPath 3.1 `fn:analyze-string` function to parse bibliographic text. Given a TEI XML source, the query extracts page ranges from bibliographic entries by matching patterns like "p. 35-42" and wraps them in a `tei:citedRange` element, while preserving the remaining text. The output shows a series of TEI `<bibl>` records where the cited page ranges are cleanly separated from the bibliographic citation text, enabling structured access to page references for downstream processing or display.

AI-generated description

Similar vizzes

Loading thumbnail…

XQuery Full Text

This example demonstrates the evolution of text search in XQuery, from basic string matching to full-text querying with linguistic processing. It shows how `fn:contains` and `fn:matches` perform literal pattern matching, while the XQuery Full Text 3.1 features—`contains text`, `using stemming`, `ft:mark`, and the `score` clause—enable case-insensitive, stem-aware, ranked search results. The code queries a collection of TEI-encoded texts (`vwwp_tei`) and returns matched paragraphs, with scoring wrapped in XML output and string formatting via `format-number`.

CCliffordAnderson

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

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

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

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

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

61% match

Loading thumbnail…

Gist ccc08dae693660d7aa1b8cf2708fd13d

This example demonstrates how to query and highlight text passages in the Victorian Women Writers Project TEI corpus using XQuery 3.1. It shows a progression from simple full-text searches for repeated terms to fuzzy matching via `ft:search` and `ft:extract`, and finally visualizes results by marking hits with `ft:mark` and segmenting them into tumbling windows. The code relies on BaseX’s full-text and windowing capabilities to extract and structure paragraph-level matches containing “garden” or “house.”

CCliffordAnderson

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

60% match