<?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">Legal Design through Business Process Model and Notation (BPMN): a Digital Services Act Case-Study</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Davide</forename><surname>Audrito</surname></persName>
							<email>davide.audrito2@unibo.it</email>
							<affiliation key="aff0">
								<orgName type="department">Legal Studies Department</orgName>
								<orgName type="institution">University of Bologna</orgName>
								<address>
									<addrLine>Via Zamboni 27</addrLine>
									<postCode>40126</postCode>
									<settlement>Bologna</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Andrea</forename><forename type="middle">Filippo</forename><surname>Ferraris</surname></persName>
							<email>andreafilippo.ferraris@unito.it</email>
							<affiliation key="aff1">
								<orgName type="department">Law Department</orgName>
								<orgName type="institution">University of Turin</orgName>
								<address>
									<addrLine>Lungo Dora Siena 100/A</addrLine>
									<postCode>10154</postCode>
									<settlement>Torino</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff2">
								<address>
									<settlement>Sherbrooke</settlement>
									<region>Québec</region>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Legal Design through Business Process Model and Notation (BPMN): a Digital Services Act Case-Study</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">7C19A9CC5D5CE75ECA5E1A8EC6F7498A</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T19:27+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>Legal Design</term>
					<term>Legal Compliance</term>
					<term>Business Process Model and Notation</term>
					<term>Digital Services Act</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Legal Design represents a well-rooted research area at the crossroads of law, design and computer-science, which plays a significant role in the clarification and accessibility of legal sources. This research work shows that legal design fosters the ability of economic operators, including private citizens, public administrations and companies, to conform to manifold legislative requirements arising from multilevel legal orders. To achieve this objective, we rely on the Business Process Model and Notation (BPMN) standard to represent a core provision of the so-called Digital Services Act (DSA). Building on a preliminary first-stage research work, we model a second normative requirement of the DSA with a view to showcase the potential role of BPMN in legal education.</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>The principle of normativity posits that legal norms emerge from a legitimate process orchestrated by authorized entities. Such laws are targeted towards one or several agents, often denoted as personas, who can assimilate the normative content and freely elect to conform to or defy the prescribed regulations <ref type="bibr" target="#b10">[12]</ref>, a notion underpinned by the principle of self-determination <ref type="bibr" target="#b15">[17]</ref>. Nevertheless, complications surface when individual actors, whether natural or legal entities, lack genuine comprehension of the obligations imposed by law. This can largely be attributed to the intricacies of legal jargon, colloquially termed "legalese", recognized for its complexity, verbosity, and extreme specificity <ref type="bibr" target="#b2">[4]</ref>.</p><p>Conversely, visual representation possesses the potential to enrich comprehension and understanding of intricate legal notions <ref type="bibr" target="#b13">[15]</ref>. By harnessing the capacity of legal design methods, instruments, doctrines, and visual illustrations, we stand to enhance the conveyance of legal information and foster superior interactions between citizens and legal frameworks.</p><p>For the efficacy of the legal design methodology, it is imperative to maintain uniformity across legal knowledge, graphical depictions, textual representation, and design attributes. As such, it becomes crucial to confirm that legal design models adhere to the principles of normativity <ref type="bibr" target="#b14">[16]</ref> and explicability <ref type="bibr" target="#b7">[9]</ref>, thereby ensuring the effective dissemination and comprehension of legal norms.</p><p>Building on the principle of normativity, our research aims to model the provisions outlined in Regulation (EU) 2022/2065, also known as the Digital Services Act (DSA). This regulation was adopted in October 2022 and will come into effect in early 2024 (see Section 3). Our objective is to reframe the normative contents of the DSA using the Business Process Model and Notation (BPMN) standard. This will help providers of intermediary services (PISs), or personas, understand and comply with the new obligations. Our research work demonstrates that legal design methods such as BPMN are valuable in facilitating the transmission of legal information without the risk of misleading non-experts by neglecting the principle of normativity.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Relevant Work</head><p>Legal informatics is engaged with Artificial Intelligence techniques <ref type="bibr" target="#b22">[23]</ref>, network analysis <ref type="bibr" target="#b18">[20,</ref><ref type="bibr" target="#b21">22]</ref>, ontologies <ref type="bibr" target="#b0">[2]</ref>, and other research areas. The legal design methodology has been rising over the last decades, both on the side of theoretical studies <ref type="bibr" target="#b17">[19,</ref><ref type="bibr" target="#b5">7]</ref> and in the framework of applied works and projects <ref type="bibr" target="#b4">[6,</ref><ref type="bibr" target="#b6">8]</ref>, so that nowadays it can be considered an autonomous discipline.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1.">Legal Design</head><p>Today's complex and constantly evolving regulatory landscape presents significant challenges for businesses, with a wide array of intricate legal obligations often leading to confusion, noncompliance, and possible legal repercussions. However, the use of legal design principles and visualization techniques offers a promising solution by enhancing businesses' grasp of their legal duties and guiding them more efficiently <ref type="bibr" target="#b23">[24,</ref><ref type="bibr" target="#b8">10]</ref>.</p><p>Margaret Hagan defines legal design as a user-oriented approach to the legal field, aiming to create more accessible, efficient, and satisfying legal systems and services <ref type="bibr" target="#b9">[11]</ref>. This is achieved through a combination of legal design methods, tools, and visual aids that improve the transmission of legal information and facilitate smoother interactions between people and the legal systems they engage with.</p><p>A striking example of legal design's potential to effect change and promote social justice can be seen in the work of Candy Chang with The Street Vendor Project and the Center for Urban Pedagogy. Their pioneering guide, "Vendor Power" <ref type="bibr" target="#b24">[25]</ref>, shows how legal design can simplify complex legal rules into easy-to-understand visual diagrams for street vendors. The guide, available in several languages, helps vendors better understand their rights and comply with relevant laws more easily.</p><p>Furthermore, the inclusion of personal stories in the guide highlights the crucial role of community engagement in legal design initiatives <ref type="bibr" target="#b1">[3]</ref>. This holistic approach not only increases the accessibility of legal information but also fosters a sense of inclusivity and empowers people to actively participate in shaping the legal frameworks that directly affect their lives.</p><p>In Finland, legal design has been strategically employed by the Finland Arbitration Institute (FAI), in collaboration with Dottir Attorneys and design agency Hellon. They have created an interactive FAI Arbitration Process flowchart, transforming complex arbitration procedures into understandable, usable information, thereby promoting transparency and boosting user engagement. The joint project demonstrates how legal design can enable clearer communication in the legal sphere, promote innovative problem-solving, and emphasize a more user-centered approach.</p><p>Legal design, through its user-friendly visual aids and effective storytelling, serves as a critical tool in bridging the gap between the complexities of legal requirements and people's ability to proficiently navigate them <ref type="bibr" target="#b23">[24,</ref><ref type="bibr" target="#b8">10]</ref>. This contributes to a more equal and inclusive society.</p><p>By converting complex legal rules into simple, accessible visual diagrams, legal design gives businesses a clear, comprehensive view of their regulatory environment. This clarity promotes a deeper understanding of industry-specific legal requirements, reducing confusion and lowering the risk of non-compliance <ref type="bibr" target="#b20">[21]</ref>. Presenting information in multiple languages ensures that legal design remains inclusive and accessible to businesses operating in diverse contexts and global markets <ref type="bibr" target="#b16">[18]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">Business Process Model and Notation (BPMN) for Law</head><p>The use of the BPMN standard has proven to be highly effective in modeling legal knowledge, tasks, and processes <ref type="bibr" target="#b3">[5]</ref>. By visually representing business workflows, BPMN helps businesses gain a better understanding of their operations and identify areas for improvement <ref type="bibr" target="#b12">[14]</ref>. Legal professionals have embraced BPMN to illustrate various legal processes, including contract review and approval workflows.</p><p>However, relying solely on BPMN may not fully address the challenge of making legal compliance more accessible for businesses. To overcome this limitation, the integration of legal design principles is key. Legal design complements BPMN by providing visually intuitive representations of legal rules and requirements in a user-friendly format.</p><p>Through the application of legal design, legal professionals can create clear and easily understandable visualizations of legal processes and obligations. This enables businesses to grasp their regulatory responsibilities more effectively and take the necessary steps to comply. By incorporating design principles that prioritize clarity and accessibility, legal design enhances the usability of legal information for businesses.</p><p>The combination of BPMN and legal design offers a comprehensive approach to legal compliance. By leveraging the insights provided by BPMN and the user-centric approach of legal design, businesses can gain a holistic understanding of their legal requirements. This empowers them to identify potential gaps in their processes and proactively ensure compliance.</p><p>Ultimately, the integration of BPMN and legal design enables businesses to navigate the regulatory landscape with greater ease. By enhancing clarity and accessibility, businesses can minimize the risk of non-compliance and confidently adhere to legal obligations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Methodology</head><p>The Digital Services Act (DSA) establishes a single market for digital services by enshrining clear responsibilities and accountability for providers of intermediary services (PISs), including social media, e-commerce platforms, very large online platforms (VLOPs) and very large online search engines (VLOSEs).</p><p>In order to improve the understandability of the obligations enshrined in the DSA and addressed to PISs, we have built on the legal design methodological framework outlined in a preliminary research article[1]:</p><p>1. Legal analysis of the textual source based on the theory of law and, where applicable, the philosophy of law and related disciplines. 2. Application of the Business Process Model and Notation (BPMN) standard for the formalization of legal knowledge. This method improves the visualization and explainability of legal processes, while ensuring the machine-readability of the output file, i.e. in XML format. The BPMN standard was implemented through the freely available editor BPMN.iO<ref type="foot" target="#foot_0">1</ref> . 3. Interpretation of the results, possibly assessed empirically and with different methods, including indexes and questionnaires.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Results</head><p>In this section, we show the results of this second-stage research work. Besides the modelling of the normative contents enshrined in Article 14, we showcase the BPMN representation of a second normative requirement, namely Article 10 DSA.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Legal Analysis of the Text Sources</head><p>The Digital Services Act (DSA), adopted on November 16, 2022, represents a significant milestone in Information Society Services liability. It is a progressive update to the regulatory framework established by the European Union directive 31/2000, also known as the e-commerce directive. This self-executing regulation has direct and binding authority over EU individuals, companies, and member states in relation to their respective domains. Article 14 of the DSA focuses on the requirements imposed on providers of intermediary services (PISs) when formulating the terms and conditions of their services. While the DSA contains various provisions, Article 14 stands out as it specifically addresses the criteria that apply to PISs in their contractual arrangements. Therefore, this article is a relevant benchmark for the application of legal design using the Business Process Model and Notation (BPMN) methodology, considering its wording and implications.</p><p>Indeed, Article 14 DSA entirely relies on the use of "shall", which is the deontic operator for obligations. To show the complexity of the provision, the paragraphs thereof that are suitable for the BPMN representation are quoted below:</p><p>Terms and Conditions 1. Providers of intermediary services shall include information on any restrictions that they impose in relation to the use of their service in respect of information provided by the recipients of the service, in their terms and conditions. That information shall include information on any policies, procedures, measures and tools used for the purpose of content moderation, including algorithmic decisionmaking and human review, as well as the rules of procedure of their internal complaint handling system. It shall be set out in clear, plain, intelligible, userfriendly and unambiguous language, and shall be publicly available in an easily accessible and machine-readable format. [...] 3. Where an intermediary service is primarily directed at minors or is predominantly used by them, the provider of that intermediary service shall explain the conditions for, and any restrictions on, the use of the service in a way that minors can understand. [...] 5. Providers of very large online platforms and of very large online search engines shall provide recipients of services with a concise, easily-accessible and machinereadable summary of the terms and conditions, including the available remedies and redress mechanisms, in clear and unambiguous language.</p><p>6. Very large online platforms and very large online search engines within the meaning of Article 33 shall publish their terms and conditions in the official languages of all the Member States in which they offer their services.</p><p>The text contains lengthy sentences with consecutive direct objects, such as policies, procedures, measures, and tools. We focus on requirements that can be met with a "standard solution" for autonomous compliance. For instance, Article 14(1) of the DSA states that providers of intermediary services must include recipient-imposed restrictions in their terms and conditions. By incorporating the necessary information, PISs fulfill this requirement. In contrast, Article 14(4) of the DSA mandates diligent, objective, and proportionate behavior for PISs, which falls outside our scope.</p><p>While Article 14 DSA addresses the requirements imposed on PISs when formulating the terms and conditions of their services, Article 10 enshrines the obligations to provide information upon receipt of orders issued by the competent public authorities. The following paragraphs of Article 10 are suitable for the BPMN representation and were included in our analyisis: Orders to provide information 1. Upon receipt of an order to provide specific information about one or more specific individual recipients of the service, issued by the relevant national judicial or administrative authorities on the basis of the applicable Union law or national law in compliance with Union law, providers of intermediary services shall, without undue delay inform the authority issuing the order, or any other authority specified in the order, of its receipt and of the effect given to the order, specifying if and when effect was given to the order. 5. At the latest when effect is given to the order, or, where applicable, at the time provided by the issuing authority in its order, providers of intermediary services shall inform the recipient of the service concerned of the order received and the effect given to it. Such information provided to the recipient of the service shall include a statement of reasons and the possibilities for redress that exist, in accordance with paragraph 2.</p><p>Similar to Article 14, the provisions in Article 10 are characterized by the use of lengthy sentences and convoluted wording. Once more, the text of Article 10 is grounded upon the deontic operator "shall, " which points out the occurrence of legal obligations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2.">Application of the BPMN Standard</head><p>The use of the BPMN standard simplifies the legal text and lays the foundations for a questionnaire to be replied by PISs for testing-related purposes. Figure <ref type="figure" target="#fig_1">1</ref>   The whole flowchart is contained in a "pool", which represents participants in a process, i.e. providers of intermediary services. In the pool, there are two horizontal "lanes" above and below respectively, which serve to organize and categorize activities. We use lanes as sub-pools for activities of two categories of PISs that are affected by ad hoc obligations enshrined in Article 14(3) and ( <ref type="formula">6</ref>) DSA. These categories are PISs primarily directed at or predominantly used by minors and PISs with very large platforms and very large search engines.</p><p>The process begins with a "start event", i.e. circle on the left, under the label of "Begin compliance process" and ends with an "end event", i.e. circle on the right side, under the label "End compliance test". Starting from the start event, solid lines with solid arrowheads are used to show the "sequence flow" of activities performed in the process. In turn, "activities" are indicated by rounded-corner rectangles and labelled by following the formula "verb + direct object". The forth activity from the left, i.e. publish information, is connected to an "exclusive gateway" represented by a diamond with a cross in the middle. Indeed, depending on the nature of the PISs category addressed by the obligations, activities follow one of three alternative flows towards either "shall explain" or "publish specific information" or "end event" respectively.</p><p>For our purposes, each activity, i.e. rounded-corner rectangle, is connected to an "annotation", which is one of the "artifacts" of the BPMN standard and provides additional text information for the reader of the BPMN diagram.</p><p>Figure <ref type="figure" target="#fig_2">2</ref> shows annotations of the activities "include information" and "include in information". The former activity is complemented through the description "in terms and conditions on any restrictions that they impose in relation to the use of their service in respect of information provided by the recipients of the service".</p><p>Annotations enrich activities with essential details needed to comply with the requirements and they enable the deconstruction and modelling of legal concepts. This function also allows to showcase questions for compliance-check purposes. For instance, the activity "set out information" could be integrated by the annotation "Did you set out in your terms and conditions information in clear, plain, intelligible, user-friendly and unambiguous language?". While the categories of BPMN standard elements utilized to depict the normative requirements of Article 14 are the same as those used for modeling Article 10, Figure <ref type="figure" target="#fig_3">3</ref> demonstrates that the latter provision possesses certain distinctive characteristics that warrant further discussion.</p><p>Article 10 DSA possesses a notable feature in that it initiates with an event, specifically the "receipt of an order to provide specific information about one or more specific individual recipients of the service". This means, that once the relevant public authorities require providers of intermediary services to provide specific information on individuals, who are recipients of the service, the obligations enshrined in Article 10 become effective and concrete <ref type="bibr" target="#b11">[13]</ref>. In contrast, Article 14 introduces the modeling with a non-textual and ad hoc event, namely the purpose of the representation, which is "Begin compliance test". Secondly, as the normative requirements apply to the general category of PISs, only one swimlane is necessary to indicate the scope of application ratione persone covered by the article. The structural disparities between the two examined normative provisions are resolved by the flexibility of the BPMN standard, which allows for a broader understanding of complex normative requirements, including by legal practitioners, among citizens, companies and other organizations.</p><p>In conclusion, the comprehensive suite of BPMN 2.0 symbols demonstrates its effectiveness as a method to model legal procedures and concepts. Figure <ref type="figure" target="#fig_4">4</ref> illustrates a flowchart detailing the requirements outlined in Article 20(1). Upon initiating the event, PISs are obligated to make one or more decisions based on the information provided by the recipients, particularly if it constitutes illegal content or breaches the terms and conditions of the service. For modeling purposes, an inclusive gateway is used to represent that PISs shall pick up one or multiple options among the four decisions provided by Article 20(1) of the Digital Services Act (DSA). </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusions and Future Work</head><p>This research work represents the initial stage of applying the Business Process Model and Notation (BPMN) standard as a legal design tool for the purpose of enhancing legal compliance. Moving forward, our aim is to develop a robust methodology to validate and evaluate the findings presented in this study and the final modeling of the whole text of the Digital Services Act. This can be achieved through the creation of formal ontologies in conjunction with BPMN, as they provide a structured and uniform representation of legal knowledge and requirements.</p><p>By incorporating formal ontologies into the BPMN framework, we can establish a comprehensive and semantically rich representation of legal concepts and obligations. This integration enables a more precise and detailed understanding of the legal domain, ensuring accuracy and consistency in the modeling of legal compliance requirements.</p><p>In order to effectively test the proposed approach, we plan to rely on manifold evaluation methods, including the use of indexes and questionnaires. These tools will help us assess the usability and effectiveness of the textual reformulation and graphic representations that are key components of legal design. Drawing from established best practices in the legal design literature, such as the use of bullet points, icons, pictures, and symbols, we aim to create visualizations that are intuitive, user-friendly, and conducive to promoting compliance with legal obligations.</p><p>By emphasizing the role of formal ontologies in conjunction with BPMN, our research effort contributes to the advancement of legal design as a discipline. Through the integration of these formal frameworks, we can enhance the clarity, accuracy, and comprehensibility of legal compliance requirements, facilitating businesses' understanding and adherence to regulatory obligations.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>portrays the BPMN representation of Article 14 DSA.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: The BPMN representation of Article 14 DSA</figDesc><graphic coords="6,89.29,329.18,416.71,241.72" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Examples of BPMN annotations contributing to model legal concepts</figDesc><graphic coords="7,213.06,402.99,166.67,111.74" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: The BPMN representation of Article 10 DSA</figDesc><graphic coords="8,89.29,106.52,416.69,330.63" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: The BPMN representation of Article 20(1) DSA</figDesc><graphic coords="9,150.55,106.52,291.70,396.04" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://demo.bpmn.io</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Analogical lightweight ontology of eu criminal procedural rights in judicial cooperation</title>
		<author>
			<persName><forename type="first">D</forename><surname>Audrito</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Sulis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Humphreys</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Di Caro</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence and Law</title>
		<imprint>
			<biblScope unit="page" from="1" to="24" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">From visualization to legal design: a collaborative and creative process</title>
		<author>
			<persName><forename type="first">G</forename><surname>Berger-Walliser</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">D</forename><surname>Barton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Haapio</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Am. Bus. LJ</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="page">347</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Legalese versus plain language</title>
		<author>
			<persName><forename type="first">P</forename><surname>Butt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Amicus Curiae</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="page">28</biblScope>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Business process management for legal domains: Supporting execution and management of preliminary injunctions</title>
		<author>
			<persName><forename type="first">F</forename><surname>Capuzzimati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Violato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Baldoni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Boella</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">JURIX</title>
		<imprint>
			<biblScope unit="page" from="149" to="152" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Legal design patterns for privacy</title>
		<author>
			<persName><forename type="first">Michael</forename><surname>Curtotti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">H P S</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 18th International Legal Informatics Symposium IRIS</title>
				<editor>
			<persName><forename type="first">E</forename><surname>Schweighofer</surname></persName>
		</editor>
		<meeting>the 18th International Legal Informatics Symposium IRIS</meeting>
		<imprint>
			<date type="published" when="2015">2015. 2015</date>
			<biblScope unit="page" from="455" to="462" />
		</imprint>
	</monogr>
	<note>Co-operation</note>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Legal design perspectives</title>
		<author>
			<persName><forename type="first">R</forename><surname>Ducato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Strowel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Theoretical and practical insights from the field</title>
				<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Contract as automaton: The computational representation of financial agreements</title>
		<author>
			<persName><forename type="first">M</forename><surname>Flood</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Goodenough</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">OFR Working Paper</title>
		<imprint>
			<biblScope unit="volume">15</biblScope>
			<date type="published" when="2015">03 2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Ai4people-an ethical framework for a good ai society: opportunities, risks, principles, and recommendations</title>
		<author>
			<persName><forename type="first">L</forename><surname>Floridi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Cowls</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Beltrametti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Chatila</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Chazerand</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Dignum</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Luetge</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Madelin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Pagallo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Rossi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Minds and machines</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="page" from="689" to="707" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Legal design patterns for privacy</title>
		<author>
			<persName><forename type="first">H</forename><surname>Haapio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hagan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Palmirani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rossi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Data Protection/LegalTech Proceedings of the 21st International Legal Informatics Symposium IRIS</title>
				<imprint>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="445" to="450" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Law By Design</title>
		<author>
			<persName><forename type="first">M</forename><surname>Hagan</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">L A</forename><surname>Hart</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Raz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Green</surname></persName>
		</author>
		<title level="m">The concept of law</title>
				<imprint>
			<publisher>oxford university press</publisher>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Il fondamento della validità del diritto</title>
		<author>
			<persName><forename type="first">H</forename><surname>Kelsen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Rivista di</title>
		<imprint>
			<date type="published" when="1957">1957</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Business process model and notation: The current state of affairs</title>
		<author>
			<persName><forename type="first">M</forename><surname>Kocbek Bule</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Jost</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hericko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Polančič</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computer Science and Information Systems</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="page" from="509" to="539" />
			<date type="published" when="2015-06">06. 2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Visualisation of law and legal process: An opportunity missed</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">, W L C</forename><surname>Mclachlan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information Visualization</title>
		<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">A smart legal order for the digital era: A hybrid ai and dialogic model</title>
		<author>
			<persName><forename type="first">M</forename><surname>Palmirani</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Ragion pratica</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="633" to="655" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">The justification of civil disobedience</title>
		<author>
			<persName><forename type="first">J</forename><surname>Rawls</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Arguing about law</title>
				<imprint>
			<date type="published" when="2013">2013</date>
			<biblScope unit="page" from="244" to="253" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Lynx: Towards a legal knowledge graph for multilingual europe</title>
		<author>
			<persName><forename type="first">V</forename><surname>Rodríguez-Doncel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Montiel-Ponsoda</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Law in Context</title>
		<imprint>
			<biblScope unit="volume">37</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="175" to="178" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">User interface design issues for easy and efficient human computer interaction: An explanatory approach</title>
		<author>
			<persName><forename type="first">D</forename><surname>Saha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mandal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Pal</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Computer Sciences and Engineering</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="127" to="135" />
			<date type="published" when="2015-01">01 2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<title level="m" type="main">Automated extraction and representation of citation network: A CJEU case-study</title>
		<author>
			<persName><forename type="first">G</forename><surname>Sartor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Santin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Audrito</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Sulis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">D</forename><surname>Caro</surname></persName>
		</author>
		<editor>Guizzardi, R.S.S., Neumayr, B.</editor>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title/>
		<author>
			<persName><forename type="first">Emper</forename><surname>Cmls</surname></persName>
		</author>
		<author>
			<persName><surname>Jusmod</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">LNCS</title>
		<imprint>
			<biblScope unit="volume">13650</biblScope>
			<biblScope unit="page" from="102" to="111" />
			<date type="published" when="2022">2022. 2022</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Knowledge graphs: trust, privacy, and transparency from a legal governance approach</title>
		<author>
			<persName><forename type="first">D</forename><surname>Schwabe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Laufer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Casanovas</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Law in Context</title>
		<imprint>
			<biblScope unit="volume">37</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="24" to="41" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Exploiting co-occurrence networks for classification of implicit inter-relationships in legal texts</title>
		<author>
			<persName><forename type="first">E</forename><surname>Sulis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Humphreys</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Vernero</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">A</forename><surname>Amantea</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Audrito</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">D</forename><surname>Caro</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Inf. Syst</title>
		<imprint>
			<biblScope unit="volume">106</biblScope>
			<biblScope unit="page">101821</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Exploiting textual similarity techniques in harmonization of laws</title>
		<author>
			<persName><forename type="first">E</forename><surname>Sulis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">B</forename><surname>Humphreys</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Audrito</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">D</forename><surname>Caro</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">AIxIA 2021</title>
				<editor>et al., S.B.</editor>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2021">2021</date>
			<biblScope unit="volume">13196</biblScope>
			<biblScope unit="page" from="185" to="197" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">Privacy, notice, and design</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">E</forename><surname>Waldman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">STANFORD TECHNOLOGY LAW REVIEW</title>
		<imprint>
			<biblScope unit="volume">21</biblScope>
			<biblScope unit="page">129</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<monogr>
		<title level="m" type="main">Legal design: New thinking and new challenges</title>
		<author>
			<persName><forename type="first">R</forename><surname>Yankovskiy</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="volume">76</biblScope>
		</imprint>
	</monogr>
</biblStruct>

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