Guiding Questions

Purpose of this Building Block Component: The offering comprises data assets and associated services that enable use cases. This includes: data products and services.

Data Space Offerings

Data products

structured environmental, spatial, emissions, material flow, or asset-level data

Services

access control, consent management, data quality assurance, enrichment tools, compliance reporting modules

It is essential to bundle offerings in a way that reflects user needs (e.g. emissions dashboard for real estate owners; API-based footprint verification for consultants).

This should also account for:

  • Licensing models

  • Terms of use

  • User support services

  • Interoperability with EU data infrastructure (e.g. Data4Sustainability, EUDR registries)

A well-structured offering enhances usability, legal certainty, and trust, increasing uptake and long-term engagement.

Data Products

Purpose: Clearly structured environmental, spatial, emissions, material flow, and asset-level data.

  1. What key data assets will be initially offered?

  2. How will data assets be standardised and validated?

  3. How frequently will data be updated and shared?

  4. How can data products be designed to be modular and reusable across multiple use cases?

  5. How can data assets be standardized and validated efficiently?

  6. How can offerings remain aligned with participant needs over time

Functional Questions:

  1. What data model will be used?

Functional/Technical Questions:

  1. What is the source of the data?

Note: This topic is also covered in the Data Space Offering Strategic Questions WP6

  1. How can offerings remain aligned with participant needs over time

Associated Services

Purpose:

  • Data access control & consent management

  • Data quality assurance & validation

  • Data enrichment tools (e.g., analytics, visualisation)

  • Compliance reporting modules (aligned with CSRD,etc)

Questions:

  1. Which services are critical to the initial use cases?

  2. How will compliance and consent management be technically enforced?

  3. What are the minimum standards for data quality assurance?

  4. Which services add the most value to participants while remaining interoperable?

  5. How should services be prioritized based on current and future use cases?

Licensing and Terms of Use

Purpose: Licensing models clearly aligned with open data standards or commercial/regulated usage. Define clear terms of use, including IP rights, access rights, and permitted usage.

  1. Under which license models will data be provided?

  2. Are there specific data-usage restrictions or access tiers?

User Support

Purpose: Define helpdesk, training resources, and dedicated support channels.

  1. How will support needs differ across stakeholders (public/private, technical/non-technical)?

  2. Who will deliver these support services (in-house, third-party)?

  3. How can support resources be tailored to different types of participants?

  4. How can training ensure quality data contribution?

Interoperability

Purpose: Alignment with EU-wide data infrastructures (Data4Sustainability, EUDR registries, Copernicus) and Common EU Data Spaces (CEADS, EMDS, etc). Define Standardised data formats and APIs.

  1. Which external EU registries and frameworks should be integrated to ensure compliance and interoperability?

  2. How will ongoing alignment with evolving EU data interoperability standards be ensured?

Last updated