redispatch-xml

XML/XSD format parsing, serialization, and validation for Redispatch 2.0, the German electricity-grid congestion-management protocol (§§ 13, 13a, 14 EnWG, mandatory since 1 October 2021).

All nine BDEW Redispatch 2.0 document types are fully implemented: parse, serialize, structural validation, and semantic validation. The crate targets MSRV 1.94 and is #![deny(unsafe_code)].

Regulatory basis

All German grid operators (TSO/DSO) must implement Redispatch 2.0. Absence of a conformant implementation is a regulatory violation under § 14 EnWG.

Document types

All documents are CIM/IEC 62325-based XML, not EDIFACT. IFTSTA status messages (EDIFACT) are handled by the edi-energy crate.

Versions and Anwendungszeitpunkte are BDEW's own catalogue metadata; a Fehlerkorrektur supersedes its base revision without bumping the version, and the conformance test below always reads the newest revision on disk.

XSD schemas and application guidelines are published by BDEW at bdew-mako.de (topicGroupId 25 — XML-Datenformate Redispatch 2.0).

XSD conformance is checked, not assumed

tests/xsd_coverage.rs reads the published XSDs out of the local document mirror and asserts that every element BDEW declares appears in the model, scoped per document. Anything deliberately left out is listed in NOT_MODELLED with a reason; an unexplained entry fails the test.

The check exists because the failure mode is invisible. serde ignores unknown XML elements, so a field simply absent from a struct means an inbound document carrying it is accepted and the value silently dropped — indistinguishable from a document that genuinely omitted it. It caught, among others:

The XSDs are third-party publications and are not redistributed with this crate, so the test skips — visibly, with a message — when no local copy is present. They are published at bdew-mako.de (topicGroupId 25), and the determination behind them is BNetzA BK6-23-241.

Quick start

use redispatch_xml::{parse, parse_and_validate, serialize, Document};

// Auto-detect document type and parse
let doc = parse(xml_bytes)?;

// Parse + structural/semantic validation in one step
let doc = parse_and_validate(xml_bytes)?;

// Serialize a Document back to XML bytes
let bytes = serialize(&doc)?;

// Serialize a specific type (when document type is known at compile time)
use redispatch_xml::{serialize_as, documents::activation::ActivationDocument};
let bytes = serialize_as(&activation_doc, /* add_xml_decl: */ true)?;

// Parse a specific type directly
use redispatch_xml::parse_as;
let doc: ActivationDocument = parse_as(xml_bytes)?;

API overview

Type system highlights

• DocumentId / MarketParticipantId — validated newtypes with Display, AsRef<str>, TryFrom<&str>, TryFrom<String>, custom serde.
• TimeInterval — parses/serializes "yyyy-mm-ddThh:mmZ/yyyy-mm-ddThh:mmZ", validates UTC and start-before-end. Implements Display.
• Decimal3 — non-negative f64 serialized as "NNN.NNN" (3 dp). Implements Display.
• AttrV<T> — ENTSO-E attr-v wrapper (<Element v="…"/>) with new, value(), From<T> and Display; AttrVWithScheme<T, S> adds the codingScheme attribute.
• All public fallible constructors are annotated #[must_use].
• Enums open for extension: Direction, MeasureUnit, MarketRoleType and ControlZone are #[non_exhaustive]. CodingScheme is not — its three values (A10 GS1, NDE BDEW, A01 EIC) are the closed set the XSDs admit.

Market roles

Related crates

Part of mako, an open-source Rust platform for German energy market communication (Marktkommunikation). Full documentation: https://hupe1980.github.io/mako/