PhoenixmlDb.Xslt 1.6.6

There is a newer version of this package available.
See the version list below for details.
dotnet add package PhoenixmlDb.Xslt --version 1.6.6
                    
NuGet\Install-Package PhoenixmlDb.Xslt -Version 1.6.6
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="PhoenixmlDb.Xslt" Version="1.6.6" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="PhoenixmlDb.Xslt" Version="1.6.6" />
                    
Directory.Packages.props
<PackageReference Include="PhoenixmlDb.Xslt" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add PhoenixmlDb.Xslt --version 1.6.6
                    
#r "nuget: PhoenixmlDb.Xslt, 1.6.6"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package PhoenixmlDb.Xslt@1.6.6
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=PhoenixmlDb.Xslt&version=1.6.6
                    
Install as a Cake Addin
#tool nuget:?package=PhoenixmlDb.Xslt&version=1.6.6
                    
Install as a Cake Tool

PhoenixmlDb.Xslt

XSLT 4.0 transformation engine for PhoenixmlDb — transform XML documents into HTML, JSON, CSV, text, or other XML formats.

Features

  • XSLT 3.0/4.0 — template matching, streaming, accumulators, packages, maps/arrays
  • All output methods — HTML5, XML, XHTML, JSON, text, CSV, adaptive
  • Multiple outputsxsl:result-document for multi-file generation
  • Full XPath 4.0 — 240+ built-in functions available in all expressions
  • Packages — reusable stylesheet libraries with visibility control

Quick example

using PhoenixmlDb.Xslt;

var transformer = new XsltTransformer();
await transformer.LoadStylesheetAsync(
    File.ReadAllText("style.xsl"),
    new Uri(Path.GetFullPath("style.xsl")));

transformer.SetParameter("title", "My Report");
var html = await transformer.TransformAsync(
    File.ReadAllText("data.xml"));

// Handle secondary outputs (xsl:result-document)
foreach (var (href, content) in transformer.SecondaryResultDocuments)
    File.WriteAllText(Path.Combine(outputDir, href), content);

See the full API overview in the README.

Package Description
PhoenixmlDb.Core Core types and XDM data model (dependency)
PhoenixmlDb.XQuery XQuery 4.0 query engine (dependency)
PhoenixmlDb.Xslt.Cli xslt command-line tool

Documentation

Full documentation at phoenixml.dev

License

Apache 2.0

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  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.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.6.10 0 8/27/2026
1.6.9 32 8/26/2026
1.6.8 49 8/26/2026
1.6.7 63 8/24/2026
1.6.6 71 8/23/2026
1.6.5 91 8/22/2026
1.6.4 117 8/16/2026
1.6.3 88 8/14/2026
1.6.2 86 8/13/2026
1.6.1 106 8/4/2026
1.6.0 108 7/31/2026
1.5.0 127 7/27/2026
1.4.25 106 7/17/2026
1.4.24 88 7/14/2026
1.4.23 131 7/12/2026
1.4.22 107 7/10/2026
1.4.21 111 7/9/2026
1.4.20 103 7/9/2026
1.4.19 100 7/9/2026
1.4.18 101 7/8/2026
Loading failed

Two engine fixes, both found by running the XSpec suite rather than the conformance corpora,
and both in the same family: a name or a namespace that is correct in the source but absent by
the time the engine looks for it.

Together they moved XSpec from 36 suites completing to 39, and from 160 assertions actually
executed to 190. Twenty-one suites advanced a stage; none regressed.

### A typed body's captured output keeps its namespace declarations

A template or variable with an `as=` type captures its body by serializing it and reparsing the
text. The wrapper's namespace declarations were built from the LIVE output scopes — but the
reparse happens after the body has finished and those scopes have popped. A prefix used inside
the captured chunk could therefore be missing from the wrapper, the reparse failed with
`'x' is an undeclared prefix`, and the failure was swallowed: the chunk came back as a plain
string. The typed template then reported

   XTTE0505: type String does not match declared type Element

which names a type mismatch and never mentions namespaces. That distance between cause and
symptom is why seven hand-written reproductions all passed — each constructed its elements
INSIDE the capture, where the serializer emits the declarations. It only breaks when elements
are COPIED in, carrying a prefix but not its binding.

The wrapper is now backstopped with the stylesheet's own prefix bindings, which are in scope
for anything the stylesheet could have constructed.

### `key()` resolves a prefixed name across module boundaries

`key('ns:name', …)` failed with `XTDE1260` ("key has not been defined") when the calling module
bound the prefix to a different URI than the module that declared the key — a normal situation
in a multi-module stylesheet, and the shape XSpec generates. Resolution now falls back to an
unambiguous match on the local name when the qualified lookup misses, which is a fallback and
not a relaxation: it applies only when exactly one declared key has that local name.

This cleared all 27 XSpec suites that were stopping on `XTDE1260`.

### Notes

`PhoenixmlDb.Core` is republished at 1.6.6 unchanged under the uniform-version policy. The real
changes at this number are here and in `PhoenixmlDb.XQuery` (`fn:partition`, the `fn` lambda
shorthand, and `fn:parse-html` reporting `FODC0006` instead of returning its input escaped).

Also in this release, but affecting the test harness rather than the engine: the QT3 runner now
reads the corpus's `<module>` declarations, so `import module` resolves. QT3 module-resolution
errors went 188 -> 40 and the pass rate 92.57% -> 92.76%.