<!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>J. O. Salas);</journal-title>
      </journal-title-group>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Core Services for Compliant and Trustworthy Data Marketplaces: the EU UPCAST Project</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Soulmaz Gheisari</string-name>
          <email>s.gheisari@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christopher Maidens</string-name>
          <email>C.Maidens@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Semih Yumusak</string-name>
          <email>semih.yumusak@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jaime Osvaldo Salas</string-name>
          <email>j.o.salas@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paolo Pareti</string-name>
          <email>P.Pareti@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>George Giamouridis</string-name>
          <email>g.giamouridis@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Miao Hu</string-name>
          <email>Miao.Hu@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adeel Aslam</string-name>
          <email>A.Aslam@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bijay Prasad Jaysawal</string-name>
          <email>B.P.Jaysawal@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Luis-Daniel Ibáñez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>George Konstantinidis</string-name>
          <email>g.konstantinidis@soton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dumitru Roman</string-name>
          <email>dumitru.roman@sintef.no</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>İstanbul, Türkİye</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Electronics and Computer Science, University of Southampton</institution>
          ,
          <addr-line>Southampton</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>SINTEF</institution>
          ,
          <addr-line>Oslo</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>1862</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>Compliance and trustworthiness are critical to the success of modern data marketplaces, where sensitive information is exchanged across organisational and jurisdictional boundaries. The UPCAST project addresses these challenges through a modular, plugin-based architecture that integrates privacy-preserving consent management, dynamic policy enforcement, and negotiation services. This paper presents the design and interaction of UPCAST's core services, focusing on the bidirectional integration of Consent Management and Negotiation to ensure that agreements are legally sound, policy-compliant, and transparent to all stakeholders. By embedding compliance verification and trust assessment into the negotiation lifecycle, UPCAST moves beyond post-hoc auditing towards real-time, context-aware enforcement. The resulting architecture enables marketplaces that are adaptable to evolving regulatory requirements, interoperable across sectors, and capable of supporting secure, transparent, and mutually beneficial data transactions.</p>
      </abstract>
      <kwd-group>
        <kwd>Consent management</kwd>
        <kwd>Core services</kwd>
        <kwd>Data marketplace</kwd>
        <kwd>Negotiation manager</kwd>
        <kwd>Policy editor</kwd>
        <kwd>Privacy manager</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        (GDPR) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and emerging European data governance legislation, including the Data Governance Act [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ],
the Data Act [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and the Digital Markets Act [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>UPCAST adopts a plugin-based architecture to allow its components to be flexibly deployed, extended,
or replaced depending on marketplace requirements. In this architecture, Core Services provide
functionalities such as authentication, policy management, consent handling, negotiation, trust
assessment, contract generation, monitoring, and contextual awareness (State of the World). These are
complemented by Client Services for user interaction (e.g., Privacy Manager, Negotiation Manager,
Data-asset Submission Manager) and Specialised Services for specific value-added capabilities (e.g.,
ontology-based policy authoring, workflow handling, natural language support). By separating these</p>
      <p>ceur-ws.org
functionalities into modular services, UPCAST facilitates interoperability and promotes the creation
of data marketplaces that can adapt to evolving business models and regulatory landscapes. Beyond
its conceptual design, UPCAST is implemented in collaboration with industry leaders and operates in
concrete marketplace environments, including telecommunications-focused marketplaces led by Nokia 2
and cross-sectoral platforms provided by Dawex 3. These deployments demonstrate the framework’s
applicability across domains with distinct regulatory, technical, and business constraints, and provide a
valuable proving ground for the compliance and trust mechanisms described in this paper.</p>
      <p>
        The conceptual and architectural foundations of UPCAST have been discussed in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], which presents
a generic modular design pattern for data marketplaces, identifies a set of reusable marketplace plugins,
and demonstrates how such an approach supports flexibility, composability, and compliance. That work
emphasises the importance of a plugin-oriented perspective for ensuring that marketplaces can be
incrementally extended and maintained without requiring extensive redesign.
      </p>
      <p>In this paper, we build upon those architectural principles and focus specifically on the Core Services
for Compliant and Trustworthy Data Marketplaces within UPCAST, with particular emphasis on
privacy-preserving consent management and negotiation workflows . We present the updated UPCAST
architecture highlighting how these services interact bidirectionally to ensure that all negotiated
agreements are legally sound, policy-compliant, and transparent to stakeholders. Our contribution is
twofold: (i) to detail the design and integration of Privacy and Negotiation services in the UPCAST
framework, and (ii) to demonstrate how these components collectively operationalise compliance and
trust throughout the data marketplace transaction lifecycle. The remainder of this paper is structured as
follows. Section 2 introduces the UPCAST Core Services for compliance and trust, including Section 2.1
by a detailed description of the privacy services and their integration into marketplace workflows and
Section 2.2 focuses on the automated negotiation capabilities. Section 3 reviews the state of the art in
data marketplace architectures. Finally Section 4 concludes the paper with key findings and outlines
directions for future work.</p>
    </sec>
    <sec id="sec-2">
      <title>2. UPCAST Core Services for Compliance and Trust</title>
      <p>We organise the UPCAST Core Services for compliance and trust into three main categories of services:
Policy Services, End-to-End Services, and Support Services. Each category is implemented as a
set of independently deployable services, enabling flexible composition and seamless integration into
diverse marketplace deployments. Figure 1 presents the updated UPCAST Core Services architecture,
highlighting the interactions that underpin compliance and trust in the marketplace transaction lifecycle.</p>
      <p>
        Policy Services in UPCAST provide the foundation for expressing and enforcing data usage rules.
The UPCAST Policy Editor allows stakeholders to create and maintain machine-readable policies
using languages such as the Open Digital Rights Language (ODRL) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and the Data Privacy Vocabulary
(DPV) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Specialised services such as the ODRL Editor and Ontology Editor support fine-grained
control over permissible actions, obligations, and constraints. All validated policies are stored in a policy
data store, which serves as the authoritative source for compliance verification across the marketplace.
      </p>
      <p>Note that Policy Services are not isolated; they interface directly with Consent Management to ensure
that end-user permissions are aligned with contractual and regulatory requirements.</p>
      <p>End-to-End Services implement the primary operational workflows of the marketplace, integrating
compliance checks into every transaction stage. UPCAST Consent Management service is
responsible for capturing, storing, and validating consent in accordance with the defined policies. It maintains
a bidirectional link with the UPCAST Negotiation Service, to verify that proposed terms respect
the current consent state, prior to negotiation. And after negotiation, it records any updated consent
derived from contractual agreements. The Negotiation Service also coordinates with other operational
services. Trust and Reputation Management provides quantitative trust scores to guide
negotiation strategies. WorkFlow Editor supports users to describe their intended sequence of operations.
2https://www.nokia.com/es_int/nokia-en-espana/
3https://www.dawex.com/en/
Conflict Resolution proposes compliant alternatives when terms clash with policies or consents.
Natural Language Support generates human-readable explanations of contractual clauses. Successful
negotiations are passed to the Contract Generation service, producing both machine-executable and
human-readable agreements stored in a contract repository.</p>
      <p>Support Services provide cross-cutting functionality to ensure that compliance and trust are
maintained across all marketplace operations. The Monitoring Service continuously logs consent events,
policy enforcement actions, and contract executions. The State of the World service aggregates
contextual information such as jurisdiction-specific rules, market conditions, or external compliance
alerts, which can directly influence negotiation outcomes. The Authentication service enforces access
control to ensure that only authorised actors can participate in policy editing, consent management, or
negotiation.</p>
      <p>The integration of these three service categories within the UPCAST plugin-based architecture
ensures that compliance is embedded into the operational fabric of the marketplace, rather than being
an external or manual verification process. In the following, we focus on two of the most critical
capabilities for achieving both compliance and trust: privacy-preserving services and negotiation services.</p>
      <sec id="sec-2-1">
        <title>2.1. Privacy-Preserving Services in UPCAST</title>
        <p>Privacy protection in UPCAST is implemented as an integrated set of services that span the client,
policy, and operational layers of the architecture. Rather than treating privacy as a static compliance
requirement, UPCAST embeds it into the transaction lifecycle through dynamic consent management,
continuous monitoring, and contextual adaptation.</p>
        <p>The Privacy Manager at the Client Layer operates at the client-facing layer, enabling data subjects
and data providers to configure and communicate their privacy preferences in a structured,
machineinterpretable format. These preferences can include various issues such as, the specific purposes for
which data may be used, applicable usage constraints (e.g., time limits), and revocation or modification
rules for previously granted permissions.</p>
        <p>The Privacy Manager transmits these preferences to the consent management service for validation
against active policies.</p>
        <p>The UPCAST Consent Management service works as the authoritative system of record for all
consent-related information. It interacts bidirectionally with the UPCAST Negotiation Service to: (1)
Verify that proposed terms in an ongoing negotiation align with the current consent state. (2) Update
the consent data store once a contract is finalised, ensuring that downstream enforcement mechanisms
have an up-to-date reference.</p>
        <p>Consent Management also interfaces with the UPCAST Policy Editor to ensure that consents are
consistent with regulatory requirements expressed in marketplace policies.</p>
        <p>The Monitoring and Auditability ensures full traceability of privacy-related actions and provides
verifiable evidence for regulatory audits. All consent events—grants, revocations, expirations, and
violations—are sent from Consent Management to the Monitoring Service as structured audit logs.</p>
        <p>The State of the World enhances privacy decision-making by driving contextual constraints into
the consent validation process. For example, it can provide updates on jurisdiction-specific regulations,
contractual obligations inherited from upstream data sources, or newly published compliance guidelines.
This allows privacy enforcement to adapt dynamically to changing conditions, reducing the risk of
inadvertent policy breaches.</p>
        <p>By combining these capabilities, UPCAST operationalises privacy-by-design principles as the
following:
• Privacy constraints are explicitly captured at the point of data onboarding or transaction initiation.
• Enforcement is continuous and context-aware, rather than periodic or reactive.</p>
        <p>• All actions are logged for transparency and accountability.</p>
        <p>This design ensures that privacy is not merely a contractual clause but an actively enforced property of
the marketplace’s operation.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Negotiation-Support Services in UPCAST</title>
        <p>The UPCAST Negotiation Service 4 is responsible for managing the ofer–counterofer process between
marketplace participants, ensuring that contractual terms are both economically optimal and compliant
with applicable policies and user consents. In the UPCAST architecture, negotiation is not a standalone
process but is tightly integrated with other compliance-critical services.</p>
        <p>WorkFlow Editor provides a service to define acceptable workflow patterns from data provider
side and intended workflow from data consumer side. Upon receiving a request to access a data
source, negotiation begins with compliance pre-check, it queries the Consent Management plugin
to determine whether the proposed terms in the align with existing consent records. If the terms of
negotiation violate an active consent constraint or or the intended workflow breaches the provider’s
admitted patterns the negotiation service triggers the Conflict Resolution service to propose compliant
alternatives. Negotiation continues by ofer and counterofer back and forth. Once an agreement is
reached, the updated terms are written back to a consent data store to ensure downstream enforcement.
This bidirectional interaction ensures that no agreement can bypass established privacy constraints.</p>
        <p>To enhance transparency, the Natural Language Support service generates human-readable
summaries of proposed contract terms and policy constraints. This ensures that all parties, regardless of
technical expertise, can fully understand the terms being negotiated.</p>
        <p>
          When negotiation concludes, the Contract Generation plugin produces both Human-readable
agreements for legal review and signature and Machine-executable agreements for automated enforcement.
Contracts are stored in a contract repository and linked to their corresponding consent and policy
records, enabling continuous compliance monitoring.
4UPCAST negotiation protocol extends the Contract Negotiation Protocol (CNP) defined by the
International-Data-SpacesAssociation (IDSA) [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>The Trust and Reputation Management plugin maintains dynamic trust scores for all marketplace
participants, informed by historical contract fulfilment rates, recorded policy violations, and
peerprovided ratings. These trust metrics influence negotiation strategies, allowing the Negotiation Service
to prioritise agreements with high-reputation entities and to adjust contract terms for lower-reputation
parties.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Background and Related Work</title>
      <p>The development of data marketplaces has accelerated in recent years, driven by the need to enable
controlled and value-generating data sharing across organisational and sectoral boundaries. Architectures
for such marketplaces vary from centralised platforms to fully decentralised, peer-to-peer systems, and
hybrids that combine elements of both. Several prominent European initiatives have sought to provide
reference architectures and governance frameworks for trusted data sharing.</p>
      <p>
        The International Data Spaces (IDS) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] framework introduces the concept of connectors to enforce
data usage policies and contractual obligations, with a strong emphasis on interoperability and data
sovereignty. Similarly, Gaia-X [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] defines a federated infrastructure for data exchange, focusing
on trust through certification, identity management, and standardised service descriptions. The
i3MARKET project [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] has explored decentralised data marketplaces with blockchain-based trust
anchors. While each of these initiatives addresses critical aspects of interoperability and compliance,
their architectural models tend to be more monolithic or require substantial integration efort when
adapting to specific sectoral needs.
      </p>
      <p>
        The UPCAST project advances this state of the art by adopting a plugin-based architecture [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
where Core Services and Plugins can be independently deployed, extended, and replaced. This design
philosophy supports rapid adaptation to new regulatory requirements, emerging data usage scenarios,
and evolving market demands. In UPCAST, plugins encapsulate discrete marketplace capabilities—such
as ontology-driven policy authoring, consent management, negotiation, trust and reputation assessment,
and contract generation—each of which can be integrated into diferent deployment contexts without
altering the core architecture.
      </p>
      <p>This modularity enables UPCAST to balance compliance, trustworthiness, and interoperability
while avoiding the rigidity often found in monolithic designs. Moreover, the explicit separation between
Policy Services, End-to-End Services, and Support Services in UPCAST allows stakeholders to compose
marketplace instances that are tailored to both their operational and compliance needs.</p>
      <p>In this paper, we leverage this modular architecture to examine, in depth, two key capabilities
essential to compliant and trustworthy data exchange: privacy-preserving consent management
and automated negotiation services. By analysing their integration and interaction within the
UPCAST framework, we aim to demonstrate how compliance can be operationalised as a first-class
property of the marketplace transaction lifecycle, rather than a post-hoc verification step.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>We present the design of UPCAST’s core services for enabling compliant and trustworthy data
marketplaces, focusing on the integration of privacy-preserving consent management and negotiation
process. Through its plugin-based architecture, UPCAST embeds compliance into the operational fabric
of the marketplace, ensuring that agreements are both legally sound and aligned with user-defined
constraints.</p>
      <p>By maintaining a bidirectional link between Consent Management and the Negotiation Service, the
architecture ensures that compliance is validated in real time, rather than as a post-processing step. The
inclusion of Trust and Reputation Management, Conflict Resolution, and Natural Language Support
further strengthens the reliability and transparency of negotiated agreements.</p>
      <p>Future research and development will extend UPCAST’s capabilities in several directions such as: (1)
Expanding UPCAST Policy Editor to cover domain-specific regulatory requirements and emerging AI
governance standards. (2) Modeling the negotiation process as a strategic game, and automating the
whole negotiation process.</p>
      <p>By pursuing these enhancements, UPCAST aims to set a benchmark for compliance and trust in data
marketplaces, ofering a flexible, modular, and future-proof foundation for secure data exchange across
diverse sectors.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This work was funded by the UKRI Horizon Europe guarantee funding scheme for the Horizon Europe
projects UPCAST (10.3030/101093216).</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>The authors declare that ChatGPT were used in the preparation of this manuscript to improve language
clarity and grammar in certain sections under the authors’ direction.”</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>European</given-names>
            <surname>Union</surname>
          </string-name>
          ,
          <source>Regulation (eu)</source>
          <year>2016</year>
          /
          <article-title>679 of the european parliament and of the council of 27 april 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (general data protection regulation</article-title>
          ), https://eur-lex.europa.eu/ eli/reg/2016/679/oj,
          <year>2016</year>
          . Accessed:
          <fpage>2025</fpage>
          -07-30.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>European</given-names>
            <surname>Parliament</surname>
          </string-name>
          and
          <article-title>Council of the European Union, Regulation (EU) 2022/868 of the European Parliament and of the Council on European data governance (Data Governance Act)</article-title>
          , https://eur-lex. europa.eu/eli/reg/2022/868/oj,
          <year>2022</year>
          .
          <source>Oficial Journal of the European Union, L</source>
          <volume>152</volume>
          ,
          <issue>3</issue>
          .6.
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>European</given-names>
            <surname>Parliament</surname>
          </string-name>
          and
          <article-title>Council of the European Union, Regulation (EU) 2023/2854 of the European Parliament and of the Council on harmonised rules on fair access to and use of data (Data Act)</article-title>
          , https://eur-lex.europa.eu/eli/reg/2023/2854/oj,
          <year>2023</year>
          .
          <source>Oficial Journal of the European Union</source>
          ,
          <string-name>
            <surname>L</surname>
          </string-name>
          <year>2023</year>
          ,
          <volume>22</volume>
          .
          <fpage>12</fpage>
          .
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>European</given-names>
            <surname>Parliament</surname>
          </string-name>
          and
          <article-title>Council of the European Union, Regulation (EU) 2022/1925 of the European Parliament and of the Council on contestable and fair markets in the digital sector (Digital Markets Act)</article-title>
          , https://eur-lex.europa.eu/eli/reg/2022/1925/oj,
          <year>2022</year>
          .
          <source>Oficial Journal of the European Union, L</source>
          <volume>265</volume>
          ,
          <year>12</year>
          .
          <fpage>10</fpage>
          .
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S.</given-names>
            <surname>Gheisari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Yumusak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. O.</given-names>
            <surname>Salas</surname>
          </string-name>
          , L.
          <string-name>
            <surname>-D. Ibáñez</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <string-name>
            <surname>Konstantinidis</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Roman</surname>
          </string-name>
          ,
          <article-title>Towards modular data marketplaces (</article-title>
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>R.</given-names>
            <surname>Ianella</surname>
          </string-name>
          ,
          <article-title>Open digital rights language (odrl), Open Content Licensing: Cultivating the Creative Commons (</article-title>
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>H. J.</given-names>
            <surname>Pandit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Esteves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. P.</given-names>
            <surname>Krog</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Ryan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Golpayegani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Flake</surname>
          </string-name>
          ,
          <article-title>Data privacy vocabulary (dpv)-version 2.0</article-title>
          , in: International Semantic Web Conference, Springer,
          <year>2024</year>
          , pp.
          <fpage>171</fpage>
          -
          <lpage>193</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Contract</given-names>
            <surname>Negotiation Protocol</surname>
          </string-name>
          (CNP),
          <source>International Data Spaces Association</source>
          ,
          <year>2024</year>
          . URL: https://docs.internationaldataspaces.org/ids-knowledgebase/dataspace-protocol/ contract-negotiation/contract.negotiation.protocol,
          <source>part of the Dataspace Protocol, version 2024-1.</source>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>International</given-names>
            <surname>Data Spaces Association</surname>
          </string-name>
          ,
          <source>International Data Spaces Reference Architecture Model</source>
          , https://internationaldataspaces.org/use/reference-architecture/,
          <source>2023. Version 4</source>
          .0.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Gaia-X European</surname>
          </string-name>
          <article-title>Association for Data and Cloud AISBL, Gaia-X Architecture Document</article-title>
          , https: //gaia-x.eu/,
          <source>2023. Version</source>
          <volume>23</volume>
          .
          <fpage>10</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <fpage>i3</fpage>
          -
          <article-title>MARKET consortium, i3-MARKET: Intelligent, interoperable, integrative and deployable opensource marketplace backplane</article-title>
          ,
          <source>European Union Horizon 2020 Project</source>
          ,
          <year>2020</year>
          . URL: https://cordis. europa.eu/project/id/871754, grant Agreement ID:
          <fpage>871754</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>