<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Data spaces and data ecosystems: diferent names, same purpose?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Amélie Otto</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anthony Simonofski</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Namur Digital Institute (NaDI), MINDIT Research Center, University of Namur</institution>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <abstract>
        <p>The concept of data space has gained traction within the European data strategy, but its distinction from data ecosystems remains ambiguous. Both terms are often used interchangeably despite difering in scope and function. In a digital government context, this distinction is crucial, as public data spaces, such as those emerging in the EU Green Deal, are viewed as promising instruments for data collaboration. However, the lack of conceptual clarity between data spaces and data ecosystems can lead to governance misalignment and hinder efective implementation. This paper aims to clarify this conceptual ambiguity by identifying and comparing the defining characteristics of data spaces and data ecosystems.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Data space</kwd>
        <kwd>Data ecosystem</kwd>
        <kwd>Conceptual framework</kwd>
        <kwd>Public data space</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Since the launch of the European Data Strategy in 2020, the term data space has gained visibility
in the literature, often in close association with the term data ecosystem.[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] While recent studies
often in specific industrial or technical contexts - have acknowledged their conceptual proximity
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], the relationship between the two remains under-theorized. As noted by Curry et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ],
the boundaries between data spaces and data ecosystems are still blurred, particularly beyond
infrastructure-oriented considerations. This calls for a more systematic and nuanced conceptual
framework to distinguish their respective characteristics. With the emergence of public data
spaces as a promising new form within broader data ecosystems,[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] it becomes important for the
digital government research to clarify the distinction between the two. Conceptual clarity is key
to supporting more responsible data practices in public sector governance and future research.
Through this poster, we aim to open a discussion with experts to gather insights and critical
feedback that will inform the development of a conceptual framework distinguishing data
spaces from data ecosystems. To support this efort, we begin with a preliminary co-occurrence
analysis of their usage in the literature.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Motivation &amp; Research objective</title>
      <p>
        Based on a structured bibliometric approach, a co-occurrence network was constructed
using the 100 most relevant publications related to data spaces retrieved from Scopus with the
following query: TITLE-ABS-KEY("data space") AND PUBYEAR &gt; 2019 AND PUBYEAR &lt; 2026
AND (LIMIT-TO(SUBJAREA, "COMP") OR LIMIT-TO(SUBJAREA, "SOCI")) AND (LIMIT-TO(DOCTYPE,
"cp") OR LIMIT-TO(DOCTYPE, "ar") OR LIMIT-TO(DOCTYPE, "ch")) AND (LIMIT-TO(LANGUAGE,
"English")).The records were processed in VOSviewer to extract key terms and generate a
co-occurrence network, where edge thickness reflects term frequency. A strong link between
data space and data ecosystem suggests that they are often associated and may be seen as
conceptually related [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        Although data space and data ecosystem often co-occur in the literature, their presence
in diferent clusters points to diferent conceptual uses [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The literature and co-occurrence
analysis show that the conceptual link between data spaces and data ecosystems remains unclear,
with existing distinctions fragmented and mostly technical or sector-specific. This highlights
the need for a unified conceptual framework, as confusion between terms can cause governance
gaps, legal uncertainty, and misguided policies [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Future work could examine how researchers
and practitioners interpret and use these terms. Approaches such as Q-methodology could
help capture stakeholder perspectives, while comparative case studies could shed light on their
implementation in practice.
      </p>
      <p>Declaration on Generative AI
The author(s) have not employed any Generative AI tools.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>F.</given-names>
            <surname>Möller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Jussen</surname>
          </string-name>
          , V. Springer,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gieß</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. C.</given-names>
            <surname>Schweihof</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gelhaar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Guggenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Otto</surname>
          </string-name>
          ,
          <article-title>Industrial data ecosystems and data spaces</article-title>
          ,
          <source>Electronic Markets</source>
          <volume>34</volume>
          (
          <year>2024</year>
          )
          <fpage>41</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>E.</given-names>
            <surname>Curry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Scerri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Tuikka</surname>
          </string-name>
          ,
          <article-title>Data spaces: Design, deployment, and future directions</article-title>
          ,
          <source>in: Data Spaces</source>
          , Springer, Cham,
          <year>2022</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Lnenicka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Nikiforova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Luterek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Milic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Rudmark</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Neumaier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kević</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Zuiderwijk-van Eijk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. P.</given-names>
            <surname>Rodríguez</surname>
          </string-name>
          <string-name>
            <surname>Bolívar</surname>
          </string-name>
          ,
          <article-title>Understanding the development of public data ecosystems (</article-title>
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>N.</given-names>
            <surname>Donthu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Mukherjee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Pandey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. M.</given-names>
            <surname>Lim</surname>
          </string-name>
          ,
          <article-title>How to conduct a bibliometric analysis: An overview and guidelines</article-title>
          ,
          <source>Journal of Business Research</source>
          <volume>133</volume>
          (
          <year>2021</year>
          )
          <fpage>285</fpage>
          -
          <lpage>296</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>