<!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>
      <journal-title-group>
        <journal-title>IEEE Internet of Things Journal 12 (2025)
163-173. doi:10.1109/JIOT.2024.3459477.
[12] J. Xu</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.1109/AINA.2009.92</article-id>
      <title-group>
        <article-title>Towards Levels of Assurance for Data Trustworthiness</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Florian Zimmer</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Janosch Haber</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mayuko Kaneko</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Takuma Takeuchi</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Fraunhofer Institute for Software and Systems Engineering ISST</institution>
          ,
          <addr-line>Speicherstraße 6, Dortmund, 44147</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Fujitsu Limited</institution>
          ,
          <addr-line>4-1-1 Kamikodanaka, Nakahara-ku, Kawasaki, Kanagawa 211-8588</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Fujitsu Research of Europe</institution>
          ,
          <addr-line>9 Albert St, Slough SL1 2BE</addr-line>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>8872</volume>
      <fpage>0000</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>As data is increasingly acknowledged as a valuable asset, inter-organisational data sharing has recently received much attention. Yet, despite its potential, organisations are still hesitant to engage in data sharing activities, with a lack of trust mentioned as the main barrier. Existing work to mitigate trust barriers usually focuses only on data security concerns or risks from a data provider perspective. In this work, we highlight the unbalanced view on trust and focus on the data usage risks data consumers face. Following design science research, we propose a conceptual, first-iteration artifact called Levels of Assurance for Data Trustworthiness (Data LoA). Data LoA aims to provide an overarching framework to assure data trustworthiness in interorganisational data sharing. Assuring data trustworthiness is suggested to improve data consumers' risk assessment and decision-making capabilities, and enhances trust and transparency between data providers and consumers. This paper is focused on outlining central mechanisms of our new concept, intending to facilitate a wider discussion on the technical and social aspects and requirements of establishing data trustworthiness.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Data Trustworthiness</kwd>
        <kwd>Levels of Assurance</kwd>
        <kwd>Inter-Organisational Data Sharing</kwd>
        <kwd>Trust</kwd>
        <kwd>Data Spaces</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In an increasingly interconnected world, data is acknowledged as one of the key drivers of innovation
and growth in business and society [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Consequently, inter-organisational data sharing has recently
gained much attention from both researchers and practitioners, aiming to unlock the full potential of
data by sharing it across organisational and country borders [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        Despite its potential, in practise, organisations often hesitate to engage in data sharing activities.
Research suggests that a lack of trust and transparency are among the most fundamental barriers
hindering a widespread adoption of inter-organisational data sharing [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Addressing these factors,
significant effort has been put into the development of data spaces that address central data sovereignty
concerns of data providers by enabling them to maintain control over their data [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        A main concern of data consumers, on the other hand, is the risk of utilising third-party data, e.g.
for (automated) decision-making, without reliable means to assess its quality, integrity and
trustworthiness. [
        <xref ref-type="bibr" rid="ref1 ref2 ref4">4, 1, 2</xref>
        ]. However, as data usage risks can range from financial losses to human harm
[
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ] data consumers usually have no other option than to put their trust in the data provider, as trust
cannot be established on the data level itself [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>In this study, we argue that equipping data consumers with improved risk assessment and
decisionmaking capabilities contributes to completing the previously imbalanced perspective on data sharing
risks, and that establishing the trustworthiness of shared data assets themselves could be a key
enabling factor to accelerate the adoption of inter-organisational data sharing. Following a design
science research (DSR) approach, we develop a new artifact to bridge the gap between existing
approaches to assure data trustworthiness and the complex requirements of inter-organisational data
sharing. As a result, we propose Levels of Assurance for Data Trustworthiness (Data LoA), a novel
framework aimed at enhancing trust and transparency among data providers and consumers. Being a
first-iteration artifact, this work focuses on fundamental ideation, outlining key actors, their
interactions, and potential data trustworthiness dimensions. We demonstrate the technical application
of a first subset of Data LoA features by implementing a proof of concept (PoC) and conducting an
experimental simulation based on a real use case scenario in the Mobility Data Space. Trust, however,
is a complex socio-technical and context-dependent, subjective assessment that goes beyond pure
technical measures. The purpose of this paper, therefore, is to articulate our novel concept and facilitate
a wider discussion on the different aspects and requirements of functional data trustworthiness.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>Data trustworthiness has been studied extensively across various domains and applications such as
healthcare, defence, traffic control, and manufacturing [8]. Previous work has produced a wide range
of different solutions to measure, assess, and assure data trustworthiness, especially in the contexts of
internet of things (IoT) and mobile crowd sensing (MCS). Many solutions accomplish this by binding
data trustworthiness to different metrics and dimensions.</p>
      <p>In [9], for instance, the authors propose a trust score model to measure the trustworthiness of
industrial IoT data sources based on accuracy definitions established by an expert panel. Conversely,
in [10], the authors aim to increase data trustworthiness in IoT by estimating it based on syntactic and
semantic rules, considering data origin and time of creation. Similar approaches determine data
trustworthiness based on the similarity of multiple sensor readings in close proximity [11]. In [12], the
authors opt for a more holistic approach, proposing a data trustworthiness framework for carbon data
in the construction sector. Mentioning data availability, quality, security, and compatibility, the authors
aim to provide clear actions to increase the trustworthiness of data as it is generated and managed.</p>
      <p>Most solutions establish data trustworthiness through transparency, either by communicating
relevant aspects directly or by assembling and providing some kind of trust score. However, as most
of these solutions are tailored to a specific use case, they recognise different ways of assessing data
trustworthiness. Thus, none of them is designed with interoperability in mind, failing to provide a
comprehensive view of data trustworthiness, especially in the context of inter-organisational data
sharing. We, therefore, argue that a more general, overarching solution is needed that clearly
articulates relevant dimensions of data trustworthiness and defines transparent processes on how to
assure and assess it across organisational and legislative borders.</p>
      <p>A promising solution to overcome this fragmented landscape is levels of assurance (LoA). LoA is an
assurance technique to improve and simplify risk management and decision-making capabilities to
evaluate and grade complex scenarios [13]. The concept of LoA has been predominantly used in the
domain of identity validation, e.g. in the ISO/IEC 291152 standard for authentication assurance or in
the eIDAS3 directive declared by the EU to address the fragmented landscape of verification schemes
across member states. Another well-known identity LoA is the NIST-800-63-A4 guideline. They all
specify a range of concrete levels (such as high, substantial, and low), clearly defining what processes,
management activities, and technologies must be employed to reach a certain degree of confidence in
the assured claim. That means the more measurements are in place to ensure a given claim, the higher
the LoA. However, although there are many different LoAs already, none exist for assuring and
assessing the trustworthiness of data. To the best of our knowledge, we are the first to adapt LoA to
data trustworthiness to meet the requirements of complex inter-organisational data sharing scenarios.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Methodology</title>
      <p>In this paper, our goal is to address the lack of trust from the perspective of data consumers. We
conducted a rigorous DSR approach following Peffers et al. [14] to design a novel Data LoA artifact,
providing a framework for unifying and standardising the assurance of data trustworthiness in
interorganisational data sharing. More specifically, we followed an objective-centred DSR approach, building
upon existing data trustworthiness assuring and measuring artifacts. However, as previous solutions
were not necessarily developed using DSR, available design knowledge was limited. Therefore, we
began by mapping the problem and solution space, identifying challenges, solutions, and goals by
conducting a structured literature review (SLR) following vom Brocke et al. [15].</p>
      <p>We started with an exploratory pre-study using Google Scholar to increase familiarity with the
subject. Next, we conducted a keyword-based search and screenlining process to select relevant
articles, and performed back- and forward searches as recommended in [15] to achieve improved
coverage. Ultimately, this led to the identification of a total of 62 articles, which we labelled by domain
and artifact type based on the taxonomy proposed in [16], i.e. conceptual, mathematical, architectural
and framework. Additionally, we identified frequently mentioned motivations, challenges, and
common objectives for individual solutions. This analysis was done to ensure the relevancy of our
artifact and to inform our design efforts. Lastly, we collected all occurrences of aspects mentioned in
literature related to data trustworthiness to provide a broad perspective on different notions of trust.
The conducted research process is outlined in Figure 1. The complete labelled literature body is made
accessible for full transparency in [17].</p>
      <p>We then followed DSR methodology in defining a set of design objectives based on our SLR and
developed a novel, first-iteration artifact. Our design process aimed to address the shortcomings of
existing work by grounding our development efforts on the existing LoA concept, as this seemed to be
a promising solution aligned with the identified design goals. Being a first-iteration artifact, we focused
on defining key mechanisms, actors and their relations to establish a sound foundation for future
iterations. In the third and fourth steps of DSR, we evaluated our concept through instantiating a PoC
using data spaces, providing a field-tested environment for inter-organisational data sharing. This
experimental simulation allowed us to investigate the technical feasibility of our concept and
determine limitations and considerations for future work.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Proposed Solution</title>
      <p>4.1.</p>
      <sec id="sec-4-1">
        <title>Motivations and Objectives</title>
        <p>As we intend our novel framework to address the shortcomings of previous work, we first had to map
out and analyse the problem space. To do so, in [18], we present the results of an extensive SLR,
deriving frequently mentioned motivations and common objectives to inform our design efforts.</p>
        <p>
          We found that research agrees on the accuracy and reliability of services, operations, and
decisionmaking being closely coupled to the data they are based on [19, 20]. As a result, utilising untrustworthy,
low-quality data can lead to severe consequences, as past incidents in healthcare and power supply
demonstrated [
          <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
          ]. Additionally, increasingly automated operations are demanding a growing
amount of data [21, 11]. As a result, most solutions aim to increase transparency by measuring or
assuring data trustworthiness to allow for better risk assessment capabilities. This is usually done by
providing an in-depth view of the data’s provenance [22], or by providing an easier-to-comprehend
trust score [9]. However, while increasing data trustworthiness can greatly enhance the accuracy and
reliability of operations conducted with this data, it is also suggested that assuring and increasing data
trustworthiness can be challenging due to the number of aspects involved in establishing it [21].
        </p>
        <p>Besides adopting commonly agreed-on key motivations and goals to guide our design efforts, we
also consider an additional design objective: we found that although most solutions share a common
view of the issue and a shared set of goals, they were not designed with interoperability in mind. Yet,
given the challenging task of ensuring data trustworthiness, we are confident that a holistic solution
is needed — one in which existing solutions might be part of solving the bigger picture. Therefore, we
consider the design objective of interoperability in our design efforts, aiming to develop an overarching
solution to meet the requirements of the complex environment of inter-organisational data sharing.
4.2.</p>
      </sec>
      <sec id="sec-4-2">
        <title>Framework for Establishing Levels of Assurance for Data Trustworthiness</title>
        <p>To enhance trust in inter-organisational data sharing and increase risk assessment and
decisionmaking capabilities for consumers, we propose Data LoA, a novel assurance framework to promote
trust through increased transparency. Following DSR, our proposed concept is a first-iteration artifact,
focusing on central actors and their relations. Similar to existing LoAs within other domains, Data LoA
is defined as the degree of confidence that a data asset’s underlying information can be trusted to be true.
In other words, Data LoA seeks to assure the level of confidence that a data consumer can put into the
trustworthiness of a given data asset, considering the remaining risks they face with respect to trust
attributes not included in the provided assurance.</p>
        <p>To establish the Data LoA framework, we propose to define a range of components to capture
different aspects of ensuring, measuring, claiming, assuring, and assessing the trustworthiness of data
assets. Specifically, we propose that our data trustworthiness framework should contain:
1. a clearly defined actor model that stipulates the different roles, responsibilities and liabilities
of the parties involved in inter-organisational data sharing
2. an application-driven definition of relevant trustworthiness dimensions to be considered
for assuring and assessing data trustworthiness
3. a suitable data usage risk model that can be used to identify and assess the risks connected
to utilising third-party data in a given data-driven application
4. a clear definition of a few concrete trustworthiness assurance levels enabling data providers
to make trustworthiness claims and data consumers to evaluate them
5. a clear, practical guide for selecting appropriate trustworthiness levels for data consumers
given their determined data usage risks
6. a broadly accepted audit model for certifying, as well as auditing and assuring trust ensuring
measures, including the selection and certification of appropriate assurance providers
In the following, we provide initial considerations for the first two of these subcomponents.
4.3.</p>
      </sec>
      <sec id="sec-4-3">
        <title>Data LoA Actor Model</title>
        <p>Within Data LoA we define three main actors: Data Consumer, Data Provider and Assurance Provider.
All actors, as well as their relations, are displayed in Figure 2.</p>
        <p>Data provider and consumer are the main parties commonly encountered in typical data sharing
use cases, with one party providing the data asset and the other consuming it. In the context of LoA,
data providers are called claimants, as they claim the degree of trustworthiness of their asset. Data
consumers are referred to as risk owners, as they face the risks of relying on third-party data assets.</p>
        <p>For a data consumer to decide what level of trustworthiness their application requires, their data
usage-related risks must be assessed. Knowing these risks, consumers can consider provided data
trustworthiness claims and decide whether these sufficiently address their risks. However, as
selfassured claims are usually not considered trustworthy, we suggest that a third-party assurance
provider should be introduced to assure given claims - either by certifying the means of creating and
ensuring a data asset or by auditing the created asset. Depending on the scenario, multiple assurance
providers might be required to audit individual trust attributes.</p>
        <p>Being a first-iteration artifact, it needs to be highlighted that it is not yet clear how the different
levels should be defined, how to assess data usage risks, or how to establish and communicate
trustworthiness claims. Taking a first step towards addressing these central issues, we provide a
preliminary overview of what dimensions of data trustworthiness are likely needed to be considered.
4.4.</p>
      </sec>
      <sec id="sec-4-4">
        <title>Data Trustworthiness Dimensions</title>
        <p>Much research has been conducted on the topic of data trustworthiness across a variety of domains
and applications. However, a high degree of context and domain dependency so far have prevented the
formulation of a generally accepted notion of data trustworthiness [21, 12]. Still, most research agrees
on data trustworthiness being described as the possibility to ascertain the correctness of data provided
by a data source [19]. Taking a first step towards a uniform definition, we conducted a SLR to identify
relevant dimensions in the previously identified existing literature on data trustworthiness. The results
are displayed in Table 1.</p>
        <p>Quality 8 Availability 2 Confidentiality 1
Authenticity 8 Veracity 2 Validity 1</p>
        <p>Timeliness 5 Compatibility 1</p>
        <p>Completeness 4 Credibility 1</p>
        <p>In total, we found 18 different dimensions mentioned in literature. A full overview of the annotated
literature body can be found in [17]. The most mentioned dimensions of data trustworthiness are data
origin, integrity, and provenance. This indicates that the trustworthiness of the source, as well as
maintaining data integrity and being able to backtrack the actors and manipulations involved in the
data lifecycle, are recognised as significant factors in determining the data’s trustworthiness. Besides
that, data security, correctness, similarity, and accuracy are also considered substantial factors. While
security, correctness and accuracy are hard to argue, data similarity is often mentioned in IoT,
determining data’s trustworthiness by comparing data of multiple sensors sensing the same event [11].</p>
        <p>It is worth noting that some dimensions overlap to varying degrees. Data security, for example, is
usually also concerned with maintaining data integrity, while data origin can be considered to be an
element of data provenance. Finally, data quality seems closely related to data trustworthiness, with
some previous publications using these terms interchangeably [12]. Following the ISO/IEC 25012:20085
data quality model, data quality is, among others, comprised of accuracy, completeness, credibility,
currentness, availability, and confidentiality - emphasising the extensive overlap. Consequently, our
findings confirm the lack of a commonly agreed-on notion of data trustworthiness, which will be a
central pre-requisite for defining concise levels of data trustworthiness required by our framework.
4.5.</p>
      </sec>
      <sec id="sec-4-5">
        <title>Demonstration</title>
        <p>To demonstrate the Data LoA framework, we illustrate its real-world application in the Mobility Data
Space, a data sharing ecosystem for real-time traffic data and sensitive mobility data [23]. A key
application for this data is to provide real-time information about traffic conditions and travel times
for daily commutes. However, as data providers comprise a constantly changing, diverse set of public
transport operators, road authorities, traffic management systems, private fleets and mobile network
operators, ensuring pre-existing trust relations is virtually impossible. As a result, data consumers
often have no means of assessing the trustworthiness of available data.</p>
        <p>This use case highlights a number of value drivers for the Data LoA concept: i) the data itself is
valuable. It needs to be brought together to allow for impactful real-time predictions, which means
that data consumers are incentivised to compensate data providers, who in turn are motivated to
provide their data for a secondary value chain; ii) the data is big, complex, and decentralised and
requires extensive data sharing to unlock its full value; iii) there is a large amount of data providers
that cannot all be explicitly trusted; iv) the data usage risks are concrete, as incorrect predictions will
lead to damages to reputation and loss of business for the data consumer.</p>
        <p>Based on the described scenario, we conducted an experimental evaluation by implementing a PoC
to demonstrate the practical implications Data LoA has. To reduce complexity, we simplified the use
case down to a minimal data space, i.e., one connector for each party and a data sink and data source,
respectively. The PoC’s scope and setup are displayed in Figure 3.</p>
        <p>To realise the data space, we utilised the Eclipse Dataspace Components6 framework, as this allowed
for a sophisticated data-sharing environment. Data source and sink were implemented using Python,
offering simple data-providing and -consuming REST APIs. The PoC was deployed using Docker on a
virtual machine running Linux Ubuntu 24.04.2 LTS.</p>
        <p>In the experiment, the provider first selects and publishes a data asset from their data source,
including the Data LoA certificate in the data asset’s custom fields. We used X.509 certificates to include
the assured claim in the certificate’s extension field. This links the assured claim directly to the data
asset, and both are made available in the data space using the data catalog - an overview of available
data assets. Based on this, the consumer is able to make an informed decision about utilising the data
or not, using the appended Data LoA certificate with its assured claim. Using X.509 certificates provides
5 https://www.iso.org/standard/35736.html [11.03.25]
6 https://projects.eclipse.org/projects/technology.edc [11.03.25]
an easy way to get the assured claim validated by the certificate issuer, namely the assurance provider.
We omitted the assurance provider from the demonstrator at this stage for clarity. Nevertheless, we
validated how the provider can effectively communicate the Data LoA claim, and it is made available
to the consumer in inter-organisational data sharing in the sophisticated environment of data spaces.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>In this paper we present a novel, conceptual framework for assuring the trustworthiness of third-party
data assets to address data consumer trust barriers in inter-organisational data sharing. Based on our
findings, we are confident that the Data LoA concept will mitigate data usage risks for data consumers,
enabling them to make informed decisions when selecting what data to utilise and avoid relying on
untrustworthy data in high-risk environments. With the Data LoA framework, data consumers do not
have to rely solely on trust on an organisational level. Instead, they are able to assess trust at a data
level, enhancing overall trust in inter-organisational data sharing by increasing transparency.
However, being a first-iteration artifact, there remain a number of open questions and issues to address.
5.1.</p>
      <sec id="sec-5-1">
        <title>Limitations and Future Work</title>
        <p>Despite following a rigorous research approach, our work is subject to limitations. First, we grounded
our DSR approach on derived design knowledge using a SLR. Naturally, literature reviews are limited
by their coverage. Therefore, we attempted to mitigate this by conducting for- and backward searches.
Still, there remains the possibility of unidentified related work.</p>
        <p>Second, Data LoA is at an early stage. As a first-iteration artifact, central open questions remain,
including how to define meaningful, concrete trustworthiness levels, how to assess data usage risks in
a generalisable fashion, and how to establish, communicate and assess trustworthiness claims.
Additionally, the goal of interoperability was not addressed by the PoC demonstrator presented, and
establishing trustworthiness has predominantly been approached from a technical perspective, leaving
many open issues around legal and social responsibility as well as liability.</p>
        <p>We suggest the following future work: First, more work is urgently needed to create a sound
working definition of data trustworthiness and its dimensions. This work provided a first overview of
potential data trustworthiness dimensions, however, further research is needed to develop a more
concise notion, enabling all participants to understand and issue data trustworthiness-related claims.
A promising consortium for this matter might be the CEN working group of Trusted Data Transaction,
as it aims to identify trust characteristics of data transactions [24].</p>
        <p>Second, more work is required on the application of Data LoA: Data providers need to understand
how to establish a claim, while assurance providers need to know how to audit such claims, whereas
data consumers need to be enabled to select an appropriate level. As LoAs are defined risk-based, data
usage risks need to be identified and a selection process established for consumers to make sound
decisions. A promising starting point is existing LoAs like NIST-800-63-A, providing a decision tree to
guide level selection for identity LoA. Thus, future DSR cycles should address these issues.</p>
        <p>Finally, Data LoA needs to be contextualised: Relevant domains, applications, drivers, and
incentives must be identified. This ensures widespread adoption of the framework, clearly
communicating its benefits and trade-offs one must consider when opting to employ it. For instance,
in [25] the authors mention cost and privacy factors involved in ensuring data trustworthiness. Based
on our current understanding, relevant domains could, e.g., be in critical infrastructure, automated
systems in highly sensitive domains, or artificial intelligence in data-scarce environments, as it allows
to weigh training data based on their LoA, potentially achieving higher accuracy.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>In this paper, we present the novel concept of Data LoA, a first-iteration DSR artifact. Data LoA aims
to provide a comprehensive, standardised framework to assure the trustworthiness of data, addressing
data consumers’ trust barriers in inter-organisational data sharing. Data LoA is proposed to improve
data consumers’ risk assessment and decision-making capabilities by enhancing transparency and
mitigating the risks they face when relying on third-party data assets. Having demonstrated a PoC
implementation in the context of data spaces, we are confident that the Data LoA framework is capable
of enhancing trust in inter-organisational data sharing, driving its adoption.</p>
      <p>We found that although Data LoA addresses most of the identified challenges and objectives in
theory, more work is needed until our framework is ready for adoption. Especially a sound working
definition of data trustworthiness and a concrete definition of assurance levels are needed to realise
the Data LoA concept. We suggest that further DSR cycles should be performed to tackle the remaining
open issues incrementally and hope that this paper facilitates a wider discussion on the technical and
social aspects and requirements of establishing data trustworthiness.</p>
      <sec id="sec-6-1">
        <title>Acknowledgements</title>
        <p>The authors would like to thank their team members at Fraunhofer ISST and Fujitsu Research of Japan
for insightful discussions and the reviewers of the BPMS2 2025 workshop for their prompt and
constructive feedback.</p>
        <p>CRediT statement: Florian Zimmer: Conceptualisation, Methodology, Software, Validation,
Investigation, Writing - Original Draft, Visualisation. Janosch Haber: Conceptualisation,
Investigation, Writing – Original Draft. Mayuko Kaneko: Conceptualisation, Investigation, Writing
- Review &amp; Editing, Project administration. Takuma Takeuchi: Supervision.</p>
      </sec>
      <sec id="sec-6-2">
        <title>Declaration on Generative AI</title>
        <p>During the preparation of this work, the author(s) used Grammarly in order to: Grammar and spelling
check &amp; Improve writing style. After using these tool(s)/service(s), the author(s) reviewed and edited
the content as needed and take(s) full responsibility for the publication’s content.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>B.</given-names>
            <surname>Otto</surname>
          </string-name>
          , M. ten
          <string-name>
            <surname>Hompel</surname>
          </string-name>
          , S. Wrobel (Eds.),
          <article-title>Designing Data Spaces: The Ecosystem Approach</article-title>
          to Competitive Advantage, Springer eBook Collection, 1st ed. 2022 ed., Springer International Publishing and Imprint Springer, Cham,
          <year>2022</year>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          -93975-5.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>F.</given-names>
            <surname>Tocco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Lafaye</surname>
          </string-name>
          , Data Platform Solutions, in: B.
          <string-name>
            <surname>Otto</surname>
          </string-name>
          , M. ten
          <string-name>
            <surname>Hompel</surname>
          </string-name>
          , S. Wrobel (Eds.),
          <source>Designing Data Spaces</source>
          , Springer eBook Collection, Springer International Publishing and Imprint Springer, Cham,
          <year>2022</year>
          , pp.
          <fpage>383</fpage>
          -
          <lpage>393</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          -93975-5_
          <fpage>23</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>I.</given-names>
            <surname>Jussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Schweihoff</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Möller</surname>
          </string-name>
          ,
          <article-title>Tensions in Inter-Organizational Data Sharing: Findings from Literature and Practice</article-title>
          ,
          <source>in: 2023 IEEE 25th Conference on Business Informatics (CBI)</source>
          , IEEE,
          <year>2023</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          . doi:
          <volume>10</volume>
          .1109/CBI58679.
          <year>2023</year>
          .
          <volume>10187530</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Faheem</given-names>
            <surname>Zafar</surname>
          </string-name>
          , Abid Khan, Saba Suhail, Idrees Ahmed, Khizar Hameed, Hayat Mohammad Khan, Farhana Jabeen, Adeel Anjum,
          <article-title>Trustworthy data: A survey, taxonomy and future trends of secure provenance schemes</article-title>
          ,
          <source>Journal of Network and Computer Applications</source>
          <volume>94</volume>
          (
          <year>2017</year>
          )
          <fpage>50</fpage>
          -
          <lpage>68</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.jnca.
          <year>2017</year>
          .
          <volume>06</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>H. S.</given-names>
            <surname>Lim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Ghinita</surname>
          </string-name>
          , E. Bertino,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kantarcioglu</surname>
          </string-name>
          ,
          <article-title>A Game-Theoretic Approach for HighAssurance of Data Trustworthiness in Sensor Networks</article-title>
          ,
          <source>in: 2012 IEEE 28th International Conference on Data Engineering</source>
          ,
          <year>2012</year>
          , pp.
          <fpage>1192</fpage>
          -
          <lpage>1203</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICDE.
          <year>2012</year>
          .
          <volume>78</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>F. T.</given-names>
            <surname>Jaigirdar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Rudolph</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bain</surname>
          </string-name>
          ,
          <article-title>Can I Trust the Data I See? A Physician's Concern on Medical Data in IoT Health Architectures</article-title>
          ,
          <source>in: Proceedings of the ACSW Multiconference</source>
          , ACSW'19,
          <string-name>
            <surname>Association</surname>
          </string-name>
          for Computing Machinery, New York, NY, USA,
          <year>2019</year>
          . doi:
          <volume>10</volume>
          .1145/3290688.3290731.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>B.</given-names>
            <surname>Alhaqbani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Fidge</surname>
          </string-name>
          ,
          <article-title>A Time-Variant Medical Data Trustworthiness assessment model</article-title>
          ,
          <source>in: 2009 11th International Conference on e-Health Networking, Applications and Services (Healthcom)</source>
          ,
          <year>2009</year>
          , pp.
          <fpage>130</fpage>
          -
          <lpage>137</lpage>
          . doi:
          <volume>10</volume>
          .1109/HEALTH.
          <year>2009</year>
          .
          <volume>5406198</volume>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>