Combining Node Sequences

100%

Combining Node Sequences

✓ Published0🌍 Public

Last edited Apr 29, 2016

Created on Apr 29, 2016

Two XQuery scripts demonstrate sequence operations on XML nodes. The first script, `except.xqy`, constructs a `<stopwords>` element from a word list and removes the fourth word using the `except` operator, returning a filtered sequence. The second, `operators.xqy`, defines three sequences of `<name>` elements and applies `except` to compare them, isolating differences between node sequences. Both rely on XQuery 3.1’s sequence operators (`except`, union, intersect) to combine and subtract node sets. The examples highlight how node identity and order determine sequence subtraction, with output shown as XML fragments without external libraries.

AI-generated description

Similar vizzes

Loading thumbnail…

Making comparisons in XQuery

XQuery’s comparison operators are demonstrated through paired queries that contrast general comparisons with existential quantifiers. The code uses the XQuery `some`/`every` expressions and `satisfies` clauses to test set membership, while `=` and `eq` show value-based versus sequence-based equality. The examples, sourced from a gist, handle XML data with `isbn` attributes and use `where` clauses with `@num` comparisons. A node identity check via the `is` operator highlights how XQuery distinguishes node identity from value equality, all rendered in concise .xqy files.

CCliffordAnderson

65% match

Loading thumbnail…

XQuery Working Group - February 9, 2018

This example demonstrates two XQuery approaches for transforming CSV contact data into XML records, highlighting the difference between excluding a field by name and by structural exception. The first script, `data-munging-with-except.xqy`, uses the arrow operator and `csv:parse` from the XQuery standard library to parse the CSV, then constructs new XML records with `/record/(* except _)` to drop the underscore field. The second script, `data-munging.xqy`, achieves the same result using `$record/*[not(name()='_')]` and additionally persists each record to a database via `db:replace`. Both iterate through parsed records with a `for` loop and assign filenames through the `@name` attribute.

CCliffordAnderson

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

<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

58% match

Loading thumbnail…

Produces word frequences for any given sequence of text nodes

This visualization shows word frequencies extracted from a sequence of text nodes, displaying each unique word with its frequency count. The XQuery code collects text from the TEI-encoded source document, normalizes tokens by removing punctuation and lowercasing, then counts occurrences of each distinct word. It returns an ordered dictionary element with word-frequency pairs sorted in descending order. The example uses the XQuery 3.0 specification, including functions like `fn:tokenize`, `fn:distinct-values`, and `fn:count`, to process the remote XML data.

CCliffordAnderson

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

56% match

Loading thumbnail…

Problem 6 of 99 Problems (adapted from https://johncrane.gitbooks.io/ninety-nine-elm-problems/content/p/p06.html)

This example demonstrates a unit test suite for a palindrome-checking function written in XQuery, using the BaseX XQUnit testing framework. It shows how `fn:deep-equal` and `fn:reverse` from the XQuery 3.1 standard library verify that sequences of items (including numbers and strings) read identically forward and backward. The test cases, defined with `%unit:test` annotations and `unit:assert-equals`, cover positive and negative cases, single-item and empty sequences, and string-element palindromes. The code is organized as a module with a namespace and imported test module, reflecting a modular approach to test-driven development.

CCliffordAnderson

56% match

Loading thumbnail…

Existential Quantification in XQuery

Two XQuery expressions demonstrate existential and universal quantification over a list of author names. The first uses `every ... satisfies` to test whether all names lack a period, while the second uses `some ... satisfies` to check if at least one contains a period. Both queries evaluate against four string literals, showing how XQuery’s quantified expressions return boolean results. The embedded visual likely contrasts the two outcomes with a simple layout, though no charting library appears in the code snippets.

CCliffordAnderson

56% match