xslt 1.6.11

There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global xslt --version 1.6.11
                    
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 xslt --version 1.6.11
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=xslt&version=1.6.11
                    
nuke :add-package xslt --version 1.6.11
                    

xslt

Command-line XSLT 3.0/4.0 processor for .NET. Transform XML documents from the terminal using the PhoenixmlDb XSLT engine.

Installation

dotnet tool install -g xslt

Usage

# Transform XML with a stylesheet
xslt stylesheet.xsl input.xml

# Write output to a file
xslt -o result.html report.xsl data.xml

# Start from a named template (no source needed)
xslt -it main generate.xsl

# Pass parameters
xslt -p year=2026 -p title="Report" style.xsl data.xml

# Read source from stdin
cat data.xml | xslt transform.xsl

# Show timing breakdown
xslt --timing style.xsl large-input.xml

# Validate a stylesheet without running
xslt --dry-run style.xsl

# Stream large files (lower memory)
xslt --stream style.xsl large-input.xml

Features

  • XSLT 3.0/4.0 — packages, streaming, maps/arrays, higher-order functions, JSON output
  • Multiple output methods — XML, HTML, XHTML, text, JSON, adaptive
  • Streaming — process large files without loading into memory
  • xsl:result-document — generate multiple output files in one transform
  • Parameters — pass values from the command line
  • Timing — built-in performance profiling
  • Tracing — log template matching, function calls, and built-in rules

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
1.6.13 51 9/2/2026
1.6.12 59 8/30/2026
1.6.11 55 8/29/2026
1.6.10 60 8/27/2026
1.6.9 220 8/26/2026
1.6.8 53 8/26/2026
1.6.7 63 8/24/2026
1.6.6 68 8/23/2026
1.6.5 62 8/22/2026
1.6.4 89 8/16/2026
1.6.3 69 8/14/2026
1.6.2 64 8/13/2026
1.6.1 72 8/4/2026
1.6.0 74 7/31/2026
1.5.0 78 7/27/2026
1.4.25 80 7/17/2026
1.4.24 74 7/14/2026
1.4.23 93 7/12/2026
1.4.22 83 7/10/2026
1.4.21 75 7/9/2026
Loading failed

### `xsl:attribute` content leaked into the caller's sequence

Reported by Martin Honnen against XSpec's `format-xspec-report.xsl`:

   XTTE0505: Template 'scenario-html-class-attribute' return value does not match
             declared type Attribute: expected exactly one item, got 2

His objection was the right one — a template whose body is a single `xsl:attribute` cannot
express two items, so the second had to come from the engine. It did: the attribute's VALUE was
landing in the caller's result sequence while the attribute node itself was built empty.

`xsl:attribute` has two branches. The one taken when `separator` is present isolates the
enclosing sequence; the common no-separator branch did not — and `xsl:sequence` checks for an
active sequence accumulator *before* any attribute-content check. So

   <xsl:attribute name="class">
     <xsl:choose>…<xsl:sequence select="'failed'"/>…</xsl:choose>
   </xsl:attribute>

inside a typed template appended `"failed"` to the caller. Verified against his actual
stylesheet: it now emits complete HTML with the correct `class` values.

### Both CLIs report the engines they bundle

`xquery --version` read 1.6.9 while embedding `PhoenixmlDb.Xslt` **1.6.6**, so four releases of
XSLT fixes were unreachable from the command line and nothing on screen said so. Martin had to
infer it from a repro that kept failing against a version that supposedly contained the fix.

   xslt 1.6.11 (PhoenixmlDb XSLT 3.0/4.0)
     PhoenixmlDb.Xslt 1.6.11
     PhoenixmlDb.XQuery 1.6.10
     PhoenixmlDb.Core 1.6.7

A version identifies the package, not what it carries. Printing it surfaced live drift on the
first run, which this release also clears (the XQuery pin moves 1.6.9 → 1.6.10).

### Package locations without another vendor's file format

`fn:transform` could only learn package locations from a Saxon configuration document, which
made another implementation's format a de facto dependency for `xsl:use-package`. There is now
a native vocabulary:

   'vendor-options': map {
       QName('http://phoenixml.dev/ns/vendor-options', 'packages'): map {
           'http://example.org/lib.xsl' : 'lib/library.xsl',
           'http://example.org/other'   : map { 'location': 'o.xsl', 'version': '2.0' }
       }
   }

Saxon's vocabulary is still read so existing stylesheets keep working, but it is now one
recognised vocabulary rather than the only door. Options in other vocabularies are ignored
rather than claimed — the first cut matched a bare local name `configuration` in any namespace,
which would have seized a foreign vendor's option and could mask a real one.

### Typed template bodies no longer double-count their own text

Text written inside a stylesheet function went to both the sequence accumulator and the output
buffer, and the pass that recombines them assumed they were disjoint — so a template declared
`as="text()"` returned two items with identical content. Two XSpec suites went from erroring at
the Run stage to completing.

   Xslt.Tests 1315 passed, 0 failed, 1 skipped (1310 at 1.6.10)
   XSLT conformance 10237/10630 = 96.30%
   XSpec: 62 of 284 suites complete end to end