Standards
EN 18223: The Core Data Model and Semantics
EN 18223 defines the terminology, core data model and semantic rules of the DPP ecosystem — modular templates and interoperability in practice.
EN 18223:2026 is the base of the DPP system standards family: terminology, the core data model and semantic rules. The other standards sit on these definitions.
Why a core model?
If every product group defines its own fields, systems cannot understand each other — yet a recycling facility has to read both textile and electronics passports. The core model fixes the shared structure:
| Module | Content |
|---|---|
| Identity | Identifier, model, batch, serial |
| Operator | Manufacturer, importer, facility |
| Composition | Materials, shares, substances |
| Compliance | Declarations, certificates, tests |
| Circularity | Repair, disassembly, recycling |
| Environmental | Impact indicators and methodology |
Product-specific fields are added as extensions to these modules. See the DPP data model guide.
What "semantics" means
A field name such as "recycledContent" carries no meaning on its own; a machine has to bind it to a known concept. The semantic layer binds fields to global identifiers (URIs) — the job of JSON-LD contexts. See JSON-LD and DPP data.
The practical benefit: passports produced by two different platforms express the same concept the same way and become automatically comparable.
Relationship to sector models
Battery Pass, Catena-X CX-0143 and UNTP publish their own models. EN 18223 provides the common ground onto which they can be mapped. In practice most platforms generate sector serialisations from one canonical model. See AAS and Catena-X and UNTP.
Implementation advice
- Keep the canonical model in one place and generate schemas from it.
- Map field names to sector models and version the mapping table.
- Use language-independent codes. See multilingual passports.
- Represent "unknown" and "not applicable" in the model. See DPP data quality management.
Frequently asked questions
Does the core model give me all the fields?
No. It gives shared structure and semantics; mandatory field sets come from delegated acts. See DPP data fields.
Can I add my own fields?
Yes, as extensions. Adding voluntary fields without breaking the core is explicitly allowed.
What happens to old passports if the model changes?
It is handled through versioning: older passports are interpreted against their own model version.
