xquery4 2.0.0

dotnet tool install --global xquery4 --version 2.0.0
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local xquery4 --version 2.0.0
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=xquery4&version=2.0.0
                    
nuke :add-package xquery4 --version 2.0.0
                    

xquery

Command-line XQuery 3.1/4.0 processor for .NET. Query XML documents from the terminal using the PhoenixmlDb XQuery engine.

Installation

dotnet tool install -g xquery4

Usage

# Query an XML file
xquery '//book/title' library.xml

# Count elements
xquery 'count(//item)' catalog.xml

# Read from a query file
xquery -f transform.xq input.xml

# Query a directory of XML files
xquery 'collection()//product[price > 50]' ./data/

# JSON output
xquery -o json 'map { "count": count(//item) }' data.xml

# Read from stdin
cat data.xml | xquery '//item/@name'

# Show execution plan
xquery --plan 'for $x in 1 to 10 return $x * $x'

# Show timing breakdown
xquery --timing '//item' large-catalog.xml

Features

  • XQuery 3.1/4.0 — FLWOR, maps/arrays, higher-order functions, string constructors
  • Multiple output methods — adaptive, XML, text, JSON
  • Context item — input XML is available as . (standard XQuery)
  • Multiple sources — files, directories, URLs, stdin
  • Full prolog support — namespaces, variable/function declarations, serialization options
  • Execution plans — inspect how queries are compiled and optimized
  • Timing — built-in performance profiling

Documentation

Full documentation at phoenixml.dev

License

Apache-2.0

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
2.0.0 0 9/15/2026
1.8.0 57 9/14/2026
1.7.0 66 9/11/2026
1.6.15 64 9/9/2026
1.6.14 84 9/7/2026
1.6.13 71 9/4/2026
1.6.12 67 9/1/2026
1.6.11 79 8/29/2026
1.6.10 79 8/29/2026
1.6.9 73 8/27/2026
1.6.8 71 8/26/2026
1.6.7 78 8/24/2026
1.6.6 78 8/23/2026
1.6.5 81 8/21/2026
1.6.2 89 8/16/2026
1.6.1 85 7/31/2026
1.6.0 90 7/27/2026
1.5.5 99 7/12/2026
1.5.4 88 7/9/2026
1.5.3 90 7/8/2026
Loading failed

**Major because existing queries stop compiling.** Part of the coordinated
namespace-consolidation train: `PhoenixmlDb.Core`, `PhoenixmlDb.XQuery` and `PhoenixmlDb.Xslt`
all move to 2.0.0 together. Takes **PhoenixmlDb.Core 2.0.0**.

### Breaking — read this before upgrading

**1. The extension functions have moved to `phx`, and the old names no longer compile.**

`ft:*` and `dbxml:metadata` are gone. There are no aliases — this is a clean break, so a query
using the old names fails at compile time rather than behaving differently.

| was | now |
|---|---|
| `dbxml:metadata` | `phx:metadata` |
| `ft:stem` | `phx:stem` |
| `ft:tokenize` | `phx:tokenize` |
| `ft:score` | `phx:score` |
| `ft:is-stop-word` | `phx:is-stop-word` |
| `ft:thesaurus-lookup` | `phx:thesaurus-lookup` |

`phx` is **predeclared** — bound to `https://schemas.phoenixml.dev/2026/functions` — so no prolog
declaration is needed. The old `http://www.w3.org/2007/xpath-full-text` namespace is retired, and
with it the misleading suggestion that these were standard functions. They never were: the W3C
Full Text specification defines the `contains text` clause and no callable functions in that
namespace.

**2. A host can no longer bind `phx` to another URI.** Passing a different `phx` binding through
`CompilationOptions.StaticNamespaces` is now a compile error. If your documents use `phx` as
their own prefix, declare it in the query prolog, exactly as you would for `math:`.

**3. `IMetadataProvider` never receives a prefixed key.** Keys arrive as `local` or
`Q{uri}local`. The system key `dbxml:size` now arrives as
`Q{https://schemas.phoenixml.dev/2026/meta}size`. Custom providers matching on the literal
`dbxml:` prefix must be updated.

### Added

- **Prolog-declared prefixes now work in metadata keys.** A key written `p:local` resolves `p`
 through the query's own `declare namespace`, not only the container's bindings.

### Fixed

- **In-scope namespaces survive copies and serialization.** A copied element kept the namespaces
 it needed to serialize correctly, and `fn:in-scope-namespaces` now comes from the same walk
 rather than a second implementation that could disagree.
- **Serialization parameters are read properly**: every parameter the serializer supports,
 `output:item-separator` from the prolog, and a parameter-document through the same path.
- **An unresolvable namespace id fails loudly when serializing** instead of producing output with
 a wrong or empty namespace.
- **An XML declaration is written for a bare element** when one is requested.

### Conformance

W3C QT3 **29,813**.