Skip to main content

Schemas & Validation: akomantoso30.xsd (OASIS AKN v2.0)

Editorial page (not part of any OASIS document). It hosts the schema files distributed with the OASIS Akoma Ntoso Version 2.0 Part 2 specification (AKN 3.1, OASIS Standard 2 October 2026) and explains the identifier/layout relationship between the specification URI and the schema target namespace.

ItemValue
Fileschemas/akomantoso30.xsd, static copy hosted on this site
OASIS sourceakn-core/v2.0/os/part2-specs/schemas/akomantoso30.xsd
Size257,230 bytes
SHA-2568f1fe3e187ee5e6f5bc9dfb013f7d9195de6516f077ce10726bedf6260f8b70a
targetNamespacehttp://docs.oasis-open.org/legaldocml/ns/akn/3.0
Import./xml.xsd, schemas/xml.xsd (static copy; OASIS mirror of the W3C XML namespace schema, SHA-256 61960fb3131e38022caad5360e2f33a3382578ab3c80cd58bd74320ede61b20c)

Licenseโ€‹

The schema file carries its own license header (verbatim excerpt from schemas/akomantoso30.xsd):

TERMS AND CONDITIONS

This schema is provided by OASIS, the Copyright Holder, under licence cc-by 4.0, that can also be found at the URL https://creativecommons.org/licenses/by/4.0/legalcode

Redistribution conditions: keep the attribution and the license notice intact; the file itself is distributed unmodified here. The xml.xsd dependency is the W3C xml.xsd schema for the XML namespace (http://www.w3.org/XML/1998/namespace), reproduced unmodified as shipped in the OASIS v2.0 package so the xsd:import ./xml.xsd reference resolves when validating locally.

Specification URI vs schema target namespaceโ€‹

The LegalDocML TC defines AKN 3.1 as a backwards-compatible incremental extension of AKN 3.0. Consequences of that policy:

  • The distributed schema keeps the file name akomantoso30.xsd and the targetNamespace http://docs.oasis-open.org/legaldocml/ns/akn/3.0.
  • The specification URI of AKN 3.1, used as the identifier in Part 2 ยง7 (Conformance) and in the namespace document (akn-core-v2.0-namespace.html), is http://docs.oasis-open.org/legaldocml/ns/akn/3.1.
  • Element and attribute pages on this site therefore list ns/akn/3.0 as the namespace (they mirror the physical XSD declarations), while the AKN 3.1 specification prose names ns/akn/3.1 (see Part 2 conformance).

Level-1 syntax validationโ€‹

  • Validate AKN instances at Level 1 by binding the parser to the v2.0 akomantoso30.xsd.
  • An instance may declare the AKN 3.0 or the AKN 3.1 URI; with an OASIS XML Catalog mapping both resolve to the same v2.0 schema, so re-declaring the namespace in instance documents is never needed for syntax validation.
  • Serve schemas/xml.xsd alongside to satisfy the ./xml.xsd import when validating offline.