This release is a pre-release and may not be stable for production use.
OpenADR3 client
This repository contains a plugin for the OpenADR3-client library that adds additional Pydantic validators to the OpenADR3 domain models to ensure compliance with the OpenADR DER profile specification, the Dutch DSO to Service Provider interface. Since compliance with the profile is a superset of OpenADR3, adding validation rules on top of the OpenADR3 models is sufficient to ensure compliance.
Registering the plugin is done using the global ValidatorPluginRegistry class:
from openadr3_client.plugin import ValidatorPluginRegistry
from openadr3_client_nlflex_compliance.nlflex10.plugin import Nlflex10ValidatorPlugin
ValidatorPluginRegistry.register_plugin(Nlflex10ValidatorPlugin.setup())
Version support
The package provides a validator implementation per version of the profile specification, in a subpackage named for that version:
- Nlflex10ValidatorPlugin (
nlflex10): OpenADR DER profile specification v1.0.0
The specification each plugin validates against ships in the spec/ directory of this repository, together with the worked message examples the test suite validates against.
Register the plugin for the version of the specification you implement. An earlier plugin, Nlflex01ValidatorPlugin, validated the unreleased NL-Flex v0.1 draft and has been removed: the released v1.0.0 contradicts that draft on several rules rather than only extending it.
License
This project is licensed under the Apache-2.0 - see LICENSE for details.
Licenses third-party libraries
This project includes third-party libraries, which are licensed under their own respective Open-Source licenses. SPDX-License-Identifier headers are used to show which license is applicable. The concerning license files can be found in the LICENSES directory.
About ElaadNL
ElaadNL is a Dutch research institute founded and funded by the Dutch District Service Operators (DSOs). ElaadNL was originally tasked by the DSOs to kickstart and foster the adoption of Electric Vehicles by installing the first Dutch charging stations, as well as monitoring the effects EVs have on the grid.
A major result of this pioneering work, was the creation of the Open Charge Point Protocol (OCPP), which today is the de-facto standard for CPOs to communicate with and manage their chargepoints. The protocol is now managed in a spin-off organization: the Open Charge Alliance, which is still closely connected with ElaadNL.
Whereas ElaadNL initially focused mainly on EVs, it has now expanded its mandate to include residential energy use with the goal of increasing the adoption of demand response measures. The reason for this move is to improve efficient use of the resources of the DSO in order to reduce grid congestion, which is a major problem challenge for the Dutch DSOs as well as society as a whole.
Metadata
Release files for openadr3-client-nlflex-compliance 0.3.0b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openadr3_client_nlflex_compliance-0.3.0b2.tar.gz | 33.4 kB | With provenance | Details for openadr3_client_nlflex_compliance-0.3.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openadr3_client_nlflex_compliance-0.3.0b2-py3-none-any.whl | Python 3 | none | any | Details for openadr3_client_nlflex_compliance-0.3.0b2-py3-none-any.whl |
Total release size: 70.4 kB
Release files / openadr3_client_nlflex_compliance-0.3.0b2.tar.gz
| Download URL | openadr3_client_nlflex_compliance-0.3.0b2.tar.gz |
|---|---|
| Size | 33.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b74321894903a53e0e42f0e651193591bb4e5317b046faf4fd00f3d531ca935
|
|
BLAKE2b-256 checksum How to use checksums |
c8b8ce66887b26e78385a4a292a99cfbb0a2f4086cb8c918ea8c7af050970380
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / openadr3_client_nlflex_compliance-0.3.0b2-py3-none-any.whl
| Download URL | openadr3_client_nlflex_compliance-0.3.0b2-py3-none-any.whl |
|---|---|
| Size | 37.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1cb0ceeac6888acc39c000f3e4ddf22fe3fcd7f2d9e9a188b7b7d36e1f9a0e1
|
|
BLAKE2b-256 checksum How to use checksums |
8fec87e9b70d06245d3b0f941ea69a02538d08d8bc6e6877812b8942cc5c5b1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logSecurity for openadr3-client-nlflex-compliance 0.3.0b2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for openadr3_client_nlflex_compliance-0.3.0b2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.