<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Data Sharing Negotiation and Contracting</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Semih</forename><surname>Yumusak</surname></persName>
							<email>semih.yumusak@soton.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Electronics and Computer Science</orgName>
								<orgName type="institution">University of Southampton</orgName>
								<address>
									<settlement>Southampton</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Soulmaz</forename><surname>Gheisari</surname></persName>
							<email>s.gheisari@soton.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Electronics and Computer Science</orgName>
								<orgName type="institution">University of Southampton</orgName>
								<address>
									<settlement>Southampton</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jaime</forename><forename type="middle">Osvaldo</forename><surname>Salas</surname></persName>
							<email>j.o.salas@soton.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Electronics and Computer Science</orgName>
								<orgName type="institution">University of Southampton</orgName>
								<address>
									<settlement>Southampton</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Syed</forename><forename type="middle">Atif</forename><surname>Moqurrab</surname></persName>
							<email>s.a.moqurrab@soton.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Electronics and Computer Science</orgName>
								<orgName type="institution">University of Southampton</orgName>
								<address>
									<settlement>Southampton</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Luis-Daniel</forename><surname>Ibáñez</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Department of Electronics and Computer Science</orgName>
								<orgName type="institution">University of Southampton</orgName>
								<address>
									<settlement>Southampton</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">George</forename><surname>Konstantinidis</surname></persName>
							<email>g.konstantinidis@soton.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Electronics and Computer Science</orgName>
								<orgName type="institution">University of Southampton</orgName>
								<address>
									<settlement>Southampton</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Data Sharing Negotiation and Contracting</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">01B144FF2EB12AFBE439297E0E8C3153</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T16:48+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>data consumer, data contract, data marketplaces, data provider, data sharing agreements, negotiation 0000-0002-8878-4991 (S. Yumusak)</term>
					<term>0000-0001-8974-2841 (S. Gheisari)</term>
					<term>0000-0002-9353-8955 (J. O. Salas)</term>
					<term>0000-0002-8645-6687 (S. A. Moqurrab)</term>
					<term>0000-0001-6993-0001 (L. Ibáñez)</term>
					<term>0000-0002-3962-9303 (G. Konstantinidis)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><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 efficiency 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></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><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 offline, introduces significant challenges related to compliance, security, and trust <ref type="bibr" target="#b0">[1]</ref>  <ref type="bibr" target="#b1">[2]</ref>. Addressing these challenges requires well-structured agreements that safeguard all parties involved. Data sharing platforms can offer 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 <ref type="bibr" target="#b2">[3]</ref>. Thus, the role of data sharing platforms in enabling effective 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 <ref type="bibr" target="#b3">[4]</ref>, which focuses on defining data usage and access control policies. However, interoperable enforcement across different 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 <ref type="bibr" target="#b4">[5]</ref>, 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 effective 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 effectively <ref type="bibr" target="#b5">[6]</ref>.</p><p>This paper presents the UPCAST system for negotiating and contracting data sharing agreements, which can work as a plugin in different data sharing platforms and different 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) <ref type="foot" target="#foot_0">1</ref> , and handling multi-party agreements.</p><p>Our tool extends the contract negotiation protocol defined by the International-Data-Spaces-Association (IDSA) <ref type="foot" target="#foot_1">2</ref> , which in turn uses the ODRL concepts of Offer, 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) <ref type="bibr" target="#b6">[7]</ref>, 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">System Description and Demonstration</head><p>Before a negotiation starts we assume a provider has submitted their initial dataset specification and ODRL offers (specifying privacy constraints) in a data marketplace; these offers will be available for consumers to make requests upon.</p><p>Inline with A consumer initiates a negotiation by searching the available offers. All existing offers are accessible to consumers through their user interface in our plugin. Upon finding an offer for a resource, the consumer fetches the resource specification and its corresponding ODRL offer. The consumer then generates a request for negotiation, which consists of: (1) changing the resource specification of the resource, e.g., offering a lower price or different 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 nextFlow 3 and a proprietary system; (3) changing the ODRL usage policy (initially attached on 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 counteroffer, 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 counteroffer, 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 counteroffer, and the consumer is the one accepting it <ref type="foot" target="#foot_3">4</ref> , 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 offer 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 available<ref type="foot" target="#foot_4">5</ref> .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1.">Role of Semantic technologies</head><p>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 offering 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.</p><p>Additionally we are currently implementing reasoning capabilities in our policy and nogtiation engines.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Impact</head><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, offering insights into health, aiding personal and public health initiatives.</p><p>We are evaluating our technology using the following metrics:</p><p>• Agreement Completion Rate: Percentage of successful contract finalizations.</p><p>• User Satisfaction: Feedback on ease of use and overall experience.</p><p>• Regulatory Compliance: Adherence to data protection regulations (e.g., GDPR).</p><p>• Impact on Data-Sharing: Changes in data-sharing behavior and agreement fairness.</p><p>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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Conclusion</head><p>The UPCAST Negotiation and Contracting system offers 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></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://gdpr-info.eu/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/negotiation/contract. negotiation.protocol.md</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://www.nextflow.io/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">Note that different terminology for the two sides such as agree, accept, or verify comes from the standardised IDSA protocol</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">https://github.com/EU-UPCAST/Demo/tree/main/Video</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>This work was funded by the UKRI Horizon Europe guarantee funding scheme for the Horizon Europe projects UPCAST (101093216101093216) and RAISE (101093216101058479).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Legal and technical perspectives in data sharing agreements definition</title>
		<author>
			<persName><forename type="first">C</forename><surname>Caimi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Gambardella</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Manea</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Petrocchi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Stella</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Annual Privacy Forum</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="178" to="192" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Data quality and trust: Review of challenges and opportunities for data sharing in iot</title>
		<author>
			<persName><forename type="first">J</forename><surname>Byabazaire</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>O'hare</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Delaney</surname></persName>
		</author>
		<idno type="DOI">10.3390/electronics9122083</idno>
		<ptr target="https://www.mdpi.com/2079-9292/9/12/2083.doi:10.3390/electronics9122083" />
	</analytic>
	<monogr>
		<title level="j">Electronics</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Data sharing fundamentals: characteristics and definition</title>
		<author>
			<persName><forename type="first">I</forename><surname>Jussen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Schweihoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Dahms</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Möller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Otto</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 56th Hawaii International Conference on System Sciences</title>
				<meeting>the 56th Hawaii International Conference on System Sciences</meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Ianella</surname></persName>
		</author>
		<title level="m">Open digital rights language (odrl), Open Content Licensing: Cultivating the Creative Commons</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Li</surname></persName>
		</author>
		<title level="m">Dsap: Data sharing agreement privacy ontology</title>
				<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
	<note>Ph.D. thesis</note>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Fatima</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kraus</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Wooldridge</surname></persName>
		</author>
		<title level="m">Principles of automated negotiation</title>
				<imprint>
			<publisher>Cambridge University Press</publisher>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">J</forename><surname>Pandit</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Esteves</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">P</forename><surname>Krog</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Ryan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Golpayegani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Flake</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2404.13426</idno>
		<title level="m">Data privacy vocabulary (dpv)-version 2</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
