Introduction
Akoma Ntoso is the OASIS standard (LegalDocML) that defines an XML vocabulary for parliamentary, legislative and judiciary documents. This site is a verbatim, word-for-word reference for the Akoma Ntoso document family, built from the OASIS published deliverables with no paraphrase: every page mirrors the source tables and rows, and build-time checks verify word-level integrity for the rendered documents. The left sidebar groups every published document separately: one entry per document, nothing interleaved; this page is the standalone entry point.
Use this site to:
-
look up any AKN 3.1 element, complex type, simple type, element group, attribute group or attribute as an atomic page with its verbatim annotations, facets, children and XML examples (Part 2 group);
-
read the full specification prose (Part 2: Specifications of AKN 3.1, OASIS Standard 2026), the Part 1 XML Vocabulary (OASIS Standard 2018, the AKN 3.0 era document) and the Naming Convention (NC v1.0, OASIS Standard 2019) word-for-word;
-
download the schema files (
akomantoso30.xsd,xml.xsd) shipped with the v2.0 package for Level-1 validation, and follow the assembly guides for complete documents (act,judgment). -
call the same knowledge base from software: the read-only MCP server and REST API are documented in MCP & REST API.
Site map
-
Introduction: this page
-
Part 2: Specifications of AKN 3.1 (OASIS Standard 2026)
-
Part 1: XML Vocabulary (AKN 3.0, OASIS Standard 2018): Part 1 index
-
Naming Convention (NC v1.0, OASIS Standard 2019): NC index
-
Site Content (site editorial)
Site note: provenance. The three document groups above render OASIS published specifications verbatim; the last group (Site Content) holds the site-authored editorial supplements, which are not part of any OASIS document.
Part 2 main-schema components
Rendered from the OASIS published specification (akomantoso30.xsd):
| Item | Count |
|---|---|
| Elements | 341 |
| Complex Types | 62 |
| Simple Types | 32 |
| Element Groups | 35 |
| Attribute Groups | 79 |
| Attributes | 114 |
Document coverage
Where each artefact of the Akoma Ntoso family lives. This site carries Part 2: Specifications of AKN 3.1 (element/type/attribute reference above, plus the specification prose under Specification & Notices) and Part 1: XML Vocabulary (OASIS Standard 2018) (verbatim prose under Part 1: AKN 3.0 era; see the Part 1 index).
| Document | Version / Date | Status | Availability |
|---|---|---|---|
| Part 2: Specifications of AKN 3.1 | AKN 3.1: 2 October 2026 | OASIS Standard (current) | This site: full content |
| Part 1: XML Vocabulary | Akoma Ntoso v1.0: 29 August 2018 | OASIS Standard of the AKN 3.0 era; Akoma Ntoso 2.0 does not include a Part 1 | This site: verbatim prose (Part 1 index) · OASIS docs |
| Akoma Ntoso Naming Convention | NC v1.0: 06 June 2017 | OASIS Committee Specification 01; normatively referenced by Part 2 conformance (Level 2: eId/wId + FRBR naming) | This site: verbatim prose (NC index) · OASIS docs |
| AKN4UN | UN localization guidelines | UN HLCM practice documents for UN material: separate from the OASIS standard parts | unsceb-hlcm.github.io |
Namespace history
| Namespace URI | Used by | Notes |
|---|---|---|
http://docs.oasis-open.org/legaldocml/ns/akn/3.0 | AKN 3.0 (OASIS Standard 2018) and AKN 3.1 (OASIS Standard 2026) | Stable namespace URI; targetNamespace of akomantoso30.xsd. The URI resolves to the XML namespace document. |
| Legacy pre-OASIS AKN namespaces | Documents from the community era (pre-2011) | Old deployments only; not covered by this site |
Site note: specification URI vs schema target namespace. The LegalDocML TC defines
AKN 3.1 as a backwards-compatible incremental extension of AKN 3.0, so the distributed
schema file keeps the name akomantoso30.xsd and its targetNamespace
http://docs.oasis-open.org/legaldocml/ns/akn/3.0, while the specification URI of
AKN 3.1 is http://docs.oasis-open.org/legaldocml/ns/akn/3.1: a policy-driven split
between the conceptual identifier (namespace document, Part 2 §7) and the physical XSD
declaration. This is why the element and attribute pages above list
ns/akn/3.0 as the namespace even under the AKN 3.1 specification.
For Level-1 syntax validation, bind the parser to the v2.0 akomantoso30.xsd through
an XML Catalog mapping so that instances declaring either URI validate against the
same schema. See Schemas & Validation.