BO4E, with the Rust type system doing the checking.

Install

Nothing but identifier types is on by default. Every dependency past that is a feature you opt into.

# Identifier types only — no schema, no serde_json, no date/decimal deps.
cargo add rubo4e

# The usual application setup: generated types, JSON, real dates and decimals.
cargo add rubo4e --features versioned,json,time,decimal

What the schema cannot give you

Generated types get you the shape of the data. These are the parts that need domain rules from BDEW documents, not the JSON Schema.

A typical round-trip

Parse an incoming payload, reject anything outside the schema, then work with ordinary Rust types.

use rubo4e::current::Marktlokation;
use rubo4e::json::{Bo4eJsonExt, JsonParseLimits};
use rubo4e::Bo4eStrict;

// Parse with size, depth, and extension-data budgets enforced while reading.
let malo = Marktlokation::from_json_german_hardened(
    &body,
    JsonParseLimits::untrusted_defaults(),
)?;

// The serde path is deliberately lenient so a newer schema does not break this
// build. Opt into strictness where bad data must not get through.
malo.ensure_known_enums()?;

// From here it is ordinary Rust: the ID already verified its own check digit.
if let Some(id) = &malo.marktlokations_id {
    println!("{id}");
}

Documentation

Start with whichever question brought you here.