Every standard this platform implements, and where each one stands. A harmonised standard becomes operative when it is cited in the EU Official Journal; until then we do not claim compliance with it.
We are not reading these from the outside. Dictagon's founder is an expert in CEN/TC 442/WG 12, which is writing the DoPC standard, and participates in the CIRPASS-2 expert working groups on Digital Product Passports.
Two scope statements from the published standards. Neither is our claim. Both describe the data layer this company builds.
“a common information model allowing for the implementation of data dictionary systems”
EN 18223:2026
“through an open, interoperable network without vendor lock-in”
EN 18216:2026
Cited in the EU Official Journal. We build to these as published standards.
Digital product passport. Data exchange protocols
How passport data is exchanged, and the requirement that it move through an open network rather than a single vendor's system.
Secure, efficient data exchange protocols and formats. Data must be human and machine readable, structured, searchable and transferable through an open, interoperable network without vendor lock-in.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
Digital product passport. Unique identifiers
The identifiers for the product, the economic operator and the facility, and how granular they are.
Unique product, economic operator and facility identifiers. Covers global uniqueness, persistence, syntax, granularity (model, batch or item), interoperability and openness.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
Digital product passport. Data carriers
The QR code or other carrier on the product, and the link it makes between the physical item and its digital record.
Data carriers: symbology, format, error correction, encoding, print quality, durability, placement and machine readability, and the link between the physical product and its digital representation.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
Digital product passport. Data storage, archiving, and data persistence
That passport data stays available even if the company that created it no longer exists.
Decentralised storage, archiving and persistence. Data remains available even when the economic operator that created the passport is no longer active, through replication with back-up operators and data lifetime rules.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
Digital Product Passport. Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability
The API through which a passport is created, updated, found and read by other systems.
The DPP application programming interface, covering searchability and the lifecycle interactions of a passport.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
Digital Product Passport. System interoperability
The common information model that lets any system read a passport, including the rules for data dictionary systems.
Semantic description of a product and its properties: a common information model allowing the implementation of data dictionary systems, metadata models and formats allowing dictionary integration, rules for developing product-group-specific data models and dictionaries, and technical and organisational interoperability.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
The registry went live on 20 July 2026. A passport has somewhere to be registered, which is what turns these standards from documents into an operational requirement.
20 July 2026
Measured against the eight Digital Product Passport standards. What is not built yet is listed as not built.
Unique product identifiers at model, batch and item granularity: a GS1 Digital Link where the product has a GTIN, a ten-character code otherwise. Resolvable, and refused at publication if longer than 50 characters.
QR code, generated by the platform, downloadable as SVG and as a 600 dpi PNG with a four-module quiet zone.NFC and RFID carriers.
Versioning and audit: a published passport is never edited, a new version supersedes the previous one, every version stays retrievable, and publication is timestamped.Replication to a backup operator.
The read half of the API: a passport by any of its identifiers, one data element collection at a time, one attached document, a search that answers with passport identifiers, and the authenticity block. Responses use the EN 18223 structure, errors come back as a typed Result, and the OpenAPI description is generated from the endpoints themselves.Write operations — creating, updating and retiring a passport through the API — are planned and not built. Lifecycle management today happens in the platform, not over the API.
Every declared property and environmental indicator carries its data dictionary reference, and opens the definition. Where the dictionary has no entry yet, the passport says so.
JSON and XML exports of the full passport and of the DoPC alone, alongside a spreadsheet for people.
Public and restricted tiers, set per data point, per identification field and per document, honoured in every view, every export and every API read. A restricted document is disclosed as existing and withheld as content, so a reader knows what they are not being shown.Access is by a shared token per passport, not by identity: there are no per-organisation accounts, no roles and no audit of who read what. The wider security framework — key management, transfer of responsibility between operators — is not built.
Every published version is hashed (SHA-256 over its canonical content) and signed with this platform's Ed25519 key. The hash, the signature and the public key are served with the passport and through the API, so a recipient can verify the copy they hold without asking us. The passport page shows the verdict, and says so plainly when content no longer matches its signature.The key is ours and is not certified by any recognised authority: this proves the content has not changed since we published it, not that a third party vouches for us. No qualified electronic seal, no trust list, and no revocation infrastructure.
The EU DPP Registry currently supports only the Batteries product group, and its official guide states that registration is not yet possible even for batteries, because the semantic catalogue is not yet defined. Construction products cannot be registered today. Every passport records its registry status, which stays 'not applicable yet' until registration opens.
The read operations of EN 18222 are live, and described by an OpenAPI document generated from the endpoints themselves rather than written by hand. A passport can be fetched by any of its identifiers, one data element collection at a time, with its attached documents and its authenticity block, and searched for by product information. Write operations are planned and not built.
These texts are at FprEN stage. They exist and we follow them, but they have not published. We do not claim compliance with an unpublished standard, and where our work touches authentication or access control that is the honest position.
Digital product passport. Access rights management, information system security, and business confidentiality
Who may see which parts of a passport, and how commercially sensitive data stays protected.
Access rights management, IT security, data protection and the transfer of responsibility between operators. Public DPP data needs no access restriction to read.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
Digital product passport. Data authentication, reliability and integrity
Proving a passport's data is genuine and has not been altered.
Integrity, authenticity and reliability of DPP data exchange, using electronically signed data constructs, for anti-fraud and anti-counterfeiting purposes.
Committee: CEN/CLC JTC 24 · M/604 and M/604 Amd 1 · Regulation (EU) 2024/1781 (ESPR)
At prEN stage with CEN/TC 442/WG 12. What we generate is versioned against the current text and regenerated when it publishes.
Digital declaration of performance and conformity (DoPC) of construction products. Methodology, general requirements and criteria to develop data templates
How a digital Declaration of Performance and Conformity is structured, and the criteria for developing the data templates behind it.
Guidance for digitalising the Declaration of Performance and Conformity for products CE marked under the CPR. It covers the structure used to declare a product's performance through its essential characteristics, including both technical properties and environmental sustainability performance, and applies to manufacturers issuing a DoPC under CPR 2024. The environmental information supports sustainability assessment developed under CEN/TC 350, using a revised EN ISO 22057 to digitalise LCA-based environmental indicators.
Committee: CEN/TC 442/WG 12 (work item WI 0442061) · Regulation (EU) 2024/3110 (CPR)
Long-published standards and the regulation itself. Everything above rests on these.
Methodology to describe, author and maintain properties in interconnected data dictionaries
How a property definition is authored and maintained so two systems mean the same thing by it.
The methodology behind a data dictionary: how properties are described, authored, versioned and maintained.
Committee: ISO/TC 59/SC 13
Data templates for construction objects
How properties are grouped into a data template for a product type.
Data templates for construction objects used in the life cycle of built assets, and their relationship to data dictionaries.
Committee: ISO/TC 59/SC 13
Library objects for architecture, engineering and construction
How a reusable BIM library object is structured and what data it carries.
Requirements for library objects used in architecture, engineering and construction, including the product data they carry.
Committee: ISO/TC 59/SC 13
Construction Products Regulation
What must be declared for a construction product, and the obligation to make declarations available digitally.
The regulation itself. It replaces Regulation (EU) 305/2011 and introduces the digital declaration and, in time, the construction product's Digital Product Passport.
Committee: European Parliament and Council
Sustainability of construction works. Environmental product declarations. Core rules for the product category of construction products
The core rules an environmental product declaration must follow.
Core product category rules for environmental product declarations of construction products, including the environmental indicators an EPD reports.
Committee: CEN/TC 350
This page is generated from a single source in the codebase, so it changes when a status changes. ICS 35.240.63.
See the data journey →