1 of 33

15/09/2022

Modelling Business Agreements in the Multimodal Transportation Domain through Ontological Smart Contracts

Mario Scrocca, Marco Comerio,

Alessio Carenini and Irene Celino

mario.scrocca@cefriel.com

{marco.comerio,alessio.carenini,irene.celino}@cefriel.com

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

2 of 33

Multimodal Transportation

2

Icons from Flaticon

A wide set of stakeholders

should cooperate

to provide passengers with a seamless travel experience

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

3 of 33

Multimodal Transportation

3

Icons from Flaticon

https://rail-research.europa.eu/research-development/ip4/

IP4 Interoperability

Framework

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

4 of 33

Multimodal Transportation

4

Icons from Flaticon

https://w3id.org/mobility

IP4 modular suite

of ontologies

OSDM

GTFS-RT

TRIAS

Transmodel

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

5 of 33

Ride2Rail: introducing

ride-sharing in the IP4 ecosystem

Encourage ride-sharing (and carpooling) as complementary for public transport to reduce road congestion and environmental impact reinforcing the mobility offer in rural and low-demand areas
How?

Framework for combined flexible and scheduled transport services
Multimodal and integrated travel planning, booking, ticketing features
Four demonstration sites: Athens, Brno, Helsinki, Padua
Recommendations for replicability

5

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

6 of 33

Integrating Ride-sharing and Multimodal Transportation

6

Icons from Flaticon

IP4 Interoperability

Framework

?

How to integrate drivers offering rides to passengers

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

7 of 33

Integrating Ride-sharing and Multimodal Transportation

7

Icons from Flaticon

Crowd-based

Travel Expert

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

8 of 33

Integrating Ride-sharing and Multimodal Transportation

8

Icons from Flaticon

How to guarantee trust in a multi-stakeholder scenario (companies and private actors) involving the definition of business agreements?

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

9 of 33

Agreement Ledger Module: a blockchain-based solution

9

Icons from Flaticon

Description of the module (link)

Software module for the definition of business agreements as smart contracts implementing self-executing logic on the blockchain

Agreement

Ledger Module

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

10 of 33

Business Agreements in Ride2Rail

10

Icons from Flaticon

Description of the module (link)

Agreement

Ledger Module

The Ridesharing Booking, as an agreement between a driver and a passenger.

The Incentive, as an agreement between different parties to grant, according to a set of conditions, a reward that could promote more sustainable transportation alternatives.

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

11 of 33

Interoperability for the Agreement Ledger Module

11

Icons from Flaticon

Agreement

Ledger Module

Interoperability Framework

How to guarantee interoperability of the business agreements defined in the Agreement Ledger Module?

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

12 of 33

Business Agreements in Ride2Rail

The Ride2Rail Ontology for Agreements aims at identifying a set of classes and properties to represent the agreements between parties implemented through the Agreement Ledger Module.

12

Icons from Flaticon

IP4 modular suite

of ontologies

Ontology for Agreements

Agreement

Ledger Module

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

13 of 33

Blockchain and Semantic Web

Different approaches combining these two areas are reported in the literature. J. Cano-Benito et al. discuss six different scenarios based on the definition of ontologies to model the content of the blockchain.

In Ride2Rail, we were interested in investigating how smart contracts implemented on the blockchain could be described using an ontology.

13

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

14 of 33

Blockchain and Semantic Web

This approach addresses two interoperability needs:

the adoption of proper and shared terminology to describe domain entities and their relationships
the description in an implementation-independent way of the smart contracts defined according to a specific blockchain-based solution

14

Ontology for Agreements

Ethereum

Smart Contracts

Hyperledger

Smart Contracts

…

IP4 modular suite

of ontologies

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

15 of 33

Linked Open Terms Methodology

15

Domain Analysis

Competency Questions and Facts

Requirements

Existing Data Flows

Competency Questions

Use Cases

User Stories

Facts

Ontology

Requirements Specification

Requirements.docx
Fact.xlsx
Competency Question.xlsx

Validated with

domain experts

https://lot.linkeddata.es/

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

16 of 33

Our Approach

Support an ontological representation of smart contracts in a specific domain so that different stakeholders can access through uniform terminology a description of the smart contracts:

16

Investigation of the business agreements to be modelled in the considered scenario (use cases and user stories)

Analysis of the domain terminology covered by the business agreements (facts and competency questions)

Identification of existing vocabularies covering the relevant domain entities and relationships, and/or implementation of an ontology supporting their representation

Modelling of each business agreement as an ontological smart contract identifying the involved entities and the terms of the agreement

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

17 of 33

Use Cases

UC1 – Dispute Resolution about Ridesharing

Description: in case of a dispute between a driver and a passenger regarding a booked ride, the responsible authority wants to access trusted data to resolve it.

Stakeholders: Driver, Passenger, Authority

Workflow: The responsible authority analyses the details of the booking agreement between

the driver and the passenger obtaining trusted information that can help in solving the dispute.

UC2 – Incentives to promote Ridesharing

Description: travellers (both drivers and passengers) are given incentives to involve ridesharing

in their multimodal rides.

Stakeholders: Passenger, Driver, Travel Service Provider

Workflow: Incentives are represented as ontological smart contracts and can be queried to get information about the conditions and mechanisms of available incentives within IP4.

17

Icons from Flaticon

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

18 of 33

Competency Questions

18

https://chowlk.linkeddata.es/

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

19 of 33

Don't reinvent the wheel: Ontological Smart Contracts

Ontological Smart Contracts [1] are defined in the OASIS ontology for agents, systems, and integration of services.

The proposed ontology defines the concept of a smart contract as an entity to define agreements between agents and specify their terms, independently from the specific blockchain implementation.

19

oasis:ConditionalSet

Conditional

Conditional Body

Conditional Head

Conditional Atom

Subject

Object

Operator (w/ Argument)

Input/Output Parameter

oasis:SmartContract

oasis:SmartContractEntry

Participant

Value

Entry Template

refersAsNewTo

refersExactlyTo

[1] Cantone D et al., Ontological Smart Contracts in OASIS: Ontology for Agents, Systems, and Integration of Services.

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

20 of 33

Our implementation

20

Ride2Rail Ontology for Agreements

Ride2Rail Agreements

The Ride2Rail Ontology for Agreements and the modelled agreements were designed using the Chowlk notation and implemented leveraging the automatic conversion to OWL (+ manual editing)

Identifies relevant domain terminology from IP4 ontologies
Extends IP4 ontologies considering terminology introduced by Ride2Rail
Extends the OASIS ontology to define classes and properties in the considered domain

Exemplify the usage of the defined Ride2Rail Ontology for Agreements through the RDF representation of the business agreements implemented through the Agreement Ledger Module in the Ride2Rail project, i.e., the ridesharing booking and the incentives.

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

21 of 33

Ride2Rail Ontology for Agreements

The ontology is published online following best practices at https://w3id.org/ride2rail/terms# (r2r: prefix) 🡪 permanent identifier, content negotiation, human-readable documentation
The SKOS taxonomy for ridesharing booking events is published at https://w3id.org/ride2rail/rb-events# (rbe: prefix) using a similar approach.
All the material related to the ontology and the artifacts produced during the ontology engineering process are hosted on Github under the Ride2Rail organisation in the repository https://github.com/Ride2Rail/agreement-ledger-ontology
The RDF dataset containing the Ride2Rail Agreements is published at https://w3id.org/ride2rail/agreements# (ag: prefix)

A Chowlk diagram is provided in the ontology documentation for each oasis:SmartContract

21

Ontology for Agreements

Ride2Rail Agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

22 of 33

Ride2Rail Ontology for Agreements

22

https://chowlk.linkeddata.es/

Ontology for Agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

23 of 33

Ride2Rail Ontology for Agreements

23

https://chowlk.linkeddata.es/

Ontology for Agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

24 of 33

Ride2Rail Ontology for Agreements

24

https://chowlk.linkeddata.es/

Ontology for Agreements

Lesson learnt:

Chowlk is not a proper solution for SKOS taxonomies!

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

25 of 33

Ride2Rail Ontology for Agreements

25

https://chowlk.linkeddata.es/

Ontology for Agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

26 of 33

Ride2Rail Ontology for Agreements

26

https://chowlk.linkeddata.es/

Ontology for Agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

27 of 33

Ridesharing Booking Smart Contract

27

https://chowlk.linkeddata.es/

Ride2Rail Agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

28 of 33

Ridesharing Booking Smart Contract

28

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

29 of 33

Examples of Conditionals

29

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

30 of 33

Incentives Smart Contracts

30

https://github.com/Ride2Rail/agreement-ledger-ontology/tree/main/agreements

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

31 of 33

Conclusions

31

In an ecosystem comprehending various stakeholders, the implementation of business agreements through a distributed ledger provides:

several benefits regarding information trust and the automatic execution of the agreed terms modelled as smart contracts
no guarantee about the interoperability of the defined agreements from a technological and semantic perspective.

The domain terminology shared among the involved stakeholders should be referenced by the modelled entities an other software systems can benefit from a machine-readable representation of the agreements in an implementation independent way

The concept of ontological smart contract, defined in the OASIS ontology, supports the representation of business agreements independently from their implementation and relying on standardised vocabularies.

The approach proposed in this paper can be generalized to address business agreements in different domains

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

32 of 33

Conclusions

32

The defined Ride2Rail Ontology for Agreements enables the application of this concept to support the interoperability of business agreements in the multimodal transportation scenario considered by the Ride2Rail project

We validated and exemplified the usage of the ontology by modelling the specific business agreements implemented in the project on the ledger.

Future work

Materialisation/virtualisation of smart contracts instances stored on the blockchain
Exploitation of the obtained knowledge graph
Extend the scope of the defined ontology to enable the representation of heterogeneous agreements in the multimodal transportation domain, for example, considering requirements for the sharing and electric mobility

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2

33 of 33

33

Thank you

for your attention!

MARIO SCROCCA

Knowledge Technologies

Cefriel

marioscrocca

@mario_scrock

mario.scrocca@cefriel.com

0 32 96

255 220 6

47 60 182

0 83 255

40 130 255

94 170 240

166 199 240

91 101 135

0 32 96

42 212 138

255 181 6

#1

#2

#3

#4

#5

50 172 189

64 211 204

104 235 228

157 240 234

214 240 235

#1

#2

#3

#4

#5

Primary

5

3

1

4

2

5

3

1

4

2

GRAPHS

TEXT

Sequence of use

CEFRIEL IDENTITY

Secondary

RAG

255 255 255

0 32 96

BACKGROUND

255 40 78

255 220 6

Highlight

00 00 00

Text

Title 1

Title 2