-
Notifications
You must be signed in to change notification settings - Fork 2
/
conceptual_model.html
129 lines (123 loc) · 9.04 KB
/
conceptual_model.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
<!DOCTYPE html>
<html lang="en" style="scroll-behavior:smooth;">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
<meta name="description" content="" />
<meta name="author" content="" />
<title>THE BLOODY CHAMBER - Conceptual Model</title>
<link rel="icon" type="image/x-icon" href="/img/icon2.png" />
<link href="../css/styles.css" rel="stylesheet" />
</head>
<body id="page-top">
<nav class="navbar navbar-expand-lg navbar-light fixed-top" id="mainNav">
<div class="container">
<img src="/img/icon.png" height="60px" class="d-inline-block align-top" alt="" style="padding:10px;">
<a class="navbar-brand js-scroll-trigger" href="../index.html" style="color:#b41010 !important;">
the bLODy chamber</a>
<button class="navbar-toggler navbar-toggler-right" type="button" data-toggle="collapse"
data-target="#navbarResponsive" aria-controls="navbarResponsive" aria-expanded="false"
aria-label="Toggle navigation" id="menu">
Menu
<i class="fas fa-bars"></i>
</button>
<div class="collapse navbar-collapse" id="navbarResponsive">
<ul class="navbar-nav ml-auto">
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdownMenuLink" role="button"
data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"
style="color:#b41010 !important;">Knowledge Organization</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdownMenuLink">
<a class="dropdown-item js-scroll-trigger" href="/er_model.html">Conceptual Map and
E/R Model</a>
<a class="dropdown-item" href="/metadata.html">Metadata Analysis</a>
<a class="dropdown-item" href="/metadata.html#metadata2">Metadata Alignment</a>
<a class="dropdown-item" href="/theoretical_model.html">Theoretical model</a>
<a class="dropdown-item" href="/er_model_enhanced.html">Enhanced E/R Model</a>
<a class="dropdown-item" href="/conceptual_model.html">Conceptual Model</a>
</div>
</li>
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdownMenuLink" role="button"
data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"
style="color:#b41010 !important;">Knowledge Representation</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdownMenuLink">
<a class="dropdown-item js-scroll-trigger" href="/data.html">Data Creation</a>
<a class="dropdown-item" href="/rdf.html">RDF Production</a>
<a class="dropdown-item" href="/rdf.html#rdf2">RDF Visualization </a>
</div>
</li>
</ul>
</div>
</div>
</nav>
<section class="projects-section" id="items2" style="padding:6rem 0 0rem;">
<div class="container">
<div class="row align-items-center no-gutters mb-4 mb-lg-5">
<div class="col-xl-12 text-left" id="projt">
<h1 class="text-dark mb-4">Conceptual Model</h1>
</div>
<div class="col-xl-12 text-left">
<p>After developing a theoretical model, the next step was to move towards a formal representation of
the domain using an ontological approach. This involves creating a conceptual model by reusing
existing schemas, vocabularies, and ontologies. To ensure coherence and consistency, it is
essential to replace the terms of the theoretical model with those taken from existing models.
The main ontology chosen in this step of the project were the following: <br>
<ul style="text-align:justify">
<li><strong>Schema.org</strong>, an ontology that covers a wide range of topics, including
businesses, events, people, products, places, and organizations. It is designed to be
compatible with existing standards and technologies, such as RDFa and JSON-LD. It is
continually evolving and being updated based on community feedback and emerging trends in
data modelling and web development, so we were able to find in Schema fitting classes and properties to describe various objects and relationships in our domain.</li>
<li><strong>FABIO</strong> ontology, that is aligned with the FRBR (Functional Requirements for
Bibliographic Records) model and is designed to represent bibliographic information, namely
the description of bibliographic entities like books, articles, and journals, as well as
relationships between these entities; it was particularly useful for us in order to describe the short stories included in "The Bloody Chamber".</li>
<li><strong>CIDOC-CRM</strong>, an ontology that describes cultural heritage information. It
provides a high-level conceptual framework for modelling objects, events, agents, and other
entities, and their relationships. It was particularly useful for us in order to accurately
define relationship, influences and references among literary/artistic works, people and
movements.</li>
<li><strong>DBpedia-OWL</strong> is an ontology that is derived from the DBpedia project, it
defines classes and properties for describing entities such as people, places, and
organizations, as well as their attributes and relationships; specifically, we chose
DBpedia-OWL to describe places and particular relationships among people.</li>
<li><strong>FOAF</strong> is an ontology that is used to describe people and their social
relationships, so we relied on it to describe the people in our domain.</li>
</ul>
</p><p>Other fundamental classes, such as the ones describing the type of entity or the creator of a
certain work, were chosen from <strong>RDF</strong> and <strong>DCTerms</strong>, two very widely
used ontologies, in order to increase the level of interoperability. Initially, during this phase of the project,
we searched individually for the ontology terms that we thought were more fitting for describing our
items, but in a later stage we were careful to align our choices, with the purpose of creating a
coherent model and facilitating potential queries in our dataset. </p><p>A graphical representation of the formalization is necessary to express the conceptualization
activity. Tools such as Graffoo (Graphical Framework for OWL Ontologies) can be used to produce a graphical framework for OWL ontologies. </p>
</div>
</div>
</div>
</section>
<section class="projects-section" id="projects" style="padding:0 0 0;">
<div class="container">
<section class="projects" id="projects">
<div class="container">
<div class="row align-items-center no-gutters mb-4 mb-lg-4">
<div class="col-xl-12 col-lg-12 text-center">
<iframe frameborder="1px" style="width:100%;height:600px;"
src="https://viewer.diagrams.net/?tags=%7B%7D&highlight=000000&edit=_blank&layers=1&nav=1&title=Conceptual%20Model#Uhttps%3A%2F%2Fdrive.google.com%2Fuc%3Fid%3D1Iev7r2V_7LrH3vlOdWAP3MTmwwvU0USx%26export%3Ddownload"></iframe>
</div>
</div>
</section>
</div>
</section>
<footer class="footer small text-center text-white-50">
<div class="container">
<p class="copyright-text">© DHDK - ALma Mater Bologna University</p>
<p class="copyright-text">This is a non-commercial project for scholarly purposes only.</p>
</div>
</footer>
<script src="https://code.jquery.com/jquery-3.5.1.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/animejs/3.2.1/anime.min.js"></script>
<script src="../js/scripts.js"></script>
</body>
</html>