makoralle 🪸
makoralle provides pydantic models for the German
MaKo (Marktkommunikation) processes together with serializers that turn those
models into the output formats used downstream:
- YAML – process and EBD (Entscheidungsbaum-Diagramm) representations
- WSD – the websequencediagrams DSL for sequence diagrams
- BPMN – business process model XML
- Markdown – human-readable process documentation
It is the shared, dependency-light foundation (only pydantic and PyYAML) consumed by
the private makorele parser and by the process-documentation webapp.
Separation of concerns
Part of the Hochfrequenz MaKo tooling — four repositories, one responsibility each:
- makoralle (public, PyPI) — the data model + serializers. ← this repo
- makorele (private) — the parser (BDEW PDFs → validated models).
- machine-readable_mako-prozesse (private) — the generated dataset, consumed at a pinned tag.
- mako_prozesse — the web app that presents the dataset.
Dependencies flow one way: makorele → makoralle; the dataset is produced by the tooling and consumed by the web app at a pinned tag. makoralle imports neither the parser nor the app.
Installation
pip install makoralle
Usage
The public serialization API is exposed at the package root and resolved lazily
(importing makoralle, or a light submodule like makoralle.grouping, does not
eagerly pull in the serialization stack):
from makoralle import emit_yaml, emit_wsd, emit_markdown, emit_bpmn
from makoralle.models.process import Process
# build or load a Process model, then serialize it
yaml_text = emit_yaml(process)
wsd_text = emit_wsd(process.sequence_diagrams[0])
The models live under makoralle.models (process, ebd, pid, activity, chunk)
and the serializers under makoralle.serialization.
Development
This project uses the Hochfrequenz src-layout Python template
with uv. To set up a development environment:
uv sync --group dev
Run the unit tests, linting, type checks and coverage (matching what CI runs):
uv run --group tests pytest
uv run --group linting ruff check src/makoralle unittests
uv run --group linting ruff format --check .
uv run --group type_check mypy --strict src/makoralle
uv run --group type_check mypy --strict unittests
cd unittests && uv run --group coverage coverage run -m pytest && cd ..
2 maintainers
Metadata
2 maintainers
Release files for makoralle 0.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| makoralle-0.0.11.tar.gz | 119.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| makoralle-0.0.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 179.0 kB
Release files / makoralle-0.0.11.tar.gz
| Download URL | makoralle-0.0.11.tar.gz |
|---|---|
| Size | 119.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c062bc81ad3361bd35070bc53a24bf74dbecf258ee482c3627d58f82687fbd98
|
|
BLAKE2b-256 checksum How to use checksums |
bc4bae722fcd1472f7f5dc84fc1f78d0b8d384e6d4fd90ea1294e1a8159c07a1
|
| 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 Aug 24, 2026.
Transparency logRelease files / makoralle-0.0.11-py3-none-any.whl
| Download URL | makoralle-0.0.11-py3-none-any.whl |
|---|---|
| Size | 60.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20904cfcd777245193cbcb9cd743e77e97d31d5053a1610061cc09e5a4d7a804
|
|
BLAKE2b-256 checksum How to use checksums |
d15873a332129a2cfbc70b13b4927c83f0bfcfda722a82daccf4096d1803eb27
|
| 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 Aug 24, 2026.
Transparency log
