ELEMENTS OF DATA SPACES
Identifying high-level requirements, from which to derive an implementable design that satisfies the concerns of key stakeholders, in this case those of the participants in common European data spaces, should assume that common European data spaces are not to be seen only as technical infrastructures, but as inclusive initiatives that cater for a balanced set of technical, organisational and legal or governance-related aspects.
While being a new initiative at the EU level, data spaces are not a fully greenfield project to be built from scratch. Indeed, many public and industry-led initiatives have already started to build and pilot data sharing ecosystems, and there is an expectation that while these may be heterogeneous, some of the know-how, lessons learned — and even the software building blocks — produced by these examples could be reused for the common European data spaces, which, while not representing a formal continuation of these initiatives, may share a similar vision.
These considerations and constraints will influence the process for defining the requirements of data spaces, requiring a tailored approach, and in this section, we provide an initial reflection on what this process may entail.
PARTICULARITIES OF DATA SPACES
Some particularities of data spaces are the following:
Multiple iterations during the design process: Many instantiations are expected, corresponding to the different sectors of operation. These are anticipated to have a common base but will inevitably present slightly different priorities and trade-offs in their design, according to the nature of the data assets managed, as well as the characteristics of their participants and the applications hosted.
Multi-functionality for multi-user requirements: They should provide functionality for a broad range of societal stakeholders. These include not only policymakers and public administrations, but also private sector organisations of all sizes, the scientific community, and the public at large.
CONTINUE THE JOURNEY INTO THE TECHNICAL REQUIREMENTS OF DATA SPACES
HIGH-LEVEL NEEDS
Architecture definition is one of the first activities to be initiated in the data spaces project lifecycle
REQUIREMENTS (1)
From supporting data spaces policy, FUNCTIONAL requirement categories of Data Spaces have been identified
REQUIREMENTS (2)
Learn what are the main NON-FUNCTIONAL quality attributes of a data space and why they are needed
INITIATIVES
See how to leverage on existing data space examples to improve building and production efficiency