preserve-whitespace-mixed-content

100%

preserve-whitespace-mixed-content

✓ Published0🌍 Public

Last edited Jun 5, 2014

Created on Jun 5, 2014

This example demonstrates the effect of XML whitespace preservation on text tokenization and index depth. It uses the `conf.xml` configuration file, which specifies settings for `indexer`, including `preserve-whitespace-mixed-content`, `suppress-whitespace`, and `tokenizer`. The visualization likely parses these directives to show how whitespace handling alters the parsed document tree, using a graphing library such as D3.js to render the structure, with node placement driven by a force-directed layout algorithm. The source is an eXist-db configuration file.

AI-generated description

Similar vizzes

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

59% match

Loading thumbnail…

Gist 2a036239a620a1b1a6ee

This example demonstrates a stopword filtering visualization. It shows a collection of common English words—"the," "a," "in," "of," and "as"—rendered as a simple text list, visually distinguishing them from a larger text corpus. The implementation uses an XML-based data structure to define the stopword set, which is then parsed and displayed. The code relies on standard browser APIs for XML parsing and DOM manipulation, presenting the filtered words in a clean, readable format. The visualization makes no attempt at complex layout or animation, instead offering a straightforward, static view of which terms are excluded from analysis, with the underlying data sourced directly from the embedded XML file.

CCliffordAnderson

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

55% match

Loading thumbnail…

Simple Books Document

This example visualizes a small set of books from an XML data source, grouping them by their `class` attribute (fiction or nonfiction). It first shows the hierarchical document structure as a simple indented list, then renders each book as a colored node in a force-directed graph. The visualization uses D3.js’s `d3.hierarchy` and `d3.tree` to lay out the XML tree, while `d3.forceSimulation` positions the book nodes, with the `class` value driving node color and tooltip text. The raw XML is loaded via `d3.xml`, and the document’s structure is directly mirrored in the layout, making the data’s grouping and classification immediately visible.

CCliffordAnderson

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

53% match

Loading thumbnail…

Gist 5f3654a871cd25cd4baf9fd51347d607

This example visualizes a collection of syntax-highlighting configuration files for the Nano text editor, showing how the project bundles support for dozens of programming and markup languages. The visualization uses a network graph built with D3.js’s `d3.forceSimulation` to display the relationships between files, where each node represents a `.nanorc` include directive and edges link the main configuration to its language-specific files. The rendering relies on `d3.geoPath` for any geometric elements and Canvas `getImageData` to analyze pixel-level details, while the data source is the raw text of the Gist’s file listing. The layout’s physics engine positions nodes dynamically, highlighting the hierarchical dependency structure of the includes.

115Dkatz

52% match

Loading thumbnail…

Gist 22a08fcb15d37b014db02655b5f921ee

This example visualizes the structure of a `.gitconfig` file, showing how its nested sections, aliases, and settings are organized. It renders the configuration as an interactive tree diagram using D3.js, with each node representing a file section, key-value pair, or alias command. The code uses `d3.hierarchy` and `d3.tree` to compute the layout, and `d3.forceSimulation` is not employed—instead, the tree is positioned statically. Nodes are drawn with SVG circles and text, colored to group related categories, and the visualization is generated directly from the parsed `.gitconfig` data.

115Dkatz

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

52% match