spec
Apache-2.0AKN4OLF profile + conformance suite
The profile of Akoma Ntoso and the tests every adapter must pass. The entry point. Read this first.
Open Laws Foundation
Most legal-data projects scrape statutes and dump them into a convenient format. That throws away the structure: cross-references, temporal validity, the relationships between acts. And that structure is the part that actually makes legislation useful to machines. We do the opposite.
Stable identifier olf:it/legge/2019/123/art_3
The one-sentence design rule
Normalize the metadata: identity, time, citations. Never the content. If two lawyers from different countries would argue about how to model it, it stays native. If they agree it exists in both systems, we normalize it.
Entry into force? Exists everywhere → normalize. comma vs section structure? They’d argue → native.
Four pieces. Start with the spec; everything else conforms to it.
spec
Apache-2.0The profile of Akoma Ntoso and the tests every adapter must pass. The entry point. Read this first.
pipeline
Apache-2.0Per-jurisdiction adapters and the ingest → validate → publish workflow that turns official sources into validated Akoma Ntoso.
diff
Apache-2.0The semantic differ and changeset model. It understands Akoma Ntoso structure, so it knows the difference between an amendment and a typo fix.
archive
CC0-1.0The canonical body of legislation, in Akoma Ntoso. Generated by the pipeline, not hand-edited. Public domain.
Early. We are building the first two jurisdictions, Italy and France, to prove that one model holds across two legal traditions. Civil-law structure, two different gazettes, one identifier scheme.
Maintain legal data for a jurisdiction and want it represented here?
Open an issue in pipeline ↗︎