-
Notifications
You must be signed in to change notification settings - Fork 13
/
Copy pathecrm_091125.owl
5312 lines (3611 loc) · 290 KB
/
ecrm_091125.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="http://erlangen-crm.org/091125/"
xml:base="http://erlangen-crm.org/091125/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:owl2xml="http://www.w3.org/2006/12/owl2-xml#"
xmlns:ecrm="http://erlangen-crm.org/091125/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<owl:Ontology rdf:about="">
<rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Erlangen CRM / OWL</rdfs:label>
<owl:versionInfo
>ECRM 2009-11-25 / CIDOC-CRM 5.0.1</owl:versionInfo>
<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.ics.forth.gr/. This implementation has been originally created by Bernhard Schiemann, Martin Oischinger and Guenther Goerz at the Friedrich-Alexander-University of Erlangen-Nuremberg, Department of Computer Science, Chair of Computer Science 8 (Artificial Intelligence) and is currently developed 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. All writes reserved.</rdfs:comment>
</owl:Ontology>
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Object Properties
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<!-- http://erlangen-crm.org/091125/P1.is_identified_by -->
<owl:ObjectProperty rdf:about="P1.is_identified_by">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property describes the naming or identification of any real world item by a name or any other identifier.
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.
Examples: the capital of Italy (E53) is identified by "Rome" (E48), text 25014-32 (E33) is identified by "The Decline and Fall of the Roman Empire" (E35).</rdfs:comment>
<rdfs:domain rdf:resource="E1.CRM_Entity"/>
<rdfs:range rdf:resource="E41.Appellation"/>
<owl:inverseOf rdf:resource="P1I.identifies"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P10.falls_within -->
<owl:ObjectProperty rdf:about="P10.falls_within">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property describes an instance of E4 Period, which falls within the E53 Place and E52 Time-Span of another.
The difference with P9 consists of (forms part of) is subtle. Unlike P9 consists of (forms part of), P10 falls within (contains) does not imply any logical connection between the two periods and it may refer to a period of a completely different type.
Example: the Great Plague (E4) falls within The Gothic period (E4).</rdfs:comment>
<rdfs:range rdf:resource="E4.Period"/>
<rdfs:domain rdf:resource="E4.Period"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P100.was_death_of -->
<owl:ObjectProperty rdf:about="P100.was_death_of">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property links an E69 Death event to the E21 Person that died.
A Death event may involve multiple people, for example in the case of a battle or disaster.
This is not intended for use with general Natural History material, only people.
Example: Mozart's death (E69) was death of Mozart (E21).</rdfs:comment>
<rdfs:range rdf:resource="E21.Person"/>
<rdfs:domain rdf:resource="E69.Death"/>
<rdfs:subPropertyOf rdf:resource="P93.took_out_of_existence"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P100I.died_in -->
<owl:ObjectProperty rdf:about="P100I.died_in">
<rdfs:domain rdf:resource="E21.Person"/>
<rdfs:range rdf:resource="E69.Death"/>
<owl:inverseOf rdf:resource="P100.was_death_of"/>
<rdfs:subPropertyOf rdf:resource="P93I.was_taken_out_of_existence_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P101.had_as_general_use -->
<owl:ObjectProperty rdf:about="P101.had_as_general_use">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property links an instance of E70 Thing to an E55 Type of usage.
It allows the generic link between things, both physical and immaterial, to methods and techniques of use. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery. Example: Tony Gill's Ford Mustang (E22) had as general use transportation (E55).</rdfs:comment>
<rdfs:range rdf:resource="E55.Type"/>
<rdfs:domain rdf:resource="E70.Thing"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P101I.was_use_of -->
<owl:ObjectProperty rdf:about="P101I.was_use_of">
<rdfs:domain rdf:resource="E55.Type"/>
<rdfs:range rdf:resource="E70.Thing"/>
<owl:inverseOf rdf:resource="P101.had_as_general_use"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P102.has_title -->
<owl:ObjectProperty rdf:about="P102.has_title">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property.
The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc.
It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind.
Example: the first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55).</rdfs:comment>
<rdfs:range rdf:resource="E35.Title"/>
<rdfs:domain rdf:resource="E71.Man-Made_Thing"/>
<rdfs:subPropertyOf rdf:resource="P1.is_identified_by"/>
<owl:inverseOf rdf:resource="P102I.is_title_of"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P102I.is_title_of -->
<owl:ObjectProperty rdf:about="P102I.is_title_of">
<rdfs:domain rdf:resource="E35.Title"/>
<rdfs:range rdf:resource="E71.Man-Made_Thing"/>
<rdfs:subPropertyOf rdf:resource="P1I.identifies"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P103.was_intended_for -->
<owl:ObjectProperty rdf:about="P103.was_intended_for">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property links an instance of E71 Man-Made Thing to an E55 Type of usage.
It creates a property between specific man-made things, both physical and immaterial, to Types of intended methods and techniques of use. Note: A link between specific man-made things and a specific use activity should be expressed using P19 was intended use of (was made for).
Example: this plate (E22) was intended for being destroyed at wedding reception (E55).</rdfs:comment>
<rdfs:range rdf:resource="E55.Type"/>
<rdfs:domain rdf:resource="E71.Man-Made_Thing"/>
<owl:inverseOf rdf:resource="P103I.was_intention_of"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P103I.was_intention_of -->
<owl:ObjectProperty rdf:about="P103I.was_intention_of">
<rdfs:domain rdf:resource="E55.Type"/>
<rdfs:range rdf:resource="E71.Man-Made_Thing"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P104.is_subject_to -->
<owl:ObjectProperty rdf:about="P104.is_subject_to">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property links a particular E72 Legal Object to the instances of E30 Right to which it is subject.
The Right is held by an E39 Actor as described by P75 possesses (is possessed by).
Example: Beatles back catalogue (E72) is subject to reproduction right on Beatles back catalogue (E30).</rdfs:comment>
<rdfs:range rdf:resource="E30.Right"/>
<rdfs:domain rdf:resource="E72.Legal_Object"/>
<owl:inverseOf rdf:resource="P104I.applies_to"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P104I.applies_to -->
<owl:ObjectProperty rdf:about="P104I.applies_to">
<rdfs:domain rdf:resource="E30.Right"/>
<rdfs:range rdf:resource="E72.Legal_Object"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P105.right_held_by -->
<owl:ObjectProperty rdf:about="P105.right_held_by">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E39 Actor who holds the instances of E30 Right to an E72 Legal
Object.
It is a superproperty of P52 has current owner (is current owner of) because ownership is a
right that is held on the owned object.
P105 right held by (has right on) is a shortcut of the fully developed path from E72 Legal
Object through P104 is subject to (applies to), E30 Right, P75 possesses (is possessed by) to
E39 Actor.
Example: Beatles back catalogue (E73) right held by Michael Jackson (E21)</rdfs:comment>
<rdfs:range rdf:resource="E39.Actor"/>
<rdfs:domain rdf:resource="E72.Legal_Object"/>
<owl:inverseOf rdf:resource="P105I.has_right_on"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P105I.has_right_on -->
<owl:ObjectProperty rdf:about="P105I.has_right_on">
<rdfs:domain rdf:resource="E39.Actor"/>
<rdfs:range rdf:resource="E72.Legal_Object"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P106.is_composed_of -->
<owl:ObjectProperty rdf:about="P106.is_composed_of">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property links an E73 Information Object to another E73 Information Object in a part/whole relationship.
It allows for the decomposition of an Information Object into component parts, and hence the creation of a nested hierarchy of Information Objects.
Example: "the love song of J. Alfred Prufrock" (E33) forms part of The Works of T.S. Eliot. (E33)</rdfs:comment>
<rdfs:range rdf:resource="E90.Symbolic_Object"/>
<rdfs:domain rdf:resource="E90.Symbolic_Object"/>
<owl:inverseOf rdf:resource="P106I.forms_part_of"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P106I.forms_part_of -->
<owl:ObjectProperty rdf:about="P106I.forms_part_of">
<rdfs:domain rdf:resource="E90.Symbolic_Object"/>
<rdfs:range rdf:resource="E90.Symbolic_Object"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P107.has_current_or_former_member -->
<owl:ObjectProperty rdf:about="P107.has_current_or_former_member">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property relates an E39 Actor to the E74 Group of which he or she is a member. Groups, Legal Bodies and Persons, may all be members of Groups. A Group necessarily consists of more than one member. This property is a shortcut of the more fully developed path from E74 Group through P144 joined with (gained member by), E85 Joining, P143 joined (was joined by) to E39 Actor. The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group.
Examples: Moholy Nagy (E21) is current or former member of Bauhaus (E74), National Museum of Science and Industry (E40) has current or former member The National Railway Museum (E40), The married couple Queen Elisabeth and Prince Phillip (E74) has current or former member Prince Phillip (E21) with P107.1 kind of member husband (E55 Type)</rdfs:comment>
<rdfs:range rdf:resource="E39.Actor"/>
<rdfs:domain rdf:resource="E74.Group"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P107I.is_current_or_former_member_of -->
<owl:ObjectProperty rdf:about="P107I.is_current_or_former_member_of">
<rdfs:domain rdf:resource="E39.Actor"/>
<rdfs:range rdf:resource="E74.Group"/>
<owl:inverseOf rdf:resource="P107.has_current_or_former_member"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P108.has_produced -->
<owl:ObjectProperty rdf:about="P108.has_produced">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E24 Physical Man-Made Thing that came into existence as a result of an E12 Production.
The identity of an instance of E24 Physical Man-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Man-Made Thing. Example: The building of Rome (E12) has produced The Colosseum (E22).</rdfs:comment>
<rdfs:domain rdf:resource="E12.Production"/>
<rdfs:range rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:subPropertyOf rdf:resource="P31.has_modified"/>
<rdfs:subPropertyOf rdf:resource="P92.brought_into_existence"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P108I.was_produced_by -->
<owl:ObjectProperty rdf:about="P108I.was_produced_by">
<rdfs:range rdf:resource="E12.Production"/>
<rdfs:domain rdf:resource="E24.Physical_Man-Made_Thing"/>
<owl:inverseOf rdf:resource="P108.has_produced"/>
<rdfs:subPropertyOf rdf:resource="P31I.was_modified_by"/>
<rdfs:subPropertyOf rdf:resource="P92I.was_brought_into_existence_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P109.has_current_or_former_curator -->
<owl:ObjectProperty rdf:about="P109.has_current_or_former_curator">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E39 Actor or Actors who assume or have assumed overall curatorial responsibility for an E78 Collection.
This property is effectively a short-cut. It does not allow a history of curation to be recorded. This would require use of an Event assigning responsibility for a Collection to a curator.
Example:
the Robert Opie Collection (E78) has current or former curator Robert Opie (E39).
the Mikael. Foslie’s coralline red algae Herbarium (E78) has current or former
curator Mikael Foslie</rdfs:comment>
<rdfs:range rdf:resource="E39.Actor"/>
<rdfs:domain rdf:resource="E78.Collection"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P109I.is_current_or_former_curator_of -->
<owl:ObjectProperty rdf:about="P109I.is_current_or_former_curator_of">
<rdfs:domain rdf:resource="E39.Actor"/>
<rdfs:range rdf:resource="E78.Collection"/>
<owl:inverseOf rdf:resource="P109.has_current_or_former_curator"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P10I.contains -->
<owl:ObjectProperty rdf:about="P10I.contains">
<rdfs:range rdf:resource="E4.Period"/>
<rdfs:domain rdf:resource="E4.Period"/>
<owl:inverseOf rdf:resource="P10.falls_within"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P11.had_participant -->
<owl:ObjectProperty rdf:about="P11.had_participant">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property describes the active or passive participation of instances of E39 Actors in an E5 Event.
It connects the life-line of the related E39 Actor with the E53 Place and E50 Date of the event. The property implies that the Actor was involved in the event but does not imply any causal relationship. The subject of a portrait can be said to have participated in the creation of the portrait.
Examples: Napoleon (E21) participated in The Battle of Waterloo (E7), Maria (E21) participated in Photographing of Maria (E7).</rdfs:comment>
<rdfs:range rdf:resource="E39.Actor"/>
<rdfs:domain rdf:resource="E5.Event"/>
<owl:inverseOf rdf:resource="P11I.participated_in"/>
<rdfs:subPropertyOf rdf:resource="P12.occurred_in_the_presence_of"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P110.augmented -->
<owl:ObjectProperty rdf:about="P110.augmented">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E24 Physical Man-Made Thing that is added to (augmented) in an E79 Part Addition.
Although a Part Addition event normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be added to (augmented). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.
Example: the final nail-insertion Event (E79) augmented Coffin of George VI (E24).</rdfs:comment>
<rdfs:range rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:domain rdf:resource="E79.Part_Addition"/>
<rdfs:subPropertyOf rdf:resource="P31.has_modified"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P110I.was_augmented_by -->
<owl:ObjectProperty rdf:about="P110I.was_augmented_by">
<rdfs:domain rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:range rdf:resource="E79.Part_Addition"/>
<owl:inverseOf rdf:resource="P110.augmented"/>
<rdfs:subPropertyOf rdf:resource="P31I.was_modified_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P111.added -->
<owl:ObjectProperty rdf:about="P111.added">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E18 Physical Thing that is added during an E79 Part Addition activity. Example: the insertion of the final nail (E79) added the last nail in George VI's coffin (E18).</rdfs:comment>
<rdfs:range rdf:resource="E18.Physical_Thing"/>
<rdfs:domain rdf:resource="E79.Part_Addition"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P111I.was_added_by -->
<owl:ObjectProperty rdf:about="P111I.was_added_by">
<rdfs:domain rdf:resource="E18.Physical_Thing"/>
<rdfs:range rdf:resource="E79.Part_Addition"/>
<owl:inverseOf rdf:resource="P111.added"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P112.diminished -->
<owl:ObjectProperty rdf:about="P112.diminished">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E24 Physical Man-Made Thing that was diminished by E80 Part Removal.
Although a Part removal activity normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single Part Removal activity. Example: the coffin of Tut Ankh Amun (E22) was diminished by The opening of the coffin of Tut Ankh Amun (E80).</rdfs:comment>
<rdfs:range rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:domain rdf:resource="E80.Part_Removal"/>
<rdfs:subPropertyOf rdf:resource="P31.has_modified"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P112I.was_diminished_by -->
<owl:ObjectProperty rdf:about="P112I.was_diminished_by">
<rdfs:domain rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:range rdf:resource="E80.Part_Removal"/>
<owl:inverseOf rdf:resource="P112.diminished"/>
<rdfs:subPropertyOf rdf:resource="P31I.was_modified_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P113.removed -->
<owl:ObjectProperty rdf:about="P113.removed">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E18 Physical Thing that is removed during an E80 Part Removal activity. Examples: the opening of the coffin of Tut Ankh Amun (E80) removed The mummy of Tut Ankh Amun (E20, E22).</rdfs:comment>
<rdfs:range rdf:resource="E18.Physical_Thing"/>
<rdfs:domain rdf:resource="E80.Part_Removal"/>
<owl:inverseOf rdf:resource="P113I.was_removed_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P113I.was_removed_by -->
<owl:ObjectProperty rdf:about="P113I.was_removed_by">
<rdfs:domain rdf:resource="E18.Physical_Thing"/>
<rdfs:range rdf:resource="E80.Part_Removal"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P114.is_equal_in_time_to -->
<owl:ObjectProperty rdf:about="P114.is_equal_in_time_to">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This symmetric property allows the instances of E2 Temporal Entity with the same E52 Time-Span to be equated.
This property is only necessary if the time span is unknown (otherwise the equivalence can be calculated).
This property is the same as the "equal" relationship of Allen's temporal logic (Allen, 1983, pp. 832-843).
Example: the destruction of the Villa Justinian Tempus (E6) is equal in time to the death of Maximus Venderus (E69).</rdfs:comment>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P114.is_equal_in_time_to"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P115.finishes -->
<owl:ObjectProperty rdf:about="P115.finishes">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property allows the ending point for an E2 Temporal Entity to be situated by reference to the ending point of another temporal entity of longer duration.
This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "finishes / finished-by" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843). Example: Late Bronze Age (E4) finishes Bronze Age (E4).</rdfs:comment>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P115I.is_finished_by -->
<owl:ObjectProperty rdf:about="P115I.is_finished_by">
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P115.finishes"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P116.starts -->
<owl:ObjectProperty rdf:about="P116.starts">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property allows the starting point for an E2 Temporal Entity to be situated by reference to the starting point of another temporal entity of longer duration.
This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "starts / started-by" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843).
Example: Early Bronze Age (E4) starts Bronze Age (E4).</rdfs:comment>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P116I.is_started_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P116I.is_started_by -->
<owl:ObjectProperty rdf:about="P116I.is_started_by">
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P117.occurs_during -->
<owl:ObjectProperty rdf:about="P117.occurs_during">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property allows the entire E52 Time-Span of an E2 Temporal Entity to be situated within the Time-Span of another temporal entity that starts before and ends after the included temporal entity.
This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "during / includes" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843).
Example: Middel Saxon period (E4) occurs during Saxon period (E4).</rdfs:comment>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P117I.includes"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P117I.includes -->
<owl:ObjectProperty rdf:about="P117I.includes">
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P118.overlaps_in_time_with -->
<owl:ObjectProperty rdf:about="P118.overlaps_in_time_with">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies an overlap between the instances of E52 Time-Span of two instances of E2 Temporal Entity.
It implies a temporal order between the two entities: if A overlaps in time B, then A must start before B, and B must end after A. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated).
This property is the same as the "overlaps / overlapped-by" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843).
Example: the Iron Age (E4) overlaps in time with the Roman period (E4).</rdfs:comment>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P118I.is_overlapped_in_time_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P118I.is_overlapped_in_time_by -->
<owl:ObjectProperty rdf:about="P118I.is_overlapped_in_time_by">
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P119.meets_in_time_with -->
<owl:ObjectProperty rdf:about="P119.meets_in_time_with">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property indicates that one E2 Temporal Entity immediately follows another.
It implies a particular order between the two entities: if A meets in time with B, then A must precede B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated).
This property is the same as the "meets / met-by" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843).
Example: Early Saxon Period (E4) meets in time with Middle Saxon Period (E4).</rdfs:comment>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P119I.is_met_in_time_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P119I.is_met_in_time_by -->
<owl:ObjectProperty rdf:about="P119I.is_met_in_time_by">
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P11I.participated_in -->
<owl:ObjectProperty rdf:about="P11I.participated_in">
<rdfs:domain rdf:resource="E39.Actor"/>
<rdfs:range rdf:resource="E5.Event"/>
<rdfs:subPropertyOf rdf:resource="P12I.was_present_at"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P12.occurred_in_the_presence_of -->
<owl:ObjectProperty rdf:about="P12.occurred_in_the_presence_of">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role.
It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers. Example: Deckchair 42 (E19) was present at The sinking of the Titanic (E5).</rdfs:comment>
<rdfs:domain rdf:resource="E5.Event"/>
<rdfs:range rdf:resource="E77.Persistent_Item"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P120.occurs_before -->
<owl:ObjectProperty rdf:about="P120.occurs_before">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the relative chronological sequence of two temporal entities.
It implies that a temporal gap exists between the end of A and the start of B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated).
This property is the same as the "before / after" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843).
Example: Early Bronze Age (E4) occurs before Late Bronze Age (E4).</rdfs:comment>
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P120I.occurs_after -->
<owl:ObjectProperty rdf:about="P120I.occurs_after">
<rdfs:domain rdf:resource="E2.Temporal_Entity"/>
<rdfs:range rdf:resource="E2.Temporal_Entity"/>
<owl:inverseOf rdf:resource="P120.occurs_before"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P121.overlaps_with -->
<owl:ObjectProperty rdf:about="P121.overlaps_with">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This symmetric property allows the instances of E53 Place with overlapping geometric extents to be associated with each other.
It does not specify anything about the shared area. This property is purely spatial, in contrast to Allen operators, which are purely temporal.
Example: the territory of the United States (E53) overlaps with the Arctic (E53).</rdfs:comment>
<rdfs:range rdf:resource="E53.Place"/>
<rdfs:domain rdf:resource="E53.Place"/>
<owl:inverseOf rdf:resource="P121.overlaps_with"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P122.borders_with -->
<owl:ObjectProperty rdf:about="P122.borders_with">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This symmetric property allows the instances of E53 Place which share common borders to be related as such.
This property is purely spatial, in contrast to Allen operators, which are purely temporal. Example: Scotland (E53) borders with England (E53).</rdfs:comment>
<rdfs:domain rdf:resource="E53.Place"/>
<rdfs:range rdf:resource="E53.Place"/>
<owl:inverseOf rdf:resource="P122.borders_with"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P123.resulted_in -->
<owl:ObjectProperty rdf:about="P123.resulted_in">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E77 Persistent Item or items that are the result of an E81 Transformation.
New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the link to the common Transformation.
Examples: the transformation of the Venetian Loggia in Heraklion into a city hall (E81) resulted in the City Hall of Heraklion (E22), the death and mummification of Tut Ankh Amun (E81) resulted in the Mummy of Tut Ankh Amun (E22, E20).</rdfs:comment>
<rdfs:range rdf:resource="E77.Persistent_Item"/>
<rdfs:domain rdf:resource="E81.Transformation"/>
<owl:inverseOf rdf:resource="P123I.resulted_from"/>
<rdfs:subPropertyOf rdf:resource="P92.brought_into_existence"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P123I.resulted_from -->
<owl:ObjectProperty rdf:about="P123I.resulted_from">
<rdfs:domain rdf:resource="E77.Persistent_Item"/>
<rdfs:range rdf:resource="E81.Transformation"/>
<rdfs:subPropertyOf rdf:resource="P92I.was_brought_into_existence_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P124.transformed -->
<owl:ObjectProperty rdf:about="P124.transformed">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E77 Persistent Item or items that cease to exist due to a E81 Transformation.
It is replaced by the result of the Transformation, which becomes a new unit of documentation. The continuity between both items, the new and the old, is expressed by the link to the common Transformation.
Examples: the transformation of the Venetian Loggia in Heraklion into a city hall (E81) transformed the Venetian Loggia in Heraklion (E22); the death and mummification of Tut Ankh Amun (E81) transformed the ruling Pharao Tut Ankh Amun (E21).</rdfs:comment>
<rdfs:range rdf:resource="E77.Persistent_Item"/>
<rdfs:domain rdf:resource="E81.Transformation"/>
<owl:inverseOf rdf:resource="P124I.was_transformed_by"/>
<rdfs:subPropertyOf rdf:resource="P93.took_out_of_existence"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P124I.was_transformed_by -->
<owl:ObjectProperty rdf:about="P124I.was_transformed_by">
<rdfs:domain rdf:resource="E77.Persistent_Item"/>
<rdfs:range rdf:resource="E81.Transformation"/>
<rdfs:subPropertyOf rdf:resource="P93I.was_taken_out_of_existence_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P125.used_object_of_type -->
<owl:ObjectProperty rdf:about="P125.used_object_of_type">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer". Example: at the Battle of Agincourt (E7), the English archers used object of type long bow (E55).</rdfs:comment>
<rdfs:range rdf:resource="E55.Type"/>
<rdfs:domain rdf:resource="E7.Activity"/>
<owl:inverseOf rdf:resource="P125I.was_type_of_object_used_in"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P125I.was_type_of_object_used_in -->
<owl:ObjectProperty rdf:about="P125I.was_type_of_object_used_in">
<rdfs:domain rdf:resource="E55.Type"/>
<rdfs:range rdf:resource="E7.Activity"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P126.employed -->
<owl:ObjectProperty rdf:about="P126.employed">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies E57 Material employed in an E11 Modification.
The E57 Material used during the E11 Modification does not necessarily become incorporated into the E24 Physical Man-Made Thing that forms the subject of the E11 Modification. Examples: the repairing of the Queen Mary (E11) employed Steel (E57); distilled water (E57) was employed in the restoration of the Sistien Chapel (E11).</rdfs:comment>
<rdfs:domain rdf:resource="E11.Modification"/>
<rdfs:range rdf:resource="E57.Material"/>
<owl:inverseOf rdf:resource="P126I.was_employed_in"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P126I.was_employed_in -->
<owl:ObjectProperty rdf:about="P126I.was_employed_in">
<rdfs:range rdf:resource="E11.Modification"/>
<rdfs:domain rdf:resource="E57.Material"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P127.has_broader_term -->
<owl:ObjectProperty rdf:about="P127.has_broader_term">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies a super-Type to which an E55 Type is related.
It allows Types to be organised into hierarchies. This is the sense of "broader term generic (BTG)" as defined in ISO 2788.
Example: dime (E55) has broader term coin (E55).</rdfs:comment>
<rdfs:domain rdf:resource="E55.Type"/>
<rdfs:range rdf:resource="E55.Type"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P127I.has_narrower_term -->
<owl:ObjectProperty rdf:about="P127I.has_narrower_term">
<rdfs:range rdf:resource="E55.Type"/>
<rdfs:domain rdf:resource="E55.Type"/>
<owl:inverseOf rdf:resource="P127.has_broader_term"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P128.carries -->
<owl:ObjectProperty rdf:about="P128.carries">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies an E73 Information Object carried by an instance of E24 Physical Man-Made Thing.
In general this would be an E84 Information Carrier P65 shows visual item (is shown by) is a specialisation of P128 carries (is carried by) which should be used for carrying visual items. Example: Matthew's paperback copy of Reach for the Sky (E84) carries the text of Reach for the Sky (E73).</rdfs:comment>
<rdfs:domain rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:range rdf:resource="E73.Information_Object"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P128I.is_carried_by -->
<owl:ObjectProperty rdf:about="P128I.is_carried_by">
<rdfs:range rdf:resource="E24.Physical_Man-Made_Thing"/>
<rdfs:domain rdf:resource="E73.Information_Object"/>
<owl:inverseOf rdf:resource="P128.carries"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P129.is_about -->
<owl:ObjectProperty rdf:about="P129.is_about">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies a E1 CRM Entity that is the subject of an E73 Information Object, in the sense of "aboutness" used in library science.
This differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of the E73 Information Object. Example: reach for the Sky (E73) is about Douglas Bader (E39).</rdfs:comment>
<rdfs:range rdf:resource="E1.CRM_Entity"/>
<rdfs:domain rdf:resource="E89.Propositional_Object"/>
<rdfs:subPropertyOf rdf:resource="P67.refers_to"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P129I.is_subject_of -->
<owl:ObjectProperty rdf:about="P129I.is_subject_of">
<rdfs:domain rdf:resource="E1.CRM_Entity"/>
<rdfs:range rdf:resource="E89.Propositional_Object"/>
<owl:inverseOf rdf:resource="P129.is_about"/>
<rdfs:subPropertyOf rdf:resource="P67I.is_referred_to_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P12I.was_present_at -->
<owl:ObjectProperty rdf:about="P12I.was_present_at">
<rdfs:range rdf:resource="E5.Event"/>
<rdfs:domain rdf:resource="E77.Persistent_Item"/>
<owl:inverseOf rdf:resource="P12.occurred_in_the_presence_of"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P13.destroyed -->
<owl:ObjectProperty rdf:about="P13.destroyed">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property allows specific instances of E18 Physical Thing that have been destroyed to be related to a destruction event.
Destruction implies the end of an item's life as a subject of cultural documentation - the physical matter of which the item was composed may in fact continue to exist. A destruction event may be contiguous with a Production that brings into existence a derived object composed partly of matter from the destroyed object. Example: the Tay Bridge Desaster (E6) destroyed The Tay Bridge (E22).</rdfs:comment>
<rdfs:range rdf:resource="E18.Physical_Thing"/>
<rdfs:domain rdf:resource="E6.Destruction"/>
<rdfs:subPropertyOf rdf:resource="P93.took_out_of_existence"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P130.shows_features_of -->
<owl:ObjectProperty rdf:about="P130.shows_features_of">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established.
Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Example: the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British Museum (E22). Kind of similiarity: Copy (E55).</rdfs:comment>
<rdfs:range rdf:resource="E70.Thing"/>
<rdfs:domain rdf:resource="E70.Thing"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P130I.features_are_also_found_on -->
<owl:ObjectProperty rdf:about="P130I.features_are_also_found_on">
<rdfs:range rdf:resource="E70.Thing"/>
<rdfs:domain rdf:resource="E70.Thing"/>
<owl:inverseOf rdf:resource="P130.shows_features_of"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P131.is_identified_by -->
<owl:ObjectProperty rdf:about="P131.is_identified_by">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies a name used specifically to identify an E39 Actor.
This property is a specialisation of P1 is identified by (identifies). Example: Tyler Withersopp IV (E39) is identified by US social security number 619-17-4204 (E82).</rdfs:comment>
<rdfs:domain rdf:resource="E39.Actor"/>
<rdfs:range rdf:resource="E82.Actor_Appellation"/>
<rdfs:subPropertyOf rdf:resource="P1.is_identified_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P131I.identifies -->
<owl:ObjectProperty rdf:about="P131I.identifies">
<rdfs:range rdf:resource="E39.Actor"/>
<rdfs:domain rdf:resource="E82.Actor_Appellation"/>
<owl:inverseOf rdf:resource="P131.is_identified_by"/>
<rdfs:subPropertyOf rdf:resource="P1I.identifies"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P132.overlaps_with -->
<owl:ObjectProperty rdf:about="P132.overlaps_with">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This symmetric property allows instances of E4 Period that overlap both temporally and spatially to be related, i.e. they share some spatio-temporal extent.
This property does not imply any ordering or sequence between the two periods, either spatial or temporal.
Example: the "Urnfield" period (E4) overlaps with the "Hallstatt" period (E4).</rdfs:comment>
<rdfs:domain rdf:resource="E4.Period"/>
<rdfs:range rdf:resource="E4.Period"/>
<owl:inverseOf rdf:resource="P132.overlaps_with"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P133.is_separated_from -->
<owl:ObjectProperty rdf:about="P133.is_separated_from">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This symmetric property allows instances of E4 Period that do not overlap both temporally and spatially, to be related i,e. they do not share any spatio-temporal extent.
This property does not imply any ordering or sequence between the two periods either spatial or temporal.
Example: the "Hallstatt" period (E4) is separated from the "La Tene" era (E4).</rdfs:comment>
<rdfs:domain rdf:resource="E4.Period"/>
<rdfs:range rdf:resource="E4.Period"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P134.continued -->
<owl:ObjectProperty rdf:about="P134.continued">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property allows two activities to be related where the domain is considered as an intentional continuation of the range.
Used multiple times, this allows a chain of related activities to be created which follow each other in sequence.
Example: the construction of the Koelner Dom (Cologne Cathedral) (E7) abandoned in the 15th century, was continued by construction in the 19th century adapting the initial plans so as to preserve the intended appearance (E7).</rdfs:comment>
<rdfs:range rdf:resource="E7.Activity"/>
<rdfs:domain rdf:resource="E7.Activity"/>
<rdfs:subPropertyOf rdf:resource="P15.was_influenced_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P134I.was_continued_by -->
<owl:ObjectProperty rdf:about="P134I.was_continued_by">
<rdfs:domain rdf:resource="E7.Activity"/>
<rdfs:range rdf:resource="E7.Activity"/>
<owl:inverseOf rdf:resource="P134.continued"/>
<rdfs:subPropertyOf rdf:resource="P15I.influenced"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P135.created_type -->
<owl:ObjectProperty rdf:about="P135.created_type">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies the E55 Type, which is created in an E83 Type Creation activity. Example: The description of a new ribbon worm species by Bürger (E83) created type 'Lineus coxinus (Bürger, 1892)' (E55).</rdfs:comment>
<rdfs:range rdf:resource="E55.Type"/>
<rdfs:domain rdf:resource="E83.Type_Creation"/>
<owl:inverseOf rdf:resource="P135I.was_created_by"/>
<rdfs:subPropertyOf rdf:resource="P94.has_created"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P135I.was_created_by -->
<owl:ObjectProperty rdf:about="P135I.was_created_by">
<rdfs:domain rdf:resource="E55.Type"/>
<rdfs:range rdf:resource="E83.Type_Creation"/>
<rdfs:subPropertyOf rdf:resource="P94I.was_created_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P136.was_based_on -->
<owl:ObjectProperty rdf:about="P136.was_based_on">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property identifies one or more items that were used as evidence to declare a new E55 Type.
The examination of these items is often the only objective way to understand the precise characteristics of a new Type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the Type, such as "holotype" or "original element". Example: the taxon creation of the plant species 'Serratula glauca Linne, 1753.' (E83) was based on Object BM000576251 of the Clayton Herbarium (E20) in the taxonomic role original element (E55).</rdfs:comment>
<rdfs:range rdf:resource="E1.CRM_Entity"/>
<rdfs:domain rdf:resource="E83.Type_Creation"/>
<rdfs:subPropertyOf rdf:resource="P15.was_influenced_by"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P136I.supported_type_creation -->
<owl:ObjectProperty rdf:about="P136I.supported_type_creation">
<rdfs:domain rdf:resource="E1.CRM_Entity"/>
<rdfs:range rdf:resource="E83.Type_Creation"/>
<owl:inverseOf rdf:resource="P136.was_based_on"/>
<rdfs:subPropertyOf rdf:resource="P15I.influenced"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P137.exemplifies -->
<owl:ObjectProperty rdf:about="P137.exemplifies">
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>This property allows an item to be declared as a particular example of an E55 Type or taxon.
The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows
differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this
example to the Type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic
role "lectotype" is not associated with the Type Creation (E83) itself, but selected in a later
phase.
Examples:
- Object BM000098044 of the Clayton Herbarium (E20) exemplifies Spigelia marilandica
(L.) L. (E55) in the taxonomic role lectotype</rdfs:comment>
<rdfs:range rdf:resource="E1.CRM_Entity"/>
<rdfs:domain rdf:resource="E55.Type"/>
<rdfs:subPropertyOf rdf:resource="P2.has_type"/>
</owl:ObjectProperty>
<!-- http://erlangen-crm.org/091125/P137I.is_exemplified_by -->