Skip to content
Odal Node
Alpha — Odal Node is in active development. APIs, schemas, and docs may and will change before 1.0.

Standards & interoperability

A passport is only useful if the rest of the world can read it. The core speaks the open standards the regulation itself references, so a passport works with existing tooling rather than locking you into one vendor’s format.

The standards it speaks

  • GS1 Digital Link — the identifier scheme behind the QR code on a product. A scan resolves the product to its passport, and the same link can serve different views to different audiences (a consumer, a recycler, an authority).
  • W3C Verifiable Credentials with did:web — how a passport proves who issued it. Identity is anchored in the issuer’s own domain, so verification is an ordinary web lookup — no central registry, no blockchain, no dependency on Odal staying online.
  • IDTA Asset Administration Shell — an industrial submodel projection, so a passport can flow into Industry 4.0 systems that already speak AAS.

The European system standards, tracked clause by clause

The European DPP system standards — written by CEN/CENELEC JTC 24 — are landing in stages. Six were published in May 2026 — EN 18216, 18219, 18220, 18221, 18222, 18223 — covering exchange, identifiers, data carriers, storage, lifecycle APIs, and interoperability. The remaining two — EN 18239 (access rights, security, business confidentiality) and EN 18246 (data authentication) — are at FprEN stage, expected around September 2026. Odal tracks them clause by clause in a maintained conformance matrix, and the core’s identifier, carrier, API, and authentication semantics align to the published texts. One honest nuance: even a published standard is available but not yet harmonised (cited in the Official Journal) — so we build to them today and claim presumption of conformity only when that citation lands.