-
Notifications
You must be signed in to change notification settings - Fork 0
/
MoSA_v0.html
438 lines (393 loc) · 15.2 KB
/
MoSA_v0.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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Museum of Stolen Artifacts v0</title>
<style>
table {
font-family: arial, sans-serif;
border-collapse: collapse;
width: 100%;
}
td, th {
border: 1px solid #dddddd;
text-align: left;
padding: 8px;
}
tr:nth-child(odd) {
background-color: #dddddd;
}
</style>
<!-- <link rel="icon" href="./favicon.ico" type="image/x-icon"> -->
</head>
<body>
<h1>Museum of Stolen Artifacts Ontology v0</h1>
<hr>
<p><i>For questions or criticisms, please contact Valentin (at <valevogelmann <i>at</i>> gmail <i>dot</i> com), who maintains this document.</i></p>
<p>This is the first, basic version of the <i>Museum of Stolen Artifacts Ontology</i> (<i>MoSA</i> for short) and not even a draft, thus subject to constant changes. This is the document which can be referred to when structuring data using the MoSA ontology — all of the entities and predicates the MoSA ontology defines are listed below including their domains, ranges and relationships.
</p>
<hr>
<h2>Entities</h2>
<p>Since we are taking an iterative and bottom-up approach, this ontology is not defined with as a hierarchy of entities with a top-level element. It means that we only define the entities we "need" for making data more useful and clarifying intentions. For instance, it also means that (for now) we don't make commitments about <i>what</i> the objects in the Museum of Stolen Artifacts are.</p>
<h3>Layer Entities</h3>
<p>We do want to distinguish the different "layers of existence" of that might (or might not) apply to an object, for now these are (1) of course its physical manifestation(s) and (2) digital records that witness their existence and describe them. The latter are, however, typically taken from institutions in those countries that have stolen them, and this is a core reason for making this distinction explicit: Separating objects from what different parties say about them, can allow us to question and contest.</p>
<table>
<tr>
<th id="PhysicalManifestation">PhysicalManifestation</th>
</tr>
<tr>
<td>
<ul>
<li>Definition: </li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="DigitalRecord">DigitalRecord</th>
</tr>
<tr>
<td>
<ul>
<li>Definition: A record in a digital collection, dataset, etc which witnesses or claims the existence of an object (physical or not) and describes typically aspects of it. </li>
<li>Usage notes: This entity type mainly serves the purpose of bringing together information from various institutional collection systems but can explicitly also be used to create new records. Note, however, that of course an entry in the MoSA itself is also a <i>DigitalRecord</i> but we reserve this entity for representing <i>external</i> digital records.</li>
<li>Required properties:
<ul>
<li>
<a href=#identified_by>identified_by</a>: Making it possible to refer back to the record in its original context; requiring an identifier <i>should</i> be possible because of the digital nature of this entity.
</li>
<li>
<a href=#assigned_title>assigned_title</a>: For human identification of records, it is covenient to have a title; could be forged in case not present in an original record.
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table>
<h3>Object-Context Entities</h3>
<table>
<tr>
<th id="Museum">Museum</th>
</tr>
<tr>
<td>
<ul>
<li>Superclasses: [UNDER CONSTRUCTION: it might be useful to create a fuller ontology (i.e. hierarchy) of institutional and non-institutional entities that are actors in the context of stolen artefacts. the superclass of a <b>(Western)</b> <i>Museum</i> could then be something like "(Western) Institution"?</li>
<li>Subclasses: [UNDER CONSTRUCTION: It could become useful to distinguish different kinds of <i>(Western)</i> museums?]</li>
<li>Definition: [UNDER CONSTRUCTION: A (public) institution which holds an object in the MoSA, i.e. a stolen artefact, and is the provider of the information in a <a href="#DigitalRecord">DigitalRecord</a>.] </li>
<li>Usage notes: [UNDER CONSTRUCTION: This entity class has been created on the fly out of the need to "name" entities like the British Museum, Wereldmuseum and Musei Vaticani. The name of this class as well as its meaning are very much open for debate.]</li>
</ul>
</td>
</tr>
</table>
<h3>Provenance Entities</h3>
<table>
<tr>
<th id="ProvGeneric">ProvGeneric</th>
</tr>
<tr>
<td>
<ul>
<li>Superclasses: [UNDER CONSTRUCTION: There could be more generic entities which connect to other events in an artefact's history.]</li>
<li>Subclasses:
<ul>
<li><a href=#ProvAcquisition>ProvAcquisition</a></li>
<li>[UNDER CONSTRUCTION]: Add other specific provenance types.</li>
</ul>
</li>
<li>Definition: A generic <i>provenance</i> entry, i.e. any event or part of an artefact's history during or after its theft, and relating to how the artefact ended up in its current location.</li>
<li>Usage notes: This class and all of its subclasses carry the name <i>provenance</i>, a term in used in Western historical and museological context to describe how (and why) an object got to its present location. It is supposed to be a neutral term for research purposes but masks or hides violences and injustices. We adopt the term here to describe what other institutions describe but don't identify with it.</li>
</ul>
</td>
</tr>
<tr>
<th id="ProvAcquisition">ProvAcquisition</th>
</tr>
<tr>
<td>
<ul>
<li>Superclasses:
<ul>
<li><a href=#ProvGeneric>ProvGeneric</a></li>
</ul>
</li>
<li>Subclasses:</li>
<li>Definition: </li>
<li>Usage notes: Much like its super class term <i>provenance</i>, the term <i>acquisition</i> is supposed to neutrally and generically describe how e.g. a state or museum came into possession of an object and masks that often these events were thefts, looting and other injust, violent actions. Like in the of the super class, we record the term because they use it./li>
</ul>
</td>
</tr>
</table>
<h3>Datatype Entities</h3>
<table>
<tr>
<th id="DateDescription">DateDescription</th>
</tr>
<tr>
<td>
<ul>
<li>Definition:</li>
<li>Usage notes:</li>
<li>Required properties:
<ul>
<li>
<a href=#assigned_text>assigned_text</a>
</li>
</ul>
</li>
</ul>
</td>
</tr>
<tr>
<th id="LocationDescription">LocationDescription</th>
</tr>
<tr>
<td>
<ul>
<li>Definition:</li>
<li>Usage notes:</li>
<li>Required properties:
<ul>
<li>
<a href=#assigned_text>assigned_text</a>
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table>
<hr>
<h2>Predicates</h2>
<h3>Top-level Predicates</h3>
<p>Predicates of this kind are intended to be applied directly to members of the MoSA at the top level, this is however not a strict restriction.</p>
<table>
<tr>
<th id="name">name</th>
</tr>
<tr>
<td>
<ul>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="digitally_represented_by">digitally_represented_by</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range: <a href=#DigitalRecord>DigitalRecord</a></li>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="physical_object">physical_object</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:</li>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
</table>
<h3>Predicates pertaining to DigitalRecord</h3>
<p>These predicates may also be used in other contexts, re-use is in fact encouraged (e.g. <a href=#assigned_text>assigned_text</a> can be used for attaching any text to any entity). The reason for calling most predicates "assigned_" is to highlight the contestable nature of attributions.</p>
<table>
<tr>
<th id="identified_by">identified_by</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:<a href=#DigitalRecord>DigitalRecord</a></li>
<li>Range: a unique, persistent identifier (e.g. a URI)</li>
<li>Definition: </li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="assigned_title">assigned_title</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range: </li>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="assigned_text">assigned_text</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:</li>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="assigned_culture">assigned_culture</th>
</tr>
<tr>
<td>
<ul>
<li>Domain: any</li>
<li>Range: string (for now) in various languages</li>
<li>Definition:</li>
<li>Usage notes: Museum institutions typically assign cultures to objects (sometimes also known as "ethnic group" or "population"), this predicate can be used to record that. For now, we treat the assigned culture as a simple strig, eventually it should be a link (e.g. into a thesaurus).</li>
</ul>
</td>
</tr>
<tr>
<th id="assigned_prov">assigned_prov</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:</li>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="assigned_date">assigned_date</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:</li>
<li>Definition:</li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
</table>
<h3>Predicates pertaining to PhysicalManifestation</h3>
<p></p>
<table>
<tr>
<th id="currently_at">currently_at</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:
<ul>
<li><a href=#Museum>Museum</a></li>
<li><a href=#LocationDescription>LocationDescription</a></li>
</ul>
</li>
<li>Definition: </li>
<li>Usage notes: This property refers not (necessarily) to a precise geographical location (see <a href=#precise_location>precise_location</a> for that) but rather to a concept or (geo-polotical) entity with a geographical manifestitation, such as a country or a museum. This property may contain a <a href=#precise_location>precise_location</a> to further specify <i>where exacctly</i> in the entity the object is, e.g. a room.</li>
</ul>
</td>
</tr>
<tr>
<th id="should_be_at">should_be_at</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:</li>
<li>Definition: </li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="assigned_mnemonic">assigned_mnemonic</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range: string</li>
<li>Definition: Mnemonic (or inventory number, object number, etc) given to the physical object where it either currently is (<a href=#currently_at>currently_at</a>) or, if applicable, should be (<a href=#should_be_at>should_be_at</a>) and given to the object as a unique identifier.</li>
<li>Usage notes: Museums and other object-holding instituion use all sorts of standards for coining mnemonics, which is why the range of this property is basic strings. These mnemonics are (especially outside of digital context) a key way by which objects are identified in the places they are held, so this property should also be given for physical objects.</li>
</ul>
</td>
</tr>
<tr>
<th id="precise_location">precise_location</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:
<ul>
<li> <a href=#LocationDescription>LocationDescription</a>
</li>
<li><a href="https://www.geonames.org/">geonames URI</a></li>
</ul>
</li>
<li>Definition: </li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
<tr>
<th id="depicted_by">depicted_by</th>
</tr>
<tr>
<td>
<ul>
<li>Domain:</li>
<li>Range:</li>
<li>Definition: </li>
<li>Usage notes:</li>
</ul>
</td>
</tr>
</table>
</body>
</html>
<!-- ## entities
- DigitalRecord
- PhysicalManifestation
- ProvGeneric
- ProvAcquisition
-
- DateDescription
- LocationDescription
## predicates
<li>Domain:</li>
<li>Range:</li>
- name
- digitally_represented_by
- identified_by
- assigned_title
- assigned_text
- assigned_culture
- assigned_prov
- assigned_date
- physical_objects
- currently_at
- should_be_at
- assigned_mnemonic
- precise_location
- depicted_by
-->