Skip to content

UNECE/SDMX-DDI-Interoperability-for-Data-Integration

Repository files navigation

SDMX-DDI-Interoperability-for-Data-Integration

This activity is undertaken under the work programme of the High-Level Group for Modernisation of Official Statistics. See original activity proposal, which defines the scope of the work

Use Cases

Interoperability between SDMX to DDI-CDI - Work plan

Concrete deliverables are centered on creating an automated data integration workflow using DDI-CDI as a central link. The primary deliverables is a set of mappings and Python scripts designed to automate the transformation of data from different source models into a unified DDI-CDI representation and vice-versa. These scripts will cover three specific use cases:

  1. A simplified "proto-SDMX" example
  2. A full SDMX XML message from the ILO
  3. An example using Google Data Commons's .mcf files (based on schema.org)

Accompanying these scripts, the working stream has produced a "DDI-CDI dimensional data integration profile" which is a subset of the full DDI-CDI classes and properties that are relevant for describing and integrating dimensional data.

These files will serve as tangible examples of the desired DDI-CDI output for each use case, conforming to the specified DDI-CDI profile and extensions. Additionally, the project will deliver supporting documentation, including a summary document, a checklist of deliverables, and an analysis of open issues, priorities, and next steps. A key part of the work also involves identifying and brainstorming methods to codify the necessary data mappings and transformations

For more information see Discussion on model elements and overall approach and DDI-CDI and other standards.

Interoperability between DDI Codebook to CDI

  • EOSC Metadata Schema and Crosswalk Registry was not successful as it reported an error during the import of the DDI-CDI xsd file before to broke completely.
  • Mapping elements for DDI-C to DDI-CDI can be found in these two tables
  • Mapping of DDI Codebook metadata at the variable level which is suitable for producing DDI-CDI was embedded also in the Python tools developed by Pascal Heus, which were documented with Copilot, based on the codebook_to_ddi methods
  • DDI-Codebook file developed by Knut Wenzig (DIW Berlin), with 2 files/datasets, each with 2 variables. One variable also has missing categories/codes. The content was inspired by this working paper: Publishing Fine-Grained Standardized Metadata – Lessons Learned from Three Research Data Centers - KonsortSWD This could be used with Pascals tool to produce DDI-CDI. Afterwards one would have the basis to present different snippets of DDI-C (like in the working paper above) and compare them with DDI-CDI an approach which seems to be more promising that finding 1 to 1 relations between the two standards’ elements.

How to define mappings

Problem statement: Metadata mappings for data integration

Main proposal: combined use of technical standards to meet different mapping needs. This includes the use of RML to handle structural transformations (schema alignment and implicit identifiers) while SSSOM to handle semantic negotiation (value and unit alignment).

Benefits

  • Bridges the structural gap: semantic mapping alone is insufficient for end-to-end data integration; distinguishing between "schema lifting" (RML) and "semantic alignment" (SSSOM).

  • Enables machine-actionable ETL: By moving from procedural code to declarative mapping files, we pave the way for automated discovery and execution of cross-domain data integration pipelines.

  • Promotes scalable interoperability: support of "data mesh" approach, allowing data providers to publish authoritative mappings that consumers can reuse, significantly reducing the manual effort required for integration.

  • For more information see extensive report on Metadata Mapping and Data Integration

  • SDMX-XMLto DDI-CDI structural mapping specification

Past activities

Presentations from the second call (20-2-2025)

Presentations from the third call 6-3-2025)

  • SDMX Content constraints (Edgardo)
  • [Use of concepts at different granularities in CDI] (conceptual variables, conceptual domains, etc.) (Dan)

Fourth call (27-3-2025)

Fifth call (15-4-2025)

  • Data description in DDI-CDI (Flavio)

Call 3-6-2025

  • Presentation "diagrams 2" (Luis)
  • Presentation "Recap and update" (Flavio)
  • CodeList mapping (Flavio)

Call 26-6-2025

  • DDI products mappings (Wendy)
  • Tentative SDMX-DDI fragment for data (Flavio)

Call (8-7-2025)

Presentation (29-09-2025)

SDMX Global Conference: Towards Practical Interoperability: Mapping SDMX and DDI for Data Integration

Dagstuhl workshops (9/21-11-2025)

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •