<!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 Sharing Negotiation and Contracting</article-title>
      </title-group>
      <contrib-group>
        <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>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>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>Syed Atif Moqurrab</string-name>
          <email>s.a.moqurrab@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>
        <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>
      </contrib-group>
      <abstract>
        <p>The domain of Data Marketplaces is an emerging technology and market field that monetises and trades data. The UPCAST project is developing a series of plugins for Data Marketplaces. The UPCAST Negotiation Plugin enhances data sharing eficiency by streamlining complex negotiations, and supporting and accelerating contract management between data providers and consumers. The plugin provides a centralised platform for initiating, managing, tracking, and finalising fine-grained negotiations on various conditions, while automating routine tasks and ensuring regulatory compliance. By utilising state-of-the-art negotiation protocols, such as the IDSA Contract Negotiation Protocol, and semantic technologies, such as ODRL and DPV, the system facilitates the creation of detailed, technology-independent contracts that are both machine-readable and human-readable, presenting a substantial advancement over traditional methods.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;data consumer</kwd>
        <kwd>data contract</kwd>
        <kwd>data marketplaces</kwd>
        <kwd>data provider</kwd>
        <kwd>data sharing agreements</kwd>
        <kwd>negotiation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In the digital age, data has become a critical asset for driving innovation and enhancing
decisionmaking. Organisations increasingly rely on data to optimise their operations and maintain
a competitive edge. However, sharing and selling data over the web, or ofline, introduces
significant challenges related to compliance, security, and trust [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Addressing these
challenges requires well-structured agreements that safeguard all parties involved. Data sharing
platforms can ofer a comprehensive solution by facilitating these agreements and managing
the complexities of data exchange. Through these platforms, organisations can protect their
interests while leveraging shared data to gain insights, understand market trends, and foster
collaborative advancements [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Thus, the role of data sharing platforms in enabling efective
data exchange and collaboration is becoming increasingly vital.
      </p>
      <p>
        The Semantic Web community has concentrated on defining data usage policies, for example
through the ODRL W3C recommendation [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which focuses on defining data usage and access
control policies. However, interoperable enforcement across diferent implementations remains
a significant challenge that the community continues to address. Moreover, data sharing
agreements between data providers and consumers encompass more than just terms of use or
data usage policies; they may also require the definition and specification of the dataset to be
shared [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], information on pricing, aspects of the environmental impact of datasets, and even
details of specific data processing workflows (DPWs) that are going to process the data. To
the best of our knowledge, these features have not been addressed by any data usage policy
or negotiation framework. Furthermore, reaching an agreement requires efective and explicit
management of the negotiation steps between data providers and data consumers, followed by
both human-readable and machine-readable contract representations.
      </p>
      <p>
        Achieving a successful negotiation on these features requires employing robust and strategic
approaches. These approaches are essential to ensure fair and optimal outcomes for both data
providers and consumers, balancing interests and aligning expectations efectively [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>This paper presents the UPCAST system for negotiating and contracting data sharing
agreements, which can work as a plugin in diferent data sharing platforms and diferent marketplaces.
UPCAST facilitates data providers and consumers in negotiating dataset specifications, data
processing workflows (DPW), usage policies (ODRL), and metadata like price and environmental
impact. The system provides a centralized platform with APIs and web interfaces for managing
negotiations and contracts, ensuring compliance with regulations like General Data Protection
Regulation (GDPR)1, and handling multi-party agreements.</p>
      <p>
        Our tool extends the contract negotiation protocol defined by the
International-Data-SpacesAssociation (IDSA)2, which in turn uses the ODRL concepts of Ofer, Request and Agreement,
which we extend, enabling more descriptive and technology-independent contracts. We use the
ODRL ontology in combination with the Data Privacy Vocabulary (DPV)[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], which are used to
define metadata as well as the use, processing and purpose of processing of data under relevant
legislation, most notably GDPR. These vocabularies are utilised as standard primitives for our
contract and negotiation language available to both sides of negotiation.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. System Description and Demonstration</title>
      <p>Before a negotiation starts we assume a provider has submitted their initial dataset specification
and ODRL ofers (specifying privacy constraints) in a data marketplace; these ofers will be
available for consumers to make requests upon.</p>
      <p>Inline with A consumer initiates a negotiation by searching the available ofers. All existing
ofers are accessible to consumers through their user interface in our plugin. Upon finding an
ofer for a resource, the consumer fetches the resource specification and its corresponding ODRL
ofer. The consumer then generates a request for negotiation, which consists of: (1) changing
the resource specification of the resource, e.g., ofering a lower price or diferent environmental
requirements; (2) attaching a Data Processing Workflow (DPW) specification that describes
the consumer’s intended sequence of operations – any workflow tool can be used to generate
the consumer’s intended workflow here and we are currently implementing integration with
nextFlow3 and a proprietary system; (3) changing the ODRL usage policy (initially attached on
1https://gdpr-info.eu/
2https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/negotiation/contract.
negotiation.protocol.md
3https://www.nextflow.io/
the dataset) requesting changes on the purpose of usage, the intended actions, actors, duration
of processing, etc. Note that the values of these policies are parameterisable: we currently
use DPV and ODRL vocabularies to list these features but other ontologies, including domain
specific ones (e.g., for negotiation of data sharing in a vertical data space such as manufacturing)
is entirely possible; (4) lastly the consumer can attach a natural language “terms and conditions”
part in their request. In our system either party can also set “negotiation preferences” which
are the acceptable ranges within which they are willing to agree; these are not revealed to the
other side and can be used to support automated negotiation by use of an external agent (we
are currently developing one). In our system either party can also set “negotiation preferences”
which are the acceptable ranges within which they are willing to agree; these are not revealed
to the other side and can be used to support automated negotiation by use of an external agent
(currently in development).</p>
      <p>The provider may agree with the consumer’s request or propose a counterofer, which,
again, contains dataset specification details, a DPW pattern, ODRL usage policies, natural
language part, and their negotiation preferences. A DPW pattern defines the preferred sequence
for processing data from the provider’s side. Upon receipt of the counterofer, the consumer
continues with the same negotiation steps.</p>
      <p>If the provider is the one that agrees to the consumer’s request at some step, the consumer is
then notified and prompted to verify and sign, resulting in the establishment of an agreement.
Note that both providers and the consumers can terminate the negotiation at any step. When
the provider sends a counterofer, and the consumer is the one accepting it 4, then the provider is
notified and, again, sends an agreement to be verified and signed by the consumer. Eventually,
the verified agreement will be finalised and signed by the provider.</p>
      <p>After the agreement is finalised, a contract is issued that includes the agreed final versions of
the resource specification, DPW, ODRL usage policies and natural language terms and conditions.
Metadata such as the start date and the validation period of the contract is also added and both
parties sign it via their user interfaces. At the conference demo we will exhibit these steps
on our web-interface which is build upon an API that implements the state changes in the
negotiation process; this manages the entire negotiation process from initiation to termination
or finalisation, while the provider/consumer interfaces ofer user-friendly tools for initiating
and managing negotiations, enable both parties to propose, modify, accept, or reject terms until
they reach a mutual agreement. A video demonstrating the tool is available5.
2.1. Role of Semantic technologies
The UPCAST Negotiation Plugin uses semantic technologies like ODRL and DPV to automate
and standardise the negotiation and contracting process. ODRL provides a flexible framework
for specifying usage policies, essential for GDPR compliance, and streamlines the process by
ofering a common vocabulary, reducing inconsistencies and manual oversight. DPV further
refines data privacy descriptions, enhancing the management of sensitive data sharing. Together,
these technologies ensure clarity and consistency, minimizing conflicts and misunderstandings.
4Note that diferent terminology for the two sides such as agree, accept, or verify comes from the standardised IDSA
protocol
5https://github.com/EU-UPCAST/Demo/tree/main/Video
Additionally we are currently implementing reasoning capabilities in our policy and nogtiation
engines.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Impact</title>
      <p>We are currently implementing and evaluating the UPCAST Negotiation Plugin, using a
realworld use case of a company processing and trading complex fitness data. Our partner company
collects fitness data through devices and apps, ofering insights into health, aiding personal and
public health initiatives.</p>
      <p>We are evaluating our technology using the following metrics:
• Agreement Completion Rate: Percentage of successful contract finalizations.
• User Satisfaction: Feedback on ease of use and overall experience.
• Regulatory Compliance: Adherence to data protection regulations (e.g., GDPR).
• Impact on Data-Sharing: Changes in data-sharing behavior and agreement fairness.
At the same time, we are evaluating the following issues regarding users’ experience:
User Interface Considerations: The plugin’s user-friendly web interface guides users
through negotiation with minimal technical expertise.</p>
      <p>Potential Feedback Collection: We’ll gather feedback during pilot tests to refine the
interface, focusing on navigation, clarity, and overall satisfaction.</p>
      <p>Impact on Data-Sharing Practices: Simplifying negotiations and ensuring compliance,
the plugin aims to foster a collaborative environment, encouraging broader data-sharing and
improving decision-making across sectors.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>The UPCAST Negotiation and Contracting system ofers a promising approach to managing
data-sharing agreements by integrating state-of-the-art negotiation protocols with semantic
technologies, using generic or domain-specific vocabularies to streamline the negotiation,
agreement and contracting process and present human and machine-readable automated contracts.
By demonstrating how semantic technologies like ODRL and DPV can be applied in practical
data-sharing scenarios, this work contributes valuable insights into the future development of
data marketplaces and the broader Semantic Web ecosystem.</p>
      <p>Ongoing improvements include advanced reasoning engines for conflict resolution,
domainspecific ontologies for specialized sectors, and semantic matching algorithms to optimise
negotiation strategies based on past agreements.</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 (101093216101093216) and RAISE (101093216101058479).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>C.</given-names>
            <surname>Caimi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gambardella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Manea</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Petrocchi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Stella</surname>
          </string-name>
          ,
          <article-title>Legal and technical perspectives in data sharing agreements definition</article-title>
          ,
          <source>in: Annual Privacy Forum</source>
          , Springer,
          <year>2015</year>
          , pp.
          <fpage>178</fpage>
          -
          <lpage>192</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Byabazaire</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. O</given-names>
            <surname>'Hare</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Delaney</surname>
          </string-name>
          ,
          <article-title>Data quality and trust: Review of challenges and opportunities for data sharing in iot</article-title>
          ,
          <source>Electronics</source>
          <volume>9</volume>
          (
          <year>2020</year>
          ). URL: https://www.mdpi.com/ 2079-9292/9/12/2083. doi:
          <volume>10</volume>
          .3390/electronics9122083.
        </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>Schweihof</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Dahms</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Möller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Otto</surname>
          </string-name>
          ,
          <article-title>Data sharing fundamentals: characteristics and definition</article-title>
          ,
          <source>in: Proceedings of the 56th Hawaii International Conference on System Sciences</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <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="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <article-title>Dsap: Data sharing agreement privacy ontology</article-title>
          ,
          <source>Ph.D. thesis</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Fatima</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kraus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wooldridge</surname>
          </string-name>
          , Principles of automated negotiation, Cambridge University Press,
          <year>2014</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</article-title>
          , arXiv preprint arXiv:
          <volume>2404</volume>
          .13426 (
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>