schema.axiomordo.com

ARDS Schema Registry

The authoritative registry of all canonical ARDS schemas, domain packs, and registered extension namespaces. All URIs are permanently resolvable and versioned.

Schema URI Pattern

Every ARDS schema has a canonical, permanently resolvable URI. Resolving the URI returns the JSON Schema document.

https://schema.axiomordo.com/ards/{ardsVersion}/{family}/{schema-name}.schema.json

# Examples:
https://schema.axiomordo.com/ards/1.0/meta/ards-meta.schema.json
https://schema.axiomordo.com/ards/1.0/obligation-record/obligation-record.schema.json
https://schema.axiomordo.com/ards/1.0/fueleu/obligation-record.schema.json
https://schema.axiomordo.com/ards/1.0/cbam/embedded-carbon-declaration.schema.json

Core Schema Set — ARDS v1.0

Six artefact schemas plus the shared metadata envelope. Required for all ARDS implementations.

ards-meta
meta
schema.axiomordo.com/ards/1.0/meta/ards-meta.schema.json
The shared ards:meta metadata envelope. Required in every ARDS artefact.
GA
obligation-record
obligation-record
schema.axiomordo.com/ards/1.0/obligation-record/obligation-record.schema.json
Regulatory Obligation Record (ROR). Captures a single regulatory obligation for an entity and period.
GA
evidence-artefact
evidence-artefact
schema.axiomordo.com/ards/1.0/evidence-artefact/evidence-artefact.schema.json
Evidence Artefact (EA). Structured evidence record with provenance, source type, and verification status.
GA
compliance-verdict
compliance-verdict
schema.axiomordo.com/ards/1.0/compliance-verdict/compliance-verdict.schema.json
Compliance Verdict (CV). Records the formal compliance outcome referencing obligation and evidence.
GA
trace-bundle
trace-bundle
schema.axiomordo.com/ards/1.0/trace-bundle/trace-bundle.schema.json
Trace Bundle (TB). Machine-readable provenance graph linking all artefacts in a compliance lifecycle.
GA
unified-compliance-artefact
unified-compliance-artefact
schema.axiomordo.com/ards/1.0/unified-compliance-artefact/uca.schema.json
Unified Compliance Artefact (UCA). Portable composite embedding obligation, evidence, and verdict in one document.
GA
audit-package
audit-package
schema.axiomordo.com/ards/1.0/audit-package/audit-package.schema.json
Audit Package (AP). Sealed, cryptographically signed archive of all artefacts for a given entity and period.
GA

FuelEU Maritime Domain Pack

v1.0 — GA

Extends the ARDS core schemas for FuelEU Maritime Regulation (EU 2023/1805) compliance. Covers GHG intensity, biofuel blending, shore power, and fleet aggregation.

fueleu/obligation-record
fueleu
schema.axiomordo.com/ards/1.0/fueleu/obligation-record.schema.json
FuelEU ROR extension. Adds vessel IMO number, voyage data, GHG intensity thresholds by article, and fleet pooling references.
GA
fueleu/energy-report
fueleu
schema.axiomordo.com/ards/1.0/fueleu/energy-report.schema.json
Annual energy report per vessel. Fuel types, quantities, WTT and TTW factors, shore power usage, and biofuel blend fractions.
GA
fueleu/ghg-intensity-record
fueleu
schema.axiomordo.com/ards/1.0/fueleu/ghg-intensity-record.schema.json
Computed GHG intensity (WtW, gCO2eq/MJ) per voyage or annual period. Includes calculation methodology and source data references.
GA
fueleu/shore-power-declaration
fueleu
schema.axiomordo.com/ards/1.0/fueleu/shore-power-declaration.schema.json
Shore power connection record per port call. Power consumed, exemption status, and port authority reference.
GA
fueleu/compliance-verdict
fueleu
schema.axiomordo.com/ards/1.0/fueleu/compliance-verdict.schema.json
FuelEU CV extension. Adds penalty calculation, surplus/deficit balance, pooling arrangement references, and EMSA submission metadata.
GA

CBAM Domain Pack

v1.0 — GA

Extends ARDS for the EU Carbon Border Adjustment Mechanism (CBAM). Covers embedded carbon declarations, installation records, CBAM certificates, and authorised declarant profiles.

cbam/obligation-record
cbam
schema.axiomordo.com/ards/1.0/cbam/obligation-record.schema.json
CBAM ROR. Adds CN code, installation country of origin, importation period, and declarant EORI number.
GA
cbam/embedded-carbon-declaration
cbam
schema.axiomordo.com/ards/1.0/cbam/embedded-carbon-declaration.schema.json
Embedded carbon declaration per import consignment. Direct and indirect emissions, carbon price paid in country of origin.
GA
cbam/installation-record
cbam
schema.axiomordo.com/ards/1.0/cbam/installation-record.schema.json
Third-country installation profile. Location, sector, production processes, and national authority reference.
GA
cbam/certificate-record
cbam
schema.axiomordo.com/ards/1.0/cbam/certificate-record.schema.json
CBAM certificate issuance, surrender, and cancellation record. Links to EU Registry transaction IDs.
GA

Preview Domain Packs — ARDS v1.1

These packs are in active development by AxiomOrdo domain working groups. Preview access is available to design partners.

PFAS Domain Pack

v1.1 — Preview

Substance restriction compliance under REACH PFAS restriction proposals. Covers substance identification (CAS/EC numbers), use-case exemptions, supply chain declarations, and phase-out schedules.

Expected schemas: substance-restriction-record, use-exemption-declaration, supply-chain-declaration, phase-out-schedule

Request Preview Access →

ETS Domain Pack

v1.1 — Preview

EU Emissions Trading System compliance. Covers allocation records, verified emissions reports, surrender obligations, and registry transaction references. Aligned with MRV Regulation requirements.

Expected schemas: allocation-record, verified-emissions-report, surrender-obligation, registry-transaction

Request Preview Access →

Registered Extension Namespaces

Third-party extensions must register their namespace prefix in the ARDS Extension Registry. Registered namespaces are reserved globally.

PrefixOrganisationDomainStatusContact
fueleu: AxiomOrdo Group FuelEU Maritime Reserved standards@axiomordo.com
cbam: AxiomOrdo Group EU CBAM Reserved standards@axiomordo.com
pfas: AxiomOrdo Group PFAS Restriction Preview standards@axiomordo.com
ets: AxiomOrdo Group EU ETS Preview standards@axiomordo.com
x-* Any implementor Vendor-specific Open No registration required
To register a new namespace prefix, submit an RFC via the RFC process. Registrations are first-come, first-reserved.