-
Notifications
You must be signed in to change notification settings - Fork 13
/
Copy pathecrm_101001-fu.owl
5385 lines (4950 loc) · 323 KB
/
ecrm_101001-fu.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:xsp="http://www.owl-ontologies.com/2005/08/07/xsp.owl#"
xmlns:ecrm="http://erlangen-crm.org/101001/"
xmlns:swrlb="http://www.w3.org/2003/11/swrlb#"
xmlns:swrl="http://www.w3.org/2003/11/swrl#"
xmlns:protege="http://protege.stanford.edu/plugins/owl/protege#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xml:base="http://erlangen-crm.org/101001/">
<owl:Ontology rdf:about="">
<rdfs:label xml:lang="en">Erlangen CRM / OWL</rdfs:label>
<owl:versionInfo rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>ECRM 101001 / CIDOC-CRM 5.0.2 January 2010 Edition</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) 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. It is currently maintained by Martin Scholz, Georg Hohmann and Mark Fichtner. All writes reserved.</rdfs:comment>
<rdfs:comment xml:lang="en">Changelog
ECRM 101001 (Georg Hohmann)
- Removed all Primitive Values (E59, E60, E61, E62) due to new considerations about the handling of data values in the CRM. All object properties with range E59_Primitve_Value and subclasses have been replaced by datatype properties with any range (detailed documentation in progress).
- Added "xml:lang=en" to each comment and label.
- Removed unnecesary line breaks in all rdf:comments to enhance readability and automatic processing.
- Replaced capital "I" with lower case "i" as suffix for inverse properties.
- Removed dots and semicolons from the list items of all rdf:comments. All list items in the "examples" and "functional units" section are now terminated by a line break only.
ECRM 100707 (Fabian Schmidt / Martin Scholz)
- Replaced "." with "_" in Labels of Entities and Properties (e.g. E1_CRM_Entity instead of E1.CRM_Entity) to support turtle.
- Added Functional units to rdfs:comments of Entities and Properties according to http://www.cidoc-crm.org/cidoc_graphical_representation_v_5_1/graphical_representaion_5_0_1.html .
ECRM 100408 (Fabian Schmidt / Martin Scholz)
- All scope notes and examples have been revised and updated according to CIDOC CRM Version 5.0.2 January 2010.
- Comments have been reformatted: The scope notes are preceeded by the term "Scope note:". Examples are preceeded by the word "Examples:" and each example will start a new line. Examples are separated by semicolon. A dot terminates the example list.
ECRM 100323 (Martin Scholz)
- E41_Appellation is no longer a subclass of E62_String. Now, the preferred way to attach a string to an appellation is to use an extension that provides E41_Appellation with an appropriate datatype property (such as has_XSD_String).
- Changes in comments according to amendments and proofreading of CIDOC CRM Version 5.0.2 (pp. 129-133).
- Examples changed in the comments have been reformatted for better readability: The word "Examples:" and each following example will start a new line. Examples are separated by semicolon.
ECRM 100302
- P67: scope note updated.
- P129: scope note updated.
- DataTypeProperties of subclasses of E59_PrimitiveValue have been removed. The pure ECRM will no longer provide any specific means to represent primitive values in a data type format (like XSD till now). Instead, derived ontologies may introduce adequate properties. The ECRM as such is not bound to a specific domain nor underlying implementation (apart from OWL). Therefore the decision in favour of a data type format is not made here. The implementation of the primitive value concepts (E59-E62) as OWL classes is kept, though, to ensure compatibility / expressiveness between subontologies with different data type formats.</rdfs:comment>
</owl:Ontology>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E56_Language">
<rdfs:comment xml:lang="en">Scope note:
This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts.
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 E56 Language, e.g.: “instances of Mandarin Chinese”.
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
Example:
el [Greek]
- en [English]
- eo [Esperanto]
- es [Spanish]
- fr [French]
Functional units:
- 15. Mark and Inscription Information
- 24. Object Title Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E55_Type"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E26_Physical_Feature">
<rdfs:comment xml:lang="en">Scope note:
This class comprises identifiable features that are physically attached in an integral way to particular physical objects.
Instances of E26 Physical Feature share many of the attributes of instances of E19 Physical Object. They may have a one-, two- or three-dimensional geometric extent, but there are no natural borders that separate them completely in an objective way from the carrier objects. For example, a doorway is a feature but the door itself, being attached by hinges, is not.
Instances of E26 Physical Feature can be features in a narrower sense, such as scratches, holes, reliefs, surface colours, reflection zones in an opal crystal or a density change in a piece of wood. In the wider sense, they are portions of particular objects with partially imaginary borders, such as the core of the Earth, an area of property on the surface of the Earth, a landscape or the head of a contiguous marble statue. They can be measured and dated, and it is sometimes possible to state who or what is or was responsible for them. They cannot be separated from the carrier object, but a segment of the carrier object may be identified (or sometimes removed) carrying the complete feature.
This definition coincides with the definition of "fiat objects" (Smith & Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”.
Examples:
- the temple in Abu Simbel before its removal
- Albrecht Duerer's signature on his painting of Charles the Great
- the damage to the nose of the Great Sphinx in Giza
- Michael Jackson's nose prior to plastic surgery
Functional units:
- 15. Mark and Inscription Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E18_Physical_Thing"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P56i_is_found_on"/>
</owl:onProperty>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E73_Information_Object">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E89_Propositional_Object"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E90_Symbolic_Object"/>
</rdfs:subClassOf>
<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.
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
- E. A. Poe's "The Raven"
- the movie "The Seven Samurai" by Akira Kurosawa
- the Maxwell Equations
Functional units:
- 9. Documentation and References
- 12. Image Information, Objects and Carriers
- 15. Mark and Inscription Information
- 24. Object Title Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E74_Group">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E39_Actor"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P107_has_current_or_former_member"/>
</owl:onProperty>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>2</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P95i_was_formed_by"/>
</owl:onProperty>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>0</owl:minCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P146i_lost_member_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P144i_gained_member_by"/>
</owl:onProperty>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>2</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises any gatherings or organizations of two or more people that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country.
A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modeled as membership in an E74 Group (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group.
Examples:
- the impressionists
- the Navajo
- the Greeks
- the peace protestors in NYC on February 15 2003
- Exxon-Mobil
- King Solomon and his wives
- the President of the Swiss Confederation
Functional units:
- 10. Existence Information
- 11. Group Dynamics
- 13. Institution Information
- 26. Person Nationality Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E52_Time-Span">
<rdfs:comment xml:lang="en">Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- from 12-17-1993 to 12-8-1996
- 14h30 - 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
Functional units:
- 1. Acquisition Information
- 6. Condition Information
- 7. Deaccession and Disposal Information
- 18. Object Association Information
- 19. Object Collection Information
- 20. Object Entry Information
- 22. Object Number Information
- 23. Object Production Information
- 28. Recorder Information
- 31. Spatial-Temporal Relationship
- 34. Time-Span Information</rdfs:comment>
<owl:disjointWith>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E53_Place"/>
</owl:disjointWith>
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P84_had_at_most_duration"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P4i_is_time-span_of"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E2_Temporal_Entity"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P83_had_at_least_duration"/>
</owl:onProperty>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E1_CRM_Entity"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/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
Functional units:
- 1. Acquisition Information
- 7. Deaccession and Disposal Information;</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E7_Activity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:minCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P24_transferred_title_of"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E4_Period">
<rdfs:comment xml:lang="en">Scope note:
This class comprises sets of coherent phenomena or cultural manifestations bounded in time and space.
It is the social or physical coherence of these phenomena that identify an E4 Period and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area as a sedentary culture.
Typically this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”. There are however 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.
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 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
Functional units:
- 14. Location Information
- 18. Object Association Information
- 23. Object Production Information
- 26. Person Nationality Information
- 34. Time-Span Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E2_Temporal_Entity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P9i_forms_part_of"/>
</owl:onProperty>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E53_Place"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P7_took_place_at"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E78_Collection">
<rdfs:comment xml:lang="en">Scope note:
This class comprises aggregations of instances of E18 Physical Thing that are assembled and maintained (“curated” and “preserved,” in museological terminology) by one or more instances of E39 Actor over time for a specific purpose and audience, and according to a particular collection development plan.
Items may be added or removed from an E78 Collection in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Collection often referred to with the name of the E78 Collection (e.g. “The Wallace Collection decided…”).
Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.
Examples:
- The John Clayton Herbarium
- the Wallace Collection
- Mikael Heggelund Foslie’s coralline red algae Herbarium at Museum of Natural History
and Archaeology, Trondheim, Norway
Functional units:
- 1. Acquisition Information
- 5. Collection Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E24_Physical_Man-Made_Thing"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P109_has_current_or_former_curator"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E39_Actor"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E53_Place">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E1_CRM_Entity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P59i_is_located_on_or_within"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter.
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance.
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.
Examples:
- the extent of the UK in the year 2003
- the position of the hallmark on the inside of my wedding ring
- the place referred to in the phrase: "Fish collected at three miles north of the confluence of the Arve and the Rhone"
- Here -> <-
Functional units:
- 2. Appellation Information
- 5. Collection Information
- 13. Institution Information
- 14. Location Information
- 15. Mark and Inscription Information
- 18. Object Association Information
- 19. Object Collection Information
- 23. Object Production Information
- 26. Person Nationality Information
- 31. Spatial-Temporal Relationship
- 32. Subject Depicted Information
- 34. Time-Span Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E58_Measurement_Unit">
<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]
Functional units:
- 17. Measurement Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E55_Type"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P91i_is_unit_of"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E54_Dimension"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E19_Physical_Object">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E18_Physical_Thing"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P55_has_current_location"/>
</owl:onProperty>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P54_has_current_permanent_location"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<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
Functional units:
- 14. Location Information
- 15. Mark and Inscription Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E82_Actor_Appellation">
<rdfs:comment xml:lang="en">Scope note:
This class comprises any sort of name, number, code or symbol characteristically used to identify an E39 Actor.
An E39 Actor will typically have more than one E82 Actor Appellation, and instances of E82 Actor Appellation in turn may have alternative representations. The distinction between corporate and personal names, which is particularly important in library applications, should be made by explicitly linking the E82 Actor Appellation to an instance of either E21 Person or E74 Group/E40 Legal Body. If this is not possible, the distinction can be made through the use of the P2_has type mechanism.
Examples:
- “John Doe”
- “Doe, J”
- “the U.S. Social Security Number 246-14-2304”
- “the Artist Formerly Known as Prince”
- “the Master of the Flemish Madonna”
- “Raphael’s Workshop”
- “the Brontë Sisters”
- “ICOM”
- “International Council of Museums”
Functional units:
- 2. Appellation Information
- 13. Institution Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E41_Appellation"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E31_Document">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P70_documents"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E1_CRM_Entity"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/101001/E73_Information_Object"/>
<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 photo of the Allied Leaders at Yalta published by the UPI, 1945
- the Doomsday Book
Functional units:
- 9. Documentation and References
- 28. Recorder Information
- 29. Reference Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E64_End_of_Existence">
<rdfs:comment xml:lang="en">Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Functional units:
- 4. Changing Thing
- 10. Existence Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E5_Event"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P93_took_out_of_existence"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E77_Persistent_Item"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E38_Image">
<rdfs:comment xml:lang="en">Scope note:
This class comprises distributions of form, tone and colour that may be found on surfaces such as photos, paintings, prints and sculptures or directly on electronic media.
The degree to which variations in the distribution of form and colour affect the identity of an instance of E38 Image depends on a given purpose. The original painting of the Mona Lisa in the Louvre may be said to bear the same instance of E38 Image as reproductions in the form of transparencies, postcards, posters or T-shirts, even though they may differ in size and carrier and may vary in tone and colour. The images in a “spot the difference” competition are not the same with respect to their context, however similar they may at first appear.
Examples:
- the front side of all 20 Frs notes
- the image depicted on all reproductions of the Mona Lisa
Functional units:
- 12. Image Information, Objects and Carriers
- 15. Mark and Inscription Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E36_Visual_Item"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E70_Thing">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E77_Persistent_Item"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This general class comprises usable discrete, identifiable, instances of E77 Persistent Item that are documented as single units.
They can be either intellectual products or physical things, and are characterized by relative stability. They may for instance either have a solid physical form, an electronic encoding, or they may be logical concept or structure.
Examples:
- my photograph collection (E78 Collection)
- 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 non-smoking sign (E36)
- the cave of Dirou, Mani, Greece (E27)
Functional units:
- 15. Mark and Inscription Information
- 17. Measurement Information
- 18. Object Association Information
- 23. Object Production Information
- 24. Object Title Information
- 27. Planned Activities (design, purpose, use)
- 30. Reproduction Rights Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E67_Birth">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E63_Beginning_of_Existence"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P96_by_mother"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E21_Person"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E21_Person"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P97_from_father"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Functional units:
- 10. Existence Information
- 26. Person Nationality Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E72_Legal_Object">
<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).
Functional units:
30. Reproduction Rights Information</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/101001/E70_Thing"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E39_Actor"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P105_right_held_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E30_Right"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P104_is_subject_to"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E32_Authority_Document">
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/101001/E31_Document"/>
<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
- CIDOC Conceptual Reference Model
Functional units:
- 9. Documentation and References
- 21. Object Name and Classification Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E29_Design_or_Procedure">
<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 P6_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 standardatisation procedure
- the musical notation of Beethoven's "Ode to Joy"
- the architectal 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
Functional units:
- 6. Condition Information
- 9. Documentation and References
- 16. Material and Technique Information
- 17. Measurement Information
- 27. Planned Activities (design, purpose, use)</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/101001/E73_Information_Object"/>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E55_Type">
<rdfs:comment xml:lang="en">Scope note:
This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P1_7 has broader term (has narrower term). Such hierarchies may be extended with additional properties.
Examples:
- weight, length, depth [types of E54 Dimension]
- portrait, sketch, animation [types of E38 image]
- French, English, German [E56]
- excellent, good, poor [types of E3 Condition State]
- Ford Model T, chop stick [types of E22 Man-Made Object]
- cave, doline, scratch [types of E26 Physical Feature]
- poem, short story [types of E33 Linguistic Object]
- wedding, earthquake, skirmish [types of E5 Event]
Functional units:
- 1. Acquisition Information
- 3. Attribute Assignement
- 6. Condition Information
- 7. Deaccession and Disposal Information
- 9. Documentation and References
- 14. Location Information
- 15. Location Information
- 16. Material and Technique Information
- 17. Measurement Information
- 18. Object Association Information
- 19. Object Collection Information
- 20. Object Entry Information
- 21. Object Name and Classification Information
23. Object Production Information
- 24. Object Title Information
- 26. Person Nationality Information
- 27. Planned Activities (design, purpose, use)
- 30. Reproduction Rights Information
- 32. Subject Depicted Information
- 33. Taxonomic Discourse</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E28_Conceptual_Object"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P135i_was_created_by"/>
</owl:onProperty>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E15_Identifier_Assignment">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E13_Attribute_Assignment"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E42_Identifier"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P37_assigned"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. An E15 Identifier Assignment may include the creation of the identifier from multiple constituents, which themselves may be instances of E41 Appellation. The syntax and kinds of constituents to be used may be declared in a rule constituting an instance of E29 Design or Procedure.
Examples of such identifiers include Find Numbers, Inventory Numbers, uniform titles in the sense of librarianship and Digital Object Identifiers (DOI). Documenting the act of identifier assignment and deassignment is especially useful when objects change custody or the identification system of an organization is changed. In order to keep track of the identity of things in such cases, it is important to document by whom, when and for what purpose an identifier is assigned to an item.
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P4_ has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2_has type property.
Examples:
- replacement of the inventory number TA959a by GE34604 for a 17th century lament cloth at the Museum Benaki, Athens;
assigning the author-uniform title heading "Goethe, Johann Wolfgang von, 1749-1832.Faust. 1. Theil." for a work (E28);
on June 1, 2001 assigning the personal name heading "Guillaume, de Machaut, ca. 1300-1377" (E42,E82) to Guillaume de Machaut (E21)
Functional units:
- 22. Object Number Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E18_Physical_Thing">
<rdfs:subClassOf>
<owl:Restriction>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:maxCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P13i_was_destroyed_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom rdf:resource="http://erlangen-crm.org/101001/E53_Place"/>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P53_has_former_or_current_location"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E57_Material"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P45_consists_of"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/101001/E72_Legal_Object"/>
<owl:disjointWith>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E28_Conceptual_Object"/>
</owl:disjointWith>
<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.
The 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)
Functional units:
- 1. Acquisition Information
- 4. Changing Thing
- 5. Collection Information
- 6. Condition Information
- 7. Deaccession and Disposal Information
- 10. Existence Information
- 14. Location Information
- 15.Mark and Inscription Information
- 16. Material and Technique Information
- 19. Object Collection Information
- 20. Object Entry Information
- 32. Subject Depicted Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E69_Death">
<rdfs:subClassOf rdf:resource="http://erlangen-crm.org/101001/E64_End_of_Existence"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P100_was_death_of"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E21_Person"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<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
Functional units:
- 10. Existence Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E75_Conceptual_Object_Appellation">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E41_Appellation"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises all appellations specific to intellectual products or standardized patterns.
Examples:
- “ISBN 3-7913-1418-1”
- “ISO 2788-1986 (F)”
Functional units:
- 2. Appellation Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E12_Production">
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E11_Modification"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E24_Physical_Man-Made_Thing"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P108_has_produced"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E63_Beginning_of_Existence"/>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">Scope note:
This class comprises activities that are designed to, and succeed in, creating one or more new items.
It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one.
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
Examples:
the construction of the SS Great Britain
- the first casting from the Little Mermaid at the harbour of Copenhagen
- Rembrandt’s creating of the seventh state of his etching "Woman sitting half dressed beside a stove",
1658, identified by Bartsch Number 197 (E12,E65,E81)
Functional units:
- 4. Changing Thing
- 10. Existence Information
- 14. Location Information
- 16. Material and Technique Information
- 32. Object Production Information</rdfs:comment>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E21_Person">
<rdfs:comment xml:lang="en">Scope note:
This class comprises real persons who live or are assumed to have lived.
Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CRM does not propose a specific form to support reasoning about possible identity.
Examples:
- Tut-Ankh-Amun
- Nelson Mandela
Functional units:
- 10. Existence Information
- 13. Institution Information
- 26. Person Nationality Information
- 32. Subject Depicted Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E20_Biological_Object"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P98i_was_born"/>
</owl:onProperty>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E39_Actor"/>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E89_Propositional_Object">
<rdfs:comment xml:lang="en">Scope note:
This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or mental things and that are documented as single units or serve as topic of discourse.
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
Examples:
- Maxwell’s Equations
- the ideational contents of Aristotle’s book entitled ‘Metaphysics’ as rendered in the
Greek texts translated in … Oxford edition…
- the underlying prototype of any “no-smoking” sign (E36)
- the common ideas of the plots of the movie "The Seven Samurai" by Akira Kurosawa and
the movie “The Magnificent Seven” by John Sturges
- the image content of the photo of the Allied Leaders at Yalta 1945 (E38)
Functional units:
- 9. Documentation and References
- 12. Image Information, Objects and Carriers
- 28. Recorder Information
- 29. Reference Information
- 30. Reproduction Rights Information
- 32. Subject Depicted Information</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E28_Conceptual_Object"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P129i_is_subject_of"/>
</owl:onProperty>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E1_CRM_Entity"/>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P148_has_component"/>
</owl:onProperty>
<owl:someValuesFrom rdf:resource="http://erlangen-crm.org/101001/E89_Propositional_Object"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:someValuesFrom>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E1_CRM_Entity"/>
</owl:someValuesFrom>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P67i_is_referred_to_by"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E86_Leaving">
<rdfs:comment xml:lang="en">Scope note:
This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party.
Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position.
Examples:
- the end of Sir Isaac Newton’s duty as Member of Parliament for the University of Cambridge to the Convention Parliament in 1702; George Washington’s leaving office in 1797
Functional units:
- 11. Group Dynamics</rdfs:comment>
<rdfs:subClassOf>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E7_Activity"/>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:minCardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P146_separated_from"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:cardinality>
<owl:onProperty>
<owl:ObjectProperty rdf:about="http://erlangen-crm.org/101001/P145_separated"/>
</owl:onProperty>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E79_Part_Addition">
<owl:disjointWith>
<owl:Class rdf:about="http://erlangen-crm.org/101001/E80_Part_Removal"/>
</owl:disjointWith>
<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.