-
Notifications
You must be signed in to change notification settings - Fork 13
/
Copy pathecrm_150929.owl
7197 lines (6497 loc) · 421 KB
/
ecrm_150929.owl
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
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:swrlb="http://www.w3.org/2003/11/swrlb#"
xmlns:xsp="http://www.owl-ontologies.com/2005/08/07/xsp.owl#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#"
xmlns:swrl="http://www.w3.org/2003/11/swrl#"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:ecrm="http://erlangen-crm.org/150929/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xml:base="http://erlangen-crm.org/150929/">
<owl:Ontology rdf:about="">
<rdfs:comment xml:lang="en">Erlangen CRM / OWL - An OWL DL 1.0 implementation of the CIDOC Conceptual Reference Model, based on: Nick Crofts, Martin Doerr, Tony Gill, Stephen Stead, Matthew Stiff (eds.): Definition of the CIDOC Conceptual Reference Model (http://cidoc-crm.org/).
This implementation has been originally created by Bernhard Schiemann, Martin Oischinger and Günther Görz at the Friedrich-Alexander-University of Erlangen-Nuremberg, Department of Computer Science, Chair of Computer Science 8 (Artificial Intelligence) in cooperation with the Department of Museum Informatics of the Germanisches Nationalmuseum Nuremberg and the Department of Biodiversity Informatics of the Zoologisches Forschungsmuseum Alexander Koenig Bonn.
The Erlangen CRM / OWL implementation of the CIDOC Conceptual Reference Model is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.</rdfs:comment>
<rdfs:comment xml:lang="en">Changelog: https://github.com/erlangen-crm/ecrm/commits/master</rdfs:comment>
<rdfs:label xml:lang="en">Erlangen CRM / OWL</rdfs:label>
<owl:versionInfo rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>ECRM 150929 / CIDOC-CRM 6.2</owl:versionInfo>
</owl:Ontology>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E57_Material">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E55_Type"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of).
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: "instances of gold".
It is recommended that internationally or nationally agreed codes and terminology are used.
Examples:
- brick
- gold
- aluminium
- polycarbonate
- resin</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E57</skos:notation>
<rdfs:label xml:lang="en">E57 Material</rdfs:label>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E66_Formation">
<rdfs:comment xml:lang="en">Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people,
such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members
at the time of formation. In order to express the joining of members at the time of formation, the
respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
the formation of the CIDOC CRM Special Interest Group
the formation of the Soviet Union
the conspiring of the murderers of Caesar
In First Order Logic:
E66(x) ⊃ E7(x)
E66(x) ⊃ E63(x)</rdfs:comment>
<rdfs:label xml:lang="en">E66 Formation</rdfs:label>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E63_Beginning_of_Existence"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E74_Group"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P95_has_formed"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E7_Activity"/>
</rdfs:subClassOf>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E66</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E93_Presence">
<rdfs:label xml:lang="en">E93 Spacetime Snapshot</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E93</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E92_Spacetime_Volume"/>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note:
This class comprises instances of E92 Spacetime Volume that result from intersection of instances of
E92 Spacetime Volume with an instance of E52 Time-Span. The identity of an instance of this class is determined by the identities of the constituing spacetime volume and the time-span. This class can be used to define temporal snapshots at a particular time-span, such as the extent of the Roman Empire at 33 B.C., or the extent occupied by a museum object at rest in an exhibit. In particular, it can be used to define the spatial projection of a spacetime volume during a particular time-span, such as the maximal spatial extent of a flood at some particular hour, or all areas covered by the Poland within the 20th century AD
In First Order Logic:
E93(x) ⊃ E92(x)</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E37_Mark">
<rdfs:comment xml:lang="en">Scope note:
This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Man-Made Thing by arbitrary techniques in order to indicate the creator, owner, dedications, purpose, etc.
This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Man-Made Feature.
Examples:
Minoan double axe mark
the copyright sign ©
smileys
In First Order Logic:
E37(x) ⊃ E36(x)</rdfs:comment>
<rdfs:label xml:lang="en">E37 Mark</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E37</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E36_Visual_Item"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E24_Physical_Man-Made_Thing">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E24</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E18_Physical_Thing"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E12_Production"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P108i_was_produced_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E71_Man-Made_Thing"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises all persistent physical items that are purposely created by human activity.
This class comprises man-made objects, such as a swords, and man-made features, such as rock art. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, a "cup and ring" carving on bedrock is regarded as instance of E24 Physical Man-Made Thing.
Examples:
- the Forth Railway Bridge (E22)
- the Channel Tunnel (E25)
- the Historical Collection of the Museum Benaki in Athens (E78)
In First Order Logic:
E24(x) ⊃ E18(x)
E24(x) ⊃ E71(x)</rdfs:comment>
<rdfs:label xml:lang="en">E24 Physical Man-Made Thing</rdfs:label>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E25_Man-Made_Feature">
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E24_Physical_Man-Made_Thing"/>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E26_Physical_Feature"/>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">E25 Man-Made Feature</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc.
No assumptions are made as to the extent of modification required to justify regarding a feature as man-made. For example, rock art or even "cup and ring" carvings on bedrock a regarded as types of E25 Man-Made Feature.
Examples:
- the Manchester Ship Canal
- Michael Jackson's nose following plastic surgery
In First Order Logic:
E25(x) ⊃ E26(x)
E25(x) ⊃ E24(x)</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E25</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E29_Design_or_Procedure">
<rdfs:label xml:lang="en">E29 Design or Procedure</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing.
Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 has association with (is associated with)..
Designs or procedures can be seen as one of the following:
1. A schema for the activities it describes
2. A schema of the products that result from their application.
3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci's famous plans for flying machines.
Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product.
Examples:
- the ISO standardisation procedure
- the musical notation of Beethoven's "Ode to Joy"
- the architectural drawings for the Kölner Dom in Cologne, Germany
- The drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan
In First Order Logic:
E29(x) ⊃ E73(x)</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E29</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E73_Information_Object"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E84_Information_Carrier">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E84</skos:notation>
<rdfs:label xml:lang="en">E84 Information Carrier</rdfs:label>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E22_Man-Made_Object"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical carriers for instances of E73 Information Object.
An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an Information Carrier. Therefore the property P128 carries (is carried by) applies to E18 Physical Thing in general.
Examples:
- the Rosetta Stone
- my paperback copy of Crime & Punishment
- the computer disk at ICS-FORTH that stores the canonical Definition of the CIDOC CRM
In First Order Logic:
E84(x) ⊃ E22(x)</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E77_Persistent_Item">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E77</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E1_CRM_Entity"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises items that have a persistent identity, sometimes known as "endurants" in philosophy.
They can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. Persistent Items can be either physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names.
The criteria that determine the identity of an item are often difficult to establish -; the decision depends largely on the judgement of the observer. For example, a building is regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria. Similarly, inanimate objects may be subject to exchange of parts and matter. The class E77 Persistent Item does not take any position about the nature of the applicable identity criteria and if actual knowledge about identity of an instance of this class exists. There may be cases, where the identity of an E77 Persistent Item is not decidable by a certain state of knowledge.
The main classes of objects that fall outside the scope the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties.
Examples:
- Leonardo da Vinci
- Stonehenge
- the hole in the ozone layer
- the First Law of Thermodynamics
- the Bermuda Triangle
In First Order Logic:
E77(x) ⊃ E1(x)</rdfs:comment>
<rdfs:label xml:lang="en">E77 Persistent Item</rdfs:label>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E34_Inscription">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E33_Linguistic_Object"/>
</rdfs:subClassOf>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E37_Mark"/>
<rdfs:comment xml:lang="en">Scope note:
This class comprises recognisable, short texts attached to instances of E24 Physical Man-Made Thing.
The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CRM as E24 Physical Man-Made Thing.
The relationship of a physical copy of a book to the text it contains is modelled using E84 Information Carrier. P128 carries (is carried by): E33 Linguistic Object.
Examples:
- "keep off the grass" on a sign stuck in the lawn of the quad of Balliol College
- The text published in Corpus Inscriptionum Latinarum V 895
- Kilroy was here
In First Order Logic:
E34(x) ⊃ E33(x)
E34(x) ⊃ E37(x)</rdfs:comment>
<rdfs:label xml:lang="en">E34 Inscription</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E34</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E70_Thing">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E70</skos:notation>
<rdfs:label xml:lang="en">E70 Thing</rdfs:label>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E77_Persistent_Item"/>
<rdfs:comment xml:lang="en">Scope note:
This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability.
They may be intellectual products or physical things. They may for instance have a solid physical form, an electronic encoding, or they may be a logical concept or structure.
Examples:
- my photograph collection (E78)
- the bottle of milk in my refrigerator (E22)
- the plan of the Strassburger Muenster (E29)
- the thing on the top of Otto Hahn's desk (E19)
- the form of the no-smoking sign (E36)
- the cave of Dirou, Mani, Greece (E27)
In First Order Logic:
E70(x) ⊃ E77(x)</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E36_Visual_Item">
<rdfs:label xml:lang="en">E36 Visual Item</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E36</skos:notation>
<rdfs:comment xml:lang="en">Scope note:
This class comprises the intellectual or conceptual aspects of recognisable marks and images.
This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support.
The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Man-Made Thing that carry the same visual symbols, marks or images etc. The property P62 depicts (is depicted by) between E24 Physical Man-Made Thing and depicted subjects (E1 CRM Entity) can be regarded as a short-cut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.
Examples:
- the visual appearance of Monet's "La Pie" (E38)
- the Coca-Cola logo (E34)
- the Chi-Rho (E37)
- the communist red star (E37)
In First Order Logic:
E36(x) ⊃ E73(x)</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E73_Information_Object"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E13_Attribute_Assignment">
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E1_CRM_Entity"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P140_assigned_attribute_to"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E7_Activity"/>
</rdfs:subClassOf>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E13</skos:notation>
<rdfs:label xml:lang="en">E13 Attribute Assignment</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts.
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
Examples:
- the assessment of the current ownership of Martin Doerr's silver cup in February 1997</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E69_Death">
<rdfs:comment xml:lang="en">Scope note:
This class comprises the deaths of human beings.
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
In First Order Logic:
E69(x) ⊃ E64(x)</rdfs:comment>
<rdfs:label xml:lang="en">E69 Death</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E69</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E64_End_of_Existence"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E21_Person"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P100_was_death_of"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E8_Acquisition">
<rdfs:comment xml:lang="en">Scope note:
This class comprises transfers of legal ownership from one or more instances of E39 Actor to one or more other instances of E39 Actor.
The class also applies to the establishment or loss of ownership of instances of E18 Physical Thing. It does not, however, imply changes of any other kinds of right. The recording of the donor and/or recipient is optional. It is possible that in an instance of E8 Acquisition there is either no donor or no recipient. Depending on the circumstances, it may describe:
1. the beginning of ownership
2. the end of ownership
3. the transfer of ownership
4. the acquisition from an unknown source
5. the loss of title due to destruction of the item
It may also describe events where a collector appropriates legal title, for example by annexation or field collection. The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership (E8 Acquisition) and physical custody (E10 Transfer of Custody) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Examples:
- the collection of a hammer-head shark of the genus Sphyrna (Carchariniformes) XXXtbc by John Steinbeck and Edward Ricketts at Puerto Escondido in the Gulf of Mexico on March 25th, 1940
- the acquisition of El Greco's "The Apostles Peter and Paul" by the State Hermitage in Saint Petersburg
- the loss of my stuffed chaffinch 'Fringilla coelebs Linnaeus, 1758' due to insect damage last year
In First Order Logic:
E8(x) ⊃ E7(x)</rdfs:comment>
<rdfs:label xml:lang="en">E8 Acquisition</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E8</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E7_Activity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P24_transferred_title_of"/>
</owl:onProperty>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
>1</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E14_Condition_Assessment">
<rdfs:comment xml:lang="en">Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year's inspection of humidity damage to the frescos in the St. George chapel in our village
In First Order Logic:
E14(x) ⊃ E13(x)</rdfs:comment>
<rdfs:label xml:lang="en">E14 Condition Assessment</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E14</skos:notation>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E13_Attribute_Assignment"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
>1</owl:minCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P35_has_identified"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P34_concerned"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E18_Physical_Thing"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E92_Spacetime_Volume">
<rdfs:label xml:lang="en">E92 Spacetime Volume</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Scope note:
This class comprises 4 dimensional point sets (volumes) in physical spacetime regardless its true geometric form. They may derive their identity from being the extent of a material phenomenon or from being the interpretation of an expression defining an extent in spacetime. Intersections of instances of E92 Spacetime Volume, Place and Timespan are also regarded as instances of E92 Spacetime Volume. An instance of E92 Spacetime Volume is either contiguous or composed of a finite number of contiguous subsets. Its boundaries may be fuzzy due to the properties of the phenomena it derives from or due to the limited precision up to which defining expression can be identified with a real extent in spacetime. The duration of existence of an instance of a spacetime volume is trivially its projection on time.
Examples:
- the spacetime Volume of the Event of Ceasars murder
- the spacetime Volume where and when the carbon 14 dating of the "Schoeninger Speer II" in 1996 took place
- the spatio‐temporal trajectory of the H.M.S. Victory from its building to its actual location
- the spacetime volume defined by a polygon approximating the Danube river flood in Austria between 6th and 9th of August 2002
In First Order Logic:
E92(x) ⊃ E1(x)</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E92</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E1_CRM_Entity"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E80_Part_Removal">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E11_Modification"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P112_diminished"/>
</owl:onProperty>
<owl:someValuesFrom rdf:resource="http://erlangen-crm.org/150929/E24_Physical_Man-Made_Thing"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P113_removed"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E18_Physical_Thing"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part.
Typical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated E78 Collection. If the E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an E81 Transformation, i.e. a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be regarded as both E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewelry, or cultural artifacts being deaccessioned from different museum collections over their lifespan.
Examples:
- the removal of the engine from my car
- the disposal of object number 1976:234 from the collection
In First Order Logic:
E80(x) ⊃ E11(x)</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E80</skos:notation>
<rdfs:label xml:lang="en">E80 Part Removal</rdfs:label>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E31_Document">
<rdfs:label xml:lang="en">E31 Document</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E31</skos:notation>
<rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable immaterial items that make propositions about reality.
These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as a special case of E31 Document. This class should not be confused with the term "document" in Information Technology, which is compatible with E73 Information Object.
Examples:
- the Encyclopaedia Britannica (E32)
- The image content of the photo of the Allied Leaders at Yalta published by UPI, 1945 (E38)
- the Doomsday Book
In First Order Logic:
E31(x) ⊃ E73(x)</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E1_CRM_Entity"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P70_documents"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E73_Information_Object"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E4_Period">
<rdfs:label xml:lang="en">E4 Period</rdfs:label>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E2_Temporal_Entity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E53_Place"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P7_took_place_at"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E92_Spacetime_Volume"/>
<rdfs:comment xml:lang="en">Scope note:
This class comprises sets of coherent phenomena or cultural manifestations occurring in time and
space.
It is the social or physical coherence of these phenomena that identify an E4 Period and not the
associated spatiotemporal extent. This extent is only the “ground” or space in an abstract physical sense
that the actual process of growth, spread and retreat has covered. Consequently, different periods can
overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time
as a sedentary culture. This also means that overlapping land use rights, common among first nations,
amounts to overlapping periods.
Often, this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the
“Ming Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are
regarded as special cases of E4 Period. However, there are no assumptions about the scale of the
associated phenomena. In particular all events are seen as synthetic processes consisting of coherent
phenomena. Therefore E4 Period is a superclass of E5 Event. For example, a modern clinical E67 Birth
can be seen as both an atomic E5 Event and as an E4 Period that consists of multiple activities
performed by multiple instances of E39 Actor.
As the actual extent of an E4 Period in spacetime we regard the trajectories of the participating physical
things during their participation in an instance of E4 Period. This includes the open spaces via which
these things have interacted and the spaces by which they had the potential to interact during that
period or event in the way defined by the type of the respective period or event. Examples include the
air in a meeting room transferring the voices of the participants. Since these phenomena are fuzzy, we
assume the spatiotemporal extent to be contiguous, except for cases of phenomena spreading out over
islands or other separated areas, including geopolitical units distributed over disconnected areas such as
islands or colonies.
Whether the trajectories necessary for participants to travel between these areas are regarded as part of
the spatiotemporal extent or not has to be decided in each case based on a concrete analysis, taking use
of the sea for other purposes than travel, such as fishing, into consideration. One may also argue that
the activities to govern disconnected areas imply travelling through spaces connecting them and that
these areas hence are spatially connected in a way, but it appears counterintuitive to consider for
instance travel routes in international waters as extensions of geopolitical units.
Consequently, an instance of E4 Period may occupy a number of disjoint spacetime volumes, however
there must not be a discontinuity in the timespan covered by these spacetime volumes. This means that
an instance of E4 Period must be contiguous in time. If it has ended in all areas, it has ended as a
whole. However it may end in one area before another, such as in the Polynesian migration, and it
continues as long as it is ongoing in at least one area.
We model E4 Period as a subclass of E2 Temporal Entity and of E92 Spacetime volume. The latter is
intended as a phenomenal spacetime volume as defined in CRMgeo (Doerr and Hiebel 2013). By virtue
of this multiple inheritance we can discuss the physical extent of an E4 Period without representing
each instance of it together with an instance of its associated spacetime volume. This model combines
two quite different kinds of substance: an instance of E4 Period is a phenomena while a spacetime
volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance
of E4 Period is regarded to be unique to it due to all its details and fuzziness; its identity and existence
depends uniquely on the identity of the instance of E4 Period. Therefore this multiple inheritance is
unambiguous and effective and furthermore corresponds to the intuitions of natural language.
There are two different conceptualisations of ‘artistic style’, defined either by physical features or by
historical context. For example, “Impressionism” can be viewed as a period lasting from approximately
1870 to 1905 during which paintings with particular characteristics were produced by a group of artists
that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be
regarded as a style applicable to all paintings sharing the characteristics of the works produced by the
Impressionist painters, regardless of historical context. The first interpretation is an instance of E4
Period, and the second defines morphological object types that fall under E55 Type.
Another specific case of an E4 Period is the set of activities and phenomena associated with a
settlement, such as the populated period of Nineveh.
Examples:
- Jurassic
- European Bronze Age
- Italian Renaissance
- Thirty Years War
- Sturm und Drang
- Cubism
In First Order Logic:
E4(x) ⊃ E2(x)
E4(x) ⊃ E92(x)</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E4</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E72_Legal_Object">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E72</skos:notation>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E70_Thing"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E30_Right"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P104_is_subject_to"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E39_Actor"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P105_right_held_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">E72 Legal Object</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied.
This is true for all E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of the E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CRM.
Examples:
- the Cullinan diamond (E19)
- definition of the CIDOC Conceptual Reference Model Version 2.1 (E73)
In First Order Logic:
E72(x) ⊃ E70(x)</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E19_Physical_Object">
<rdfs:label xml:lang="en">E19 Physical Object</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises items of a material nature that are units for documentation and have physical boundaries that separate them completely in an objective way from other objects.
The class also includes all aggregates of objects made for functional purposes of whatever kind, independent of physical coherence, such as a set of chessmen. Typically, instances of E19 Physical Object can be moved (if not too heavy).
In some contexts, such objects, except for aggregates, are also called "bona fide objects" (Smith & Varzi, 2000, pp.401-420), i.e. naturally defined objects.
The decision as to what is documented as a complete item, rather than by its parts or components, may be a purely administrative decision or may be a result of the order in which the item was acquired.
Examples:
- John Smith
- Aphrodite of Milos
- the Palace of Knossos
- the Cullinan diamond
- Apollo 13 at the time of launch
In First Order Logic:
E19(x) ⊃ E18(x)</rdfs:comment>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E19</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E18_Physical_Thing"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
>1</owl:maxCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P55_has_current_location"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P54_has_current_permanent_location"/>
</owl:onProperty>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
>1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E2_Temporal_Entity">
<owl:disjointWith rdf:resource="http://erlangen-crm.org/150929/E77_Persistent_Item"/>
<rdfs:label xml:lang="en">E2 Temporal Entity</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E2</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E1_CRM_Entity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
>1</owl:cardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P4_has_time-span"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, which happen over a limited extent in time. This extent in time must be contiguous, i.e., without gaps. In case the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur
later again at another time, we regard that the former E2 Temporal Entity has ended and a new instance has come into existence. In more intuitive terms, the same event cannot happen twice.
In some contexts, these are also called perdurants. This class is disjoint from E77 Persistent Item. This is an abstract class and has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing.
Examples:
- Bronze Age (E4)
- the earthquake in Lisbon 1755 (E5)
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946 (E3)
In First Order Logic:
E2(x) ⊃ E1(x)</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E49_Time_Appellation">
<rdfs:comment xml:lang="en">Scope note:
This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, "Before Christ" for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. 'the duration of the Ming Dynasty'.
Examples:
- "Meiji" [Japanese term for a specific time-span]
- "1st half of the XX century"
- "Quaternary"
- "1215 Hegira" [a date in the Islamic calendar]
- "Last century"
In First Order Logic:
E49(x) ⊃ E41(x)</rdfs:comment>
<rdfs:label xml:lang="en">E49 Time Appellation</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E49</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E41_Appellation"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E58_Measurement_Unit">
<rdfs:label xml:lang="en">E58 Measurement Unit</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E58</skos:notation>
<rdfs:comment xml:lang="en">Scope note:
This class is a specialization of E55 Type and comprises the types of measurement units: feet, inches, centimetres, litres, lumens, etc.
This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E58 Measurement Unit, e.g.: "instances of cm".
Système International (SI) units or internationally recognized non-SI terms should be used whenever possible. (ISO 1000:1992). Archaic Measurement Units used in historical records should be preserved.
Examples:
- cm [centrimetre]
- km [kilometre]
- m [meter]
- m/s [meters per second]
- A [Ampere]
- GRD [Greek Drachme]
- C° [degrees centigrade]</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E55_Type"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P91i_is_unit_of"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E54_Dimension"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E79_Part_Addition">
<rdfs:comment xml:lang="en">Scope note:
This class comprises activities that result in an instance of E24 Physical Man-Made Thing being increased, enlarged or augmented by the addition of a part.
Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated E78 Collection. Objects to which parts are added are, by definition, man-made, since the addition of a part implies a human activity. Following the addition of parts, the resulting man-made assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically (for example the engine becoming a part of the car), or by sharing a common purpose (such as the 32 chess pieces that make up a chess set). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artifacts being added to different museum instances of E78 Collection over their lifespan.
Examples:
- the setting of the koh-i-noor diamond into the crown of Queen Elizabeth the Queen Mother
- the addition of the painting "Room in Brooklyn" by Edward Hopper to the collection of the Museum of Fine Arts, Boston
In First Order Logic:
E79(x) ⊃ E11(x)</rdfs:comment>
<rdfs:label xml:lang="en">E79 Part Addition</rdfs:label>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E11_Modification"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P110_augmented"/>
</owl:onProperty>
<owl:someValuesFrom rdf:resource="http://erlangen-crm.org/150929/E24_Physical_Man-Made_Thing"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P111_added"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E18_Physical_Thing"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E79</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E75_Conceptual_Object_Appellation">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E41_Appellation"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises all appellations specific to intellectual products or standardized patterns.
This class comprises appellations that are by their form or syntax specific to identifying instances of
E28 Conceptual Object, such as intellectual products, standardized patterns etc.
Examples:
- "ISBN 3-7913-1418-1"
- "ISO 2788-1986 (F)"
- "DOI=10.1109/MIS.2007.103"
In First Order Logic:
E75(x) ⊃ E41(x)</rdfs:comment>
<rdfs:label xml:lang="en">E75 Conceptual Object Appellation</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E75</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E45_Address">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E45</skos:notation>
<rdfs:label xml:lang="en">E45 Address</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
Examples:
- "1-29-3 Otsuka, Bunkyo-ku, Tokyo, 121, Japan"
- "Rue David Dufour 5, CH-1211, Genève"
In First Order Logic:
E45(x) ⊃ E44(x)
E45(x) ⊃ E51(x)</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E44_Place_Appellation"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E51_Contact_Point"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E65_Creation">
<rdfs:label xml:lang="en">E65 Creation</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
In First Order Logic:
E65(x) ⊃ E7(x)
E65(x) ⊃ E63(x)</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E63_Beginning_of_Existence"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P94_has_created"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E28_Conceptual_Object"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E7_Activity"/>
</rdfs:subClassOf>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E65</skos:notation>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E32_Authority_Document">
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E32</skos:notation>
<rdfs:label xml:lang="en">E32 Authority Document</rdfs:label>
<rdfs:comment xml:lang="en">Scope note:
This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.
Examples:
- Webster's Dictionary
- Getty Art and Architecture Thesaurus
- the CIDOC Conceptual Reference Model
In First Order Logic:
E32(x) ⊃ E31(x)</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E31_Document"/>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E47_Spatial_Coordinates">
<rdfs:label xml:lang="en">E47 Spatial Coordinates</rdfs:label>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E47</skos:notation>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E44_Place_Appellation"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification.
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
Examples:
- "6°5'29"N 45°12'13"W"
- "Black queen's bishop 4" [chess coordinate].
In First Order Logic:
E47(x) ⊃ E44(x)</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E18_Physical_Thing">
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"
>1</owl:maxCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P13i_was_destroyed_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P53_has_former_or_current_location"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E53_Place"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E28_Conceptual_Object"/>
</owl:disjointWith>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom rdf:resource="http://erlangen-crm.org/150929/E57_Material"/>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/150929/P45_consists_of"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<skos:notation rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>E18</skos:notation>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E72_Legal_Object"/>
<rdfs:comment xml:lang="en">Scope note:
This class comprises all persistent physical items with a relatively stable form, man-made or natural.
Depending on the existence of natural boundaries of such things, the CRM distinguishes the instances
of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc.
Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to
the surrounding matter.
An instance of E18 Physical Thing occupies not only a particular geometric space, but in the course of
its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal,
volume in spacetime. We include in the occupied space the space filled by the matter of the physical
thing and all its inner spaces, such as the interior of a box. Physical things consisting of aggregations of
physically unconnected objects, such as a set of chessmen, occupy a number of individually contiguous
spacetime volumes equal to the number of unconnected objects that constitute the set.
We model E18 Physical Thing to be a subclass of E72 Legal Object and of E92 Spacetime volume. The
latter is intended as a phenomenal spacetime volume as defined in CRMgeo (Doerr and Hiebel 2013).
By virtue of this multiple inheritance we can discuss the physical extent of an E18 Physical Thing
without representing each instance of it together with an instance of its associated spacetime volume.
This model combines two quite different kinds of substance: an instance of E18 Physical Thing is
matter while a spacetime volume is an aggregation of points in spacetime. However, the real
spatiotemporal extent of an instance of E18 Physical Thing is regarded to be unique to it, due to all its
details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E18
Physical Thing. Therefore this multiple inheritance is unambiguous and effective and furthermore
corresponds to the intuitions of natural language.
The CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states.
Examples:
- the Cullinan Diamond (E19)
- the cave "Ideon Andron" in Crete (E26)
- the Mona Lisa (E22)
In First Order Logic:
E18(x) ⊃ E72(x)
E18(x) ⊃ E92(x)</rdfs:comment>
<rdfs:label xml:lang="en">E18 Physical Thing</rdfs:label>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/150929/E92_Spacetime_Volume"/>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/150929/E73_Information_Object">
<rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units.
The encoding structure known as a "named graph" also falls under this class, so that each "named graph" is an instance of an E73 Information Object.
An E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously.
Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression.
Examples:
- image BM000038850.JPG from the Clayton Herbarium in London