-
Notifications
You must be signed in to change notification settings - Fork 1
/
cidoc.xml
4938 lines (4844 loc) · 424 KB
/
cidoc.xml
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
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:owl="http://www.w3.org/2002/07/owl#" xml:lang="en" xml:base="http://www.cidoc-crm.org/cidoc-crm/">
<!--
CIDOC CRM v7.1.1 implemented in RDFS
This is the implementation approved by the 51st CRM-SIG meeting (October 2021)
as the current RDFS version for the CIDOC CRM namespace.
Note that this is NOT a definition of the CIDOC CRM, but a CIDOC CRM compatible implementation
of an RDF Schema derived from the authoritative release of the CIDOC CRM v7.1.1 on May 2021
https://cidoc-crm.org/Version/version-7.1.1 by an automated algorithm. It is intended for an
assumed majority of uses. Depending on the application, users may create adequate extensions
compatible with the logical definitions of the CIDOC CRM.
Created by FORTH-ICS Thursday November 25, 2021
CC BY 4.0 https://creativecommons.org/licenses/by/4.0/legalcode
Updated on: Wednesday May 11, 2022
==========================
- Detected and corrected the direction of the subPropertyOf relationship between properties P161 and P67, as it has been specified in the 53rd SIG meeting that it is just a typographical error.
- Corrected typographical errors in comments.
- Improved scope notes parsing procedure.
- Corrected Class names in comment about the RDFs generation policies.
Encoding Rules:
1. The RDF spelling rules do not allow blanks. Hence we have replaced them by underscores.
For instance "E63_Beginning_of_Existence" or "P2i_is_type_of".
2. RDF does not allow to instantiate properties beginning from a range value.
Therefore, each CRM property is represented as two RDFS properties.
For instance "P2 has type (is type of)" is represented as:
"P2_has_type" for the domain to range direction and "P2i_is_type_of" for the range to domain direction.
3. The primitive values "E60 Number", "E61 Time Primitive", "E62 String", "E94 Space Primitive" and
"E95 Spacetime Primitive" referred in the Model for formal completeness are interpreted as rdfs:literal.
4. RDF does not support properties of properties, therefore, users may create their own
subProperties for CRM properties that have a type property such as "P3 has note":
Instead of P3 has note (P3-1 has type : parts description) declare
<rdf:Property rdf:about="P3_parts_description">
<rdfs:domain rdf:resource="E1_CRM_Entity"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:subPropertyOf rdf:resource="P3_has_note"/>
</rdf:Property>
5. Scope notes are represented as <rdfs:comment> elements.
6. In addition this encoding contains labels in languages different from English,
which are taken from translations of previous versions of the CIDOC CRM.
7. Any other differences in labels, scope notes and semantic relationships of this encoding
to the authoritative definition of the CIDOC CRM v7.1.1 (May 2021) are not intended transfer errors.
FORTH appreciates your feed-back on such errors.
8. CRM time extension 1.0 Encoded in RDFS (http://old.cidoc-crm.org/docs/How_to%20implement%20CRM_Time_in%20RDF.pdf)
Since the Time Primitive of the CRM can not directly be implemented in RDF Triple Stores, we define in this extension
of 4 properties replacing P81 and P82 adequately using xsd:dateTime.
Property P81 is dedicated for modeling the Time-Span's maximum known temporal extent i.e. ongoing_throughout.
Property P82 is for modeling the minimum outer bounds of events i.e. at_some_time_within.
P81 has its time interval redefined by P81a and P81b. Similarly, we redefine P82 by P82a and P82b.
-->
<!--
## RDFS Generation Policies
### Sources
Policies followed for the RDFS implementation of CIDOC v.7.1.1 were created w.r.t.:
- Implementing the CIDOC Conceptual Reference Model in RDF (http://www.cidoc-crm.org/Resources/implementing-the-cidoc-conceptual-reference-model-in-rdf)
- How to implement CRM Time in RDF (http://old.cidoc-crm.org/docs/How_to%20implement%20CRM_Time_in%20RDF.pdf)
- CIDOC-CRM SIG feedback and the general guidelines:
- Each property is declared twice, forward and backwards, unless no inverse name is defined in parentheses, or domain or range is interpreted as literal
- All Primitive Values become rdfs:Literal
- All IsA declarations from/to and between Primitive values are ignored
### Policies
#### **A. CIDOC Classes implementation in RDFS**
The CIDOC-CRM model defines classes, that in Triple Stores are typically implemented as primitive values. These classes are all subclasses of `E59 Primitive Value` and in RDFS they are interpreted as Literal. There are some classes in the CIDOC-CRM model that are both subclasses of `E59 Primitive Value` and E41 Appellation. So far we have followed the decision by CRM-SIG in "Issue 394: Solution for Dualism of E41 Appellation and rdfs:label" in 28-11-2018 wrt the question whether these classes should be implemented as rdfs:Class or still be interpreted as rdfs:Literal.
In this version we have followed the following policy regarding CIDOC Classes implementation in RDFS:
> A1. CIDOC Classes that are subClasses of `E59 Primitive Value` are interpreted as rdfs:Literal regardless of whether they are also subClasses of another Class.
As a result, the following CIDOC classes were not defined in RDFS:
- `E59 Primitive Value`
- `E60 Number`
- `E61 Time Primitive`
- `E62 String`
- `E94 Space Primitive`
- `E95 Spacetime Primitive`
Additionally, the following isA relationships were not defined in RDFS:
- `E59 Primitive Value` `subClassOf` `E1 CRM Entity`
- `E60 Number` `subClassOf` `E59 Primitive Value`
- `E61 Time Primitive` `subClassOf` `E41 Appellation`
- `E61 Time Primitive` `subClassOf` `E59 Primitive Value`
- `E62 String` `subClassOf` `E59 Primitive Value`
- `E94 Space Primitive` `subClassOf` `E41 Appellation`
- `E94 Space Primitive` `subClassOf` `E59 Primitive Value`
- `E95 Spacetime Primitive` `subClassOf` `E41 Appellation`
- `E95 Spacetime Primitive` `subClassOf` `E59 Primitive Value`
#### **B. CIDOC Properties implementation in RDFS**
The decisions in policy A affect the implementation of CIDOC Properties in RDFS. A property cannot define an rdfs:Literal as rdfs:domain, and the backwards direction of a property with an rdfs:Literal as rdfs:range cannot be created for the exact same reason.
Further, the property ranges defined as rdfs:Literal in this implementation do not inherit the properties of the superclasses defined in the CIDOC Model. A separate guideline will describe how to instantiate such properties if at all needed.
Another aspect considered for the implementation of properties in RDFS is whether a distinct inverse property definition should be provided.
In this version we followed the following policies regarding CIDOC Properties implementation in RDFS:
> B1. CIDOC Property backwards/inverse direction is **not** defined, whenever no inverse name for the property has been specified in parentheses in the official CIDOC documentation and property domain is not equal with property range.
As a result, the following properties do not define an inverse direction.
- `E1 CRM Entity. P3 has note: E62 String`
- `E19 Physical Object. P57 has number of parts: E60 Number`
- `E52 Time-Span. P79 beginning is qualified by: E62 String`
- `E52 Time-Span. P80 end is qualified by: E62 String`
- `E52 Time-Span. P81 ongoing throughout: E61 Time Primitive`
- `E52 Time-Span. P82 at some time within: E61 Time Primitive`
- `E54 Dimension. P90 has value: E60 Number`
- `E53 Place. P171 at some place within: E94 Space Primitive`
- `E53 Place. P172 contains: E94 Space Primitive`
- `E90 Symbolic Object. P190 has symbolic content: E62 String`
> B2. CIDOC Property forward direction is **not** defined whenever property domain is interpreted as rdfs:Literal (A.1). Similarly, CIDOC Property backwards/inverse direction is **not** defined, whenever property range is interpreted as rdfs:Literal (A.1). Further, the instances of classes interpreted as rdfs:Literal, cannot express in RDFs their **inherited** properties that could be expressed according to CIDOC Model.
As a result,
a) The following **direct forward direction** CIDOC Properties **cannot** be expressed and are **not defined** in RDFS:
- `E95 Spacetime Primitive. P169 defines spacetime volume (spacetime volume is defined by): E92 Spacetime Volume`
- `E61 Time Primitive. P170 defines time (time is defined by): E52 Time-Span`
b) The following **direct backwards direction** CIDOC Properties **cannot** be expressed and are **not defined** in RDFS:
- `E94 Space Primitive. P168i defines place (place is defined by): E53 Place`
> B3. Whenever no backwards/inverse property name is specified and property domain matches with property range, then the forward/direct property direction should be used for **both** directions and **no backwards/inverse property** needs to be defined.
As a result, we did not implement a separate backwards/inverse direction for the following CIDOC Properties:
- `E53 Place. P121 overlaps with: E53 Place`
- `E53 Place. P122 borders with: E53 Place`
- `E92 Spacetime Volume. P132 spatiotemporally overlaps with: E92 Spacetime Volume`
- `E92 Spacetime Volume. P133 is spatiotemporally separated from: E92 Spacetime Volume`
- `E41 Appellation. P139 has alternative form: E41 Appellation`
Additionally, all aforementioned redundant backwards/inverse CIDOC Property direction references, are replaced by the respective direct/forward CIDOC Property direction.
- The hierarchical link of `P10i` subPropertyOf `P132i` was replaced with `P10i` subPropertyOf `P132`.
#### **C. Labels and appellations**
CIDOC-CRM version 7.1.1 defines the below subpropertyOf relations:
- `P168 place is defined by` `subPropertyOf` `P1 is identified by`
- `P169i spacetime volume is defined by` `subPropertyOf` `P1 is identified by`
- `P170i time is defined by` `subPropertyOf` `P1 is identified by`
The range of P168, P169i and P170i is `E94 Space Primitive`, `E95 Spacetime Primitive` and `E61 Time Primitive` respectively, which are all subclasses of `E41 Appellation` and interpreted as `rdfs:Literal` in RDFS, i.e. these three properties are datatype properties. However, the P1 property has range E41 Appellation, i.e. this property is an object property. Since OWL 2 distinguishes between object subproperties (https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/#Object_Subproperties), data subproperties (https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/#Data_Subproperties) and annotation subproperties (https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/#Annotation_Subproperties), and also in OWL-DL the subject and object of a subproperty statement must be either both datatype properties or both object properties (see here (https://www.w3.org/TR/owl-ref/#subPropertyOf-def)), we do not include these three subPropertyOf relations in the provided RDFS implementation to avoid inconsistencies when reasoning with OWL 2 and OWL DL. Instead, we provide them in a separate ‘supplementary’ RDFS file which one can use if such inconsistencies are not expected.
In addition, since in the current practice, the property `rdfs:label` is widely used to denote appellations (see CRM-SIG Issue 394 (http://cidoc-crm.org/Issue/ID-394-solution-for-dualism-of-e41-appellation-and-rdfslabel)), the following `subPropertyOf` relation was also included in the supplementary RDFS file:
- `rdfs:label` subPropertyOf `P1 is identified by`
Note that according to the RDF Schema 1.1 specification, the domain (or range) of a property does not necessarily need to be 'subClassOf' or 'equal' to the domain (or range) of its superproperties. By including this subproperty relation, one can either directly use `rdfs:label` for providing a non-URI identifier/appellation for an instance of `E1 CRM Entity`, or use `P1 is identified by` for associating an additional URI-identifier with an instance of `E1 CRM Entity`, or use `P1 is identified by` and create an intermediate node (i.e. a URI-identifier for instance of `E41_Appellation`) for providing more detailed information about this appellation.
#### **D. Implementing Value Intervals**
The following are property pairs needed to simulate the interval-valued primitive values foreseen by the CRM:
> D1. addition of two new properties, defined as subproperties of `E52 Time-Span. P81 ongoing throughout: E61 Time Primitive`, for the 'maximum known temporal extent' boundaries specification of `E61 Time Primitive`.
As a result, we have created the following property definitions:
- `E52 Time-Span. P81a end of the begin: rdfs:Literal` (subPropertyOf `E52 Time-Span. P81 ongoing throughout: E61 Time Primitive`)
- `E52 Time-Span. P81b begin of the end: rdfs:Literal` (subPropertyOf `E52 Time-Span. P81 ongoing throughout: E61 Time Primitive`)
> D2. addition of two new properties, defined as subproperties of `E52 Time-Span. P82 at some time within: E61 Time Primitive`, for the 'minimum outer bounds' specification of `E61 Time Primitive`.
Consequently, we have created the following property definitions:
- `E52 Time-Span. P82a begin of the begin: rdfs:Literal` (subPropertyOf `E52 Time-Span. P82 at some time within: E61 Time Primitive`)
- `E52 Time-Span. P82b end of the end: rdfs:Literal` (subPropertyOf `E52 Time-Span. P82 at some time within: E61 Time Primitive`)
> D3. addition of two new properties, defined as subproperties of `E54 Dimension. P90 has value: E60 Number`, for the upper and lower boundaries specification of `E60 Number`.
Consequently, we have created the following property definitions:
- `E54 Dimension. P90a has lower value limit: rdfs:Literal` (subPropertyOf `E54 Dimension. P90 has value: E60 Number`)
- `E54 Dimension. P90b has upper value limit: rdfs:Literal` (subPropertyOf `E54 Dimension. P90 has value: E60 Number`)
#### **E. Multiple ISA custom declaration Classes**
The following are declarations of frequently used multiple instantiations as classes with respective multiple IsA (so far only one):
> E1. addition of a new class, defined as subClassOf `E41 Appellation` and `E33 Linguistic Object`, for all Appellations being regarded
specific to or characteristic for a language group and being described indirectly via a URI.
As a result, we have created the following class definition:
- `E41_E33_Linguistic_Appellation` subClass of `E41_Appellation` and `E33_Linguistic_Object`
#### **F. Translations and Scope notes**
> F1. **Translations** Each RDFS Class or Property definition is accompanied by a set of translations expressed as rdfs:labels separated by xml:lang tags. The translation label used for each language is **the most recent** still **valid** translation. Still valid translation may be interpreted in the following ways:
- The English label of the `CurrentVersion` that the current RDFS file is referring to is *almost equal* (accepting only differences regarding multiple spaces) to the English label of the `TranslationVersion` that the translated label was created for. For example, in order to accept a translation for `E22 Human-Made Object` in the CurrentVersion (7.1.1) we should have a translation for E22 that was created based on a CIDOC version that used the same name for E22. The class name of E22 was changed from `E22 Man-Made Object` to `E22 Human-Made Object` in version 6.2.7. So the only **valid** translations would be these that were created based on version 6.2.7 or later. Currently no such translation has been created, so `E22 Human-Made Object` in CurrentVersion (7.1.1) does not define any translation in the RDFS file.
- Another option is to qualify translations as **valid** based on the scope note comparison of `CurrentVersion` and `TranslationVersion`. Since scope notes include formatting information, the comparison should ignore formatting changes.
Currently in this version we follow the option to qualify translations as valid based on the comparison of the respective labels in the corresponding CIDOC versions.
> F2. **Scope notes** are defined as rdfs:comment and include only the text of the official CIDOC-CRM version in English language. Since scope notes are not just simple texts but include formatting data, a simple removal of the formatting data does not always produce a readable format. Therefore we followed the below simple conventions for the transformation of CIDOC-CRM scope note text into a readable rdfs:comment:
- Each Paragraph defines a new line
- Each element in an unordered list defines a new line
- Each element in an ordered list defines a new line prefixed with `'{order}. '`
- Each superscript text is separated from its base with `'-'`
- Each subscript text is separated from its base with `'_'` (none found)
> F3. **Scope notes of Inverse Properties**. Scope notes for the inverse/backwards direction of properties are not defined as they are covered by the definition of the direct/forward direction definition. Whenever the direct/forward property direction of a property `Pxxx` is not defined due to policy **B1**, then its scope note is used as scope note for the inverse/backwards property `Pxxxi`, and labeled as `Scope note for 'Pxxx':`.
As a result, the direct/forward property definition was used for the rdfs:comment definition of
- `E92 Spacetime Volume. P169i spacetime volume is defined by: rdfs:Literal`
- `E52 Time-Span. P170i time is defined by: rdfs:Literal`
-->
<rdfs:Class rdf:about="E1_CRM_Entity">
<rdfs:label xml:lang="en">CRM Entity</rdfs:label>
<rdfs:label xml:lang="de">CRM Entität</rdfs:label>
<rdfs:label xml:lang="el">Οντότητα CIDOC CRM</rdfs:label>
<rdfs:label xml:lang="fr">Entité CRM</rdfs:label>
<rdfs:label xml:lang="pt">Entidade CRM</rdfs:label>
<rdfs:label xml:lang="ru">CRM Сущность</rdfs:label>
<rdfs:label xml:lang="zh">CRM实体</rdfs:label>
<rdfs:comment>This class comprises all things in the universe of discourse of the CIDOC Conceptual Reference Model.
It is an abstract concept providing for three general properties:
Identification by name or appellation, and in particular by a preferred identifier
Classification by type, allowing further refinement of the specific subclass an instance belongs to
Attachment of free text and other unstructured data for the expression of anything not captured by formal properties
All other classes within the CIDOC CRM are directly or indirectly specialisations of E1 CRM Entity.</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="E2_Temporal_Entity">
<rdfs:label xml:lang="en">Temporal Entity</rdfs:label>
<rdfs:label xml:lang="de">Geschehendes</rdfs:label>
<rdfs:label xml:lang="el">Έγχρονη Οντότητα</rdfs:label>
<rdfs:label xml:lang="fr">Entité temporelle</rdfs:label>
<rdfs:label xml:lang="pt">Entidade Temporal</rdfs:label>
<rdfs:label xml:lang="ru">Временная Сущность</rdfs:label>
<rdfs:label xml:lang="zh">时序实体</rdfs:label>
<rdfs:comment>This class comprises all phenomena, such as the instances of E4 Periods and E5 Events, which happen over a limited extent in time. This extent in time must be contiguous, i.e., without gaps. In case the defining kinds of phenomena for an instance of E2 Temporal Entity cease to happen, and occur later again at another time, we regard that the former instance of E2 Temporal Entity has ended and a new instance has come into existence. In more intuitive terms, the same event cannot happen twice.
In some contexts, such phenomena are also called perdurants. This class is disjoint from E77 Persistent Item and is an abstract class that typically has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area (defined with a greater or lesser degree of precision), and E3 Condition State, which applies to instances of E18 Physical Thing.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E1_CRM_Entity" />
</rdfs:Class>
<rdfs:Class rdf:about="E3_Condition_State">
<rdfs:label xml:lang="en">Condition State</rdfs:label>
<rdfs:label xml:lang="de">Zustandsphase</rdfs:label>
<rdfs:label xml:lang="el">Κατάσταση</rdfs:label>
<rdfs:label xml:lang="fr">État matériel</rdfs:label>
<rdfs:label xml:lang="pt">Estado Material</rdfs:label>
<rdfs:label xml:lang="ru">Состояние</rdfs:label>
<rdfs:label xml:lang="zh">条件状态</rdfs:label>
<rdfs:comment>This class comprises the states of objects characterised by a certain condition over a time-span.
An instance of this class describes the prevailing physical condition of any material object or feature during a specific instance of E52 Time Span. In general, the time-span for which a certain condition can be asserted may be shorter than the real time-span, for which this condition held.
The nature of that condition can be described using P2 has type. For example, the instance of E3 Condition State “condition of the SS Great Britain between 22 September 1846 and 27 August 1847” can be characterized as an instance “wrecked” of E55 Type.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E2_Temporal_Entity" />
</rdfs:Class>
<rdfs:Class rdf:about="E4_Period">
<rdfs:label xml:lang="en">Period</rdfs:label>
<rdfs:label xml:lang="de">Phase</rdfs:label>
<rdfs:label xml:lang="el">Περίοδος</rdfs:label>
<rdfs:label xml:lang="fr">Période</rdfs:label>
<rdfs:label xml:lang="pt">Período</rdfs:label>
<rdfs:label xml:lang="ru">Период</rdfs:label>
<rdfs:label xml:lang="zh">时期</rdfs:label>
<rdfs:comment>This class comprises sets of coherent phenomena or cultural manifestations occurring in time and space.
It is the social or physical coherence of these phenomena that identify an instance of E4 Period and not the associated spatiotemporal extent. This extent is only the “ground” or space in an abstract physical sense that the actual process of growth, spread and retreat has covered. Consequently, different periods can overlap and coexist in time and space, such as when a nomadic culture exists in the same area and time as a sedentary culture. This also means that overlapping land use rights, common among first nations, amounts to overlapping periods.
Often, this class is used to describe prehistoric or historic periods such as the “Neolithic Period”, the “Ming Dynasty” or the “McCarthy Era”, but also geopolitical units and activities of settlements are regarded as special cases of E4 Period. However, there are no assumptions about the scale of the associated phenomena. In particular all events are seen as synthetic processes consisting of coherent phenomena. Therefore, E4 Period is a superclass of E5 Event. For example, a modern clinical birth, an instance of E67 Birth, can be seen as both a single event, i.e., an instance of E5 Event, and as an extended period, i.e., an instance of E4 Period, that consists of multiple physical processes and complementary activities performed by multiple instances of E39 Actor.
As the actual extent of an instance of E4 Period in spacetime we regard the trajectories of the participating physical things during their participation in an instance of E4 Period. This includes the open spaces via which these things have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event. Examples include the air in a meeting room transferring the voices of the participants. Since these phenomena are fuzzy, we assume the spatiotemporal extent to be contiguous, except for cases of phenomena spreading out over islands or other separated areas, including geopolitical units distributed over disconnected areas such as islands or colonies.
Whether the trajectories necessary for participants to travel between these areas are regarded as part of the spatiotemporal extent or not has to be decided in each case based on a concrete analysis, taking use of the sea for other purposes than travel, such as fishing, into consideration. One may also argue that the activities to govern disconnected areas imply travelling through spaces connecting them and that these areas hence are spatially connected in a way, but it appears counterintuitive to consider for instance travel routes in international waters as extensions of geopolitical units.
Consequently, an instance of E4 Period may occupy a number of disjoint spacetime volumes, however there must not be a discontinuity in the timespan covered by these spacetime volumes. This means that an instance of E4 Period must be contiguous in time. If it has ended in all areas, it has ended as a whole. However, it may end in one area before another, such as in the Polynesian migration, and it continues as long as it is ongoing in at least one area.
We model E4 Period as a subclass of E2 Temporal Entity and of E92 Spacetime Volume. The latter is intended as a phenomenal spacetime volume as defined in CIDOC CRMgeo (Doerr &amp; Hiebel, 2013). By virtue of this multiple inheritance, we can discuss the physical extent of an instance of E4 Period without representing each instance of it together with an instance of its associated spacetime volume. This model combines two quite different kinds of substance: an instance of E4 Period is a phenomenon while an instance of E92 Spacetime Volume is an aggregation of points in spacetime. However, the real spatiotemporal extent of an instance of E4 Period is regarded to be unique to it due to all its details and fuzziness; its identity and existence depends uniquely on the identity of the instance of E4 Period. Therefore, this multiple inheritance is unambiguous and effective and furthermore corresponds to the intuitions of natural language.
Typical use of this class in cultural heritage documentation is for documenting cultural and artistic periods. 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 in the European sphere of influence lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included (among others) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an instance of E4 Period, and the second defines morphological object types that fall under E55 Type.
A geopolitical unit as a specific case of an instance of E4 Period is the set of activities and phenomena related to the claim of power, the consequences of belonging to a jurisdictional area and an administrative system that establishes a geopolitical unit. Examples from the modern period are countries or administrative areas of countries such as districts whose actions and structures define activities and phenomena in the area that they intend to govern. The borders of geopolitical units are often defined in contracts or treaties although they may deviate from the actual practice. The spatiotemporal properties of Geopolitical units can be modelled through the properties inherited from E92 Spacetime Volume.
Another specific case of an instance of E4 Period is the actual extent of the set of activities and phenomena as evidenced by their physical traces that define a settlement, such as the populated period of Nineveh.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E2_Temporal_Entity" />
<rdfs:subClassOf rdf:resource="E92_Spacetime_Volume" />
</rdfs:Class>
<rdfs:Class rdf:about="E5_Event">
<rdfs:label xml:lang="en">Event</rdfs:label>
<rdfs:label xml:lang="de">Ereignis</rdfs:label>
<rdfs:label xml:lang="el">Συμβάν</rdfs:label>
<rdfs:label xml:lang="fr">Événement</rdfs:label>
<rdfs:label xml:lang="pt">Evento</rdfs:label>
<rdfs:label xml:lang="ru">Событие</rdfs:label>
<rdfs:label xml:lang="zh">事件</rdfs:label>
<rdfs:comment>This class comprises distinct, delimited and coherent processes and interactions of a material nature, in cultural, social or physical systems, involving and affecting instances of E77 Persistent Item in a way characteristic of the kind of process. Typical examples are meetings, births, deaths, actions of decision taking, making or inventing things, but also more complex and extended ones such as conferences, elections, building of a castle, or battles.
While the continuous growth of a tree lacks the limits characteristic of an event, its germination from a seed does qualify as an event. Similarly, the blowing of the wind lacks the distinctness and limits of an event, but a hurricane, flood or earthquake would qualify as an event. Mental processes are considered as events, in cases where they are connected with the material externalization of their results; for example, the creation of a poem, a performance or a change of intention that becomes obvious from subsequent actions or declarations.
The effects of an instance of E5 Event may not lead to relevant permanent changes of properties or relations of the items involved in it, for example an unrecorded performance. Of course, in order to be documented, some kind of evidence for an event must exist, be it witnesses, traces or products of the event.
While instances of E4 Period always require some form of coherence between its constituent phenomena, in addition, the essential constituents of instances of E5 Event should contribute to an overall effect; for example, the statements made during a meeting and the listening of the audience.
Viewed at a coarse level of detail, an instance of E5 Event may appear as if it had an ‘instantaneous’ overall effect, but any process or interaction of material nature in reality have an extent in time and space. At a fine level, instances of E5 Event may be analyzed into component phenomena and phases within a space and timeframe, and as such can be seen as a period, regardless of the size of the phenomena. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy overall effect and are thus not instances of E5 Event.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E4_Period" />
</rdfs:Class>
<rdfs:Class rdf:about="E6_Destruction">
<rdfs:label xml:lang="en">Destruction</rdfs:label>
<rdfs:label xml:lang="de">Zerstörung</rdfs:label>
<rdfs:label xml:lang="el">Καταστροφή</rdfs:label>
<rdfs:label xml:lang="fr">Destruction</rdfs:label>
<rdfs:label xml:lang="pt">Destruição</rdfs:label>
<rdfs:label xml:lang="ru">Разрушение</rdfs:label>
<rdfs:label xml:lang="zh">破坏</rdfs:label>
<rdfs:comment>This class comprises events that destroy one or more instances of E18 Physical Thing such that they lose their identity as the subjects of documentation.
Some destruction events are intentional, while others are independent of human activity. Intentional destruction may be documented by classifying the event as both an instance of E6 Destruction and of E7 Activity.
The decision to document an object as destroyed, transformed or modified is context sensitive:
1. If the matter remaining from the destruction is not documented, the event is modelled solely as an instance of E6 Destruction.
2. An event should also be documented as an instance of 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 original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as an instance of E11 Modification.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E64_End_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E7_Activity">
<rdfs:label xml:lang="en">Activity</rdfs:label>
<rdfs:label xml:lang="de">Handlung</rdfs:label>
<rdfs:label xml:lang="el">Δράση</rdfs:label>
<rdfs:label xml:lang="fr">Activité</rdfs:label>
<rdfs:label xml:lang="pt">Atividade</rdfs:label>
<rdfs:label xml:lang="ru">Деятельность</rdfs:label>
<rdfs:label xml:lang="zh">活动</rdfs:label>
<rdfs:comment>This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented.
This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E5_Event" />
</rdfs:Class>
<rdfs:Class rdf:about="E8_Acquisition">
<rdfs:label xml:lang="en">Acquisition</rdfs:label>
<rdfs:label xml:lang="de">Erwerb</rdfs:label>
<rdfs:label xml:lang="el">Απόκτηση</rdfs:label>
<rdfs:label xml:lang="fr">Acquisition</rdfs:label>
<rdfs:label xml:lang="pt">Aquisição</rdfs:label>
<rdfs:label xml:lang="ru">Событие Приобретения</rdfs:label>
<rdfs:label xml:lang="zh">采访</rdfs:label>
<rdfs:comment>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 CIDOC 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.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
</rdfs:Class>
<rdfs:Class rdf:about="E9_Move">
<rdfs:label xml:lang="en">Move</rdfs:label>
<rdfs:label xml:lang="de">Objektbewegung</rdfs:label>
<rdfs:label xml:lang="el">Μετακίνηση</rdfs:label>
<rdfs:label xml:lang="fr">Déplacement</rdfs:label>
<rdfs:label xml:lang="pt">Locomoção</rdfs:label>
<rdfs:label xml:lang="ru">Перемещение</rdfs:label>
<rdfs:label xml:lang="zh">移动</rdfs:label>
<rdfs:comment>This class comprises changes of the physical location of the instances of E19 Physical Object.
Note, that the class E9 Move inherits the property P7 took place at (witnessed): E53 Place. This property should be used to describe the trajectory or a larger area within which a move takes place, whereas the properties P26 moved to (was destination of), P27 moved from (was origin of) describe the start and end points only. Moves may also be documented to consist of other moves (via P9 consists of (forms part of)), in order to describe intermediate stages on a trajectory. In that case, start and end points of the partial moves should match appropriately between each other and with the overall event.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
</rdfs:Class>
<rdfs:Class rdf:about="E10_Transfer_of_Custody">
<rdfs:label xml:lang="en">Transfer of Custody</rdfs:label>
<rdfs:label xml:lang="de">Übertragung des Gewahrsams</rdfs:label>
<rdfs:label xml:lang="el">Μεταβίβαση Κατοχής</rdfs:label>
<rdfs:label xml:lang="fr">Changement de détenteur</rdfs:label>
<rdfs:label xml:lang="pt">Transferência de Custódia</rdfs:label>
<rdfs:label xml:lang="ru">Передача Опеки</rdfs:label>
<rdfs:label xml:lang="zh">转移监护权</rdfs:label>
<rdfs:comment>This class comprises transfers of the physical custody or the legal responsibility for the physical custody of objects. The recording of the donor or recipient is optional. It is possible that in an instance of E10 Transfer of Custody there is either no donor or no recipient.
Depending on the circumstances, it may describe:
1. the beginning of custody (there is no previous custodian)
2. the end of custody (there is no subsequent custodian)
3. the transfer of custody (transfer from one custodian to the next)
4. the receipt of custody from an unknown source (the previous custodian is unknown)
5. the declared loss of an object (the current or subsequent custodian is unknown)
In the event that only a single kind of transfer of custody occurs, either the legal responsibility for the custody or the actual physical possession of the object but not both, this difference should be expressed using the property P2 has type (is type of).
The sense of physical possession requires that the object of custody be in the hands of the keeper at least with a part representative for the whole. The way, in which a representative part is defined, should ensure that it is unambiguous who keeps a part and who the whole and should be consistent with the identity criteria of the kept instance of E18 Physical Thing.
The interpretation of the museum notion of "accession" differs between institutions. The CIDOC CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
Theft is a specific case of illegal transfer of custody.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
</rdfs:Class>
<rdfs:Class rdf:about="E11_Modification">
<rdfs:label xml:lang="en">Modification</rdfs:label>
<rdfs:label xml:lang="de">Bearbeitung</rdfs:label>
<rdfs:label xml:lang="el">Τροποποίηση</rdfs:label>
<rdfs:label xml:lang="fr">Modification</rdfs:label>
<rdfs:label xml:lang="pt">Modificação</rdfs:label>
<rdfs:label xml:lang="ru">Событие Изменения</rdfs:label>
<rdfs:label xml:lang="zh">修改</rdfs:label>
<rdfs:comment>This class comprises instances of E7 Activity that are undertaken to create, alter or change instances of E24 Physical Human-Made Thing.
This class includes the production of an item from raw materials and other so far undocumented objects. It also includes the conservation treatment of an object.
Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in an instance of E11 Modification, and that others may be produced as a result of it. An event should also be documented using an instance of 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.
An activity undertaken on an object which was designed to alter it, but which, in fact, it did not in any seemingly significant way (such as the application of a solvent during conservation which failed to dissolve any part of the object), is still considered as an instance of E11 Modification. Typically, any such activity will leave at least forensic traces of evidence on the object.
If the instance of E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
</rdfs:Class>
<rdfs:Class rdf:about="E12_Production">
<rdfs:label xml:lang="en">Production</rdfs:label>
<rdfs:label xml:lang="de">Herstellung</rdfs:label>
<rdfs:label xml:lang="el">Παραγωγή</rdfs:label>
<rdfs:label xml:lang="fr">Production</rdfs:label>
<rdfs:label xml:lang="pt">Produção</rdfs:label>
<rdfs:label xml:lang="ru">Событие Производства</rdfs:label>
<rdfs:label xml:lang="zh">生产</rdfs:label>
<rdfs:comment>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 an instance of 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.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E11_Modification" />
<rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E13_Attribute_Assignment">
<rdfs:label xml:lang="en">Attribute Assignment</rdfs:label>
<rdfs:label xml:lang="de">Merkmalszuweisung</rdfs:label>
<rdfs:label xml:lang="el">Απόδοση Ιδιοτήτων</rdfs:label>
<rdfs:label xml:lang="fr">Affectation d'attribut</rdfs:label>
<rdfs:label xml:lang="pt">Atribuição de Característica</rdfs:label>
<rdfs:label xml:lang="ru">Присвоение Атрибута</rdfs:label>
<rdfs:label xml:lang="zh">属性赋值</rdfs:label>
<rdfs:comment>This class comprises the actions of making assertions about one property of an object or any single relation between two items or concepts. The type of the property asserted to hold between two items or concepts can be described by the property P177 assigned property type: E55 Type.
For example, the class describes the actions of people making propositions and statements during certain scientific/scholarly procedures, e.g., the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on whether this information should be accessible by structured queries.
This class allows for the documentation of how the respective assignment came about, and whose opinion it was. Note that all instances of properties described in a knowledge base are the opinion of someone. Per default, they are the opinion of the team maintaining the knowledge base. This fact must not individually be registered for all instances of properties provided by the maintaining team, because it would result in an endless recursion of whose opinion was the description of an opinion. Therefore, the use of instances of E13 Attribute Assignment marks the fact, that the maintaining team is in general neutral to the validity of the respective assertion, but registers someone else’s opinion and how it came about.
All properties assigned in such an action can also be seen as directly relating the respective pair of items or concepts. Multiple use of instances of E13 Attribute Assignment may possibly lead to a collection of contradictory values.
All cases of properties in this model that are also described indirectly through a subclass of E13 Attribute Assignment are characterised as "short cuts" of a path via this subclass. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action of assertion or the short cut, and the relation between both alternatives can be captured by simple rules.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
</rdfs:Class>
<rdfs:Class rdf:about="E14_Condition_Assessment">
<rdfs:label xml:lang="en">Condition Assessment</rdfs:label>
<rdfs:label xml:lang="de">Zustandsfeststellung</rdfs:label>
<rdfs:label xml:lang="el">Εκτίμηση Κατάστασης</rdfs:label>
<rdfs:label xml:lang="fr">Expertise de l'état matériel</rdfs:label>
<rdfs:label xml:lang="pt">Avaliação do Estado Material</rdfs:label>
<rdfs:label xml:lang="ru">Оценка Состояния</rdfs:label>
<rdfs:label xml:lang="zh">状态评估</rdfs:label>
<rdfs:comment>This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E13_Attribute_Assignment" />
</rdfs:Class>
<rdfs:Class rdf:about="E15_Identifier_Assignment">
<rdfs:label xml:lang="en">Identifier Assignment</rdfs:label>
<rdfs:label xml:lang="de">Kennzeichenzuweisung</rdfs:label>
<rdfs:label xml:lang="el">Απόδοση Αναγνωριστικού</rdfs:label>
<rdfs:label xml:lang="fr">Attribution d’identificateur</rdfs:label>
<rdfs:label xml:lang="pt">Atribuição de Identificador</rdfs:label>
<rdfs:label xml:lang="ru">Назначение Идентификатора</rdfs:label>
<rdfs:label xml:lang="zh">标识符赋值</rdfs:label>
<rdfs:comment>This class comprises activities that result in the allocation of an identifier to an instance of E1 CRM Entity. Instances of 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. P48 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.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E13_Attribute_Assignment" />
</rdfs:Class>
<rdfs:Class rdf:about="E16_Measurement">
<rdfs:label xml:lang="en">Measurement</rdfs:label>
<rdfs:label xml:lang="de">Messung</rdfs:label>
<rdfs:label xml:lang="el">Μέτρηση</rdfs:label>
<rdfs:label xml:lang="fr">Mesurage</rdfs:label>
<rdfs:label xml:lang="pt">Medição</rdfs:label>
<rdfs:label xml:lang="ru">Событие Измерения</rdfs:label>
<rdfs:label xml:lang="zh">测量</rdfs:label>
<rdfs:comment>This class comprises actions measuring quantitative physical properties and other values that can be determined by a systematic, objective procedure of direct observation of particular states of physical reality.
An instance of E16 Measurement may us simple counting or tools, such as yardsticks or radiation detection devices. The interest is in the method and care applied, so that the reliability of the result may be judged at a later stage, or research continued on the associated documents. The date of the event is important for dimensions, which may change value over time, such as the length of an object subject to shrinkage. Methods and devices employed should be associated with instances of E16 Measurement by properties such as P33 used specific technique: E29 Design or Procedure, P125 used object of type: E55 Type, P16 used specific object (was used for): E70 Thing, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type (is type of): E55 Type. Details of methods and devices reused or reusable in other instances of E16 Measurement should be documented for these entities rather than the measurements themselves, whereas details of particular execution may be documented by free text or by instantiating adequate sub-activities, if the detail may be of interest for an overarching query.
Regardless whether a measurement is made by an instrument or by human senses, it represents the initial transition from physical reality to information without any other documented information object in between within the reasoning chain that would represent the result of the interaction of the observer or device with reality. Therefore, determining properties of an instance of E90 Symbolic Object is regarded as an instance of E13 Attribute Assignment, which may be inferred from observing and measuring representative carriers. In the case that the carrier can be named, the property P16 used specific object (was used for): should be used to indicate the instance(s) of E18 Physical Thing that was used as the empirical basis for the attribute assignment. For instance, inferring properties of depicted items using image material, such as satellite images, is not regarded as an instance of E16 Measurement, but as a subsequent instance of E13 Attribute Assignment. Rather, only the production of the images, understood as arrays of radiation intensities, is regarded as an instance of E16 Measurement. The same reasoning holds for other sensor data.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E13_Attribute_Assignment" />
</rdfs:Class>
<rdfs:Class rdf:about="E17_Type_Assignment">
<rdfs:label xml:lang="en">Type Assignment</rdfs:label>
<rdfs:label xml:lang="de">Typuszuweisung</rdfs:label>
<rdfs:label xml:lang="el">Απόδοση Τύπου</rdfs:label>
<rdfs:label xml:lang="fr">Attribution de type</rdfs:label>
<rdfs:label xml:lang="pt">Atribuição de Tipo</rdfs:label>
<rdfs:label xml:lang="ru">Присвоение Типа</rdfs:label>
<rdfs:label xml:lang="zh">类型赋值</rdfs:label>
<rdfs:comment>This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions and concepts.
This class allows for the documentation of the context of classification acts in cases where the value of the classification depends on the personal opinion of the classifier, and the date that the classification was made. This class also encompasses the notion of "determination," i.e., the systematic and molecular identification of a specimen in biology.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E13_Attribute_Assignment" />
</rdfs:Class>
<rdfs:Class rdf:about="E18_Physical_Thing">
<rdfs:label xml:lang="en">Physical Thing</rdfs:label>
<rdfs:label xml:lang="de">Materielles</rdfs:label>
<rdfs:label xml:lang="el">Υλικό Πράγμα</rdfs:label>
<rdfs:label xml:lang="fr">Chose matérielle</rdfs:label>
<rdfs:label xml:lang="pt">Coisa Material</rdfs:label>
<rdfs:label xml:lang="ru">Физическая Вещь</rdfs:label>
<rdfs:label xml:lang="zh">实物</rdfs:label>
<rdfs:comment>This class comprises all persistent physical items with a relatively stable form, human-made or natural.
Depending on the existence of natural boundaries of such things, the CIDOC CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter.
An instance of E18 Physical Thing occupies not only a particular geometric space at any instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime. We include in the occupied space the space filled by the matter of the physical thing and all its inner spaces, such as the interior of a box. For the purpose of more detailed descriptions of the presence of an instance of E18 Physical Thing in space and time it can be associated with its specific instance of E92 Spacetime Volume by the property P196 defines (is defined by).
The CIDOC CRM is generally not concerned with amounts of matter in fluid or gaseous states, as long as they are not confined in an identifiable way for an identifiable minimal time-span.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E72_Legal_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E19_Physical_Object">
<rdfs:label xml:lang="en">Physical Object</rdfs:label>
<rdfs:label xml:lang="de">Materieller Gegenstand</rdfs:label>
<rdfs:label xml:lang="el">Υλικό Αντικείμενο</rdfs:label>
<rdfs:label xml:lang="fr">Objet matériel</rdfs:label>
<rdfs:label xml:lang="pt">Objeto Material</rdfs:label>
<rdfs:label xml:lang="ru">Физический Объект</rdfs:label>
<rdfs:label xml:lang="zh">物质对象</rdfs:label>
<rdfs:comment>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 &amp; 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.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E18_Physical_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E20_Biological_Object">
<rdfs:label xml:lang="en">Biological Object</rdfs:label>
<rdfs:label xml:lang="de">Biologischer Gegenstand</rdfs:label>
<rdfs:label xml:lang="el">Βιολογικό Ακτικείμενο</rdfs:label>
<rdfs:label xml:lang="fr">Objet biologique</rdfs:label>
<rdfs:label xml:lang="pt">Objeto Biológico</rdfs:label>
<rdfs:label xml:lang="ru">Биологический Объект</rdfs:label>
<rdfs:label xml:lang="zh">生物对象</rdfs:label>
<rdfs:comment>This class comprises individual items of a material nature, which live, have lived or are natural products of or from living organisms.
Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Human-Made Object.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E19_Physical_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E21_Person">
<rdfs:label xml:lang="en">Person</rdfs:label>
<rdfs:label xml:lang="de">Person</rdfs:label>
<rdfs:label xml:lang="el">Πρόσωπο</rdfs:label>
<rdfs:label xml:lang="fr">Personne</rdfs:label>
<rdfs:label xml:lang="pt">Pessoa</rdfs:label>
<rdfs:label xml:lang="ru">Личность</rdfs:label>
<rdfs:label xml:lang="zh">人物</rdfs:label>
<rdfs:comment>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 CIDOC CRM does not propose a specific form to support reasoning about possible identity.
In a bibliographic context, a name presented following the conventions usually employed for personal names will be assumed to correspond to an actual real person (an instance of E21 Person), unless evidence is available to indicate that this is not the case. The fact that a persona may erroneously be classified as an instance of E21 Person does not imply that the concept comprises personae.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E20_Biological_Object" />
<rdfs:subClassOf rdf:resource="E39_Actor" />
</rdfs:Class>
<rdfs:Class rdf:about="E22_Human-Made_Object">
<rdfs:label xml:lang="en">Human-Made Object</rdfs:label>
<rdfs:comment>This class comprises all persistent physical objects of any size that are purposely created by human activity 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.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E19_Physical_Object" />
<rdfs:subClassOf rdf:resource="E24_Physical_Human-Made_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E24_Physical_Human-Made_Thing">
<rdfs:label xml:lang="en">Physical Human-Made Thing</rdfs:label>
<rdfs:comment>This class comprises all persistent physical items of any size that are purposely created by human activity. This class comprises, besides others, Human-Made objects, such as a sword, and Human-Made features, such as rock art. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Human-Made Thing.
Instances of Human-Made thing may be the result of modifying pre-existing physical things, preserving larger parts or most of the original matter and structure, which poses the question if they are new or even Human-Made, the respective interventions of production made on such original material should be obvious and sufficient to regard that the product has a new, distinct identity and intended function and is human-made. Substantial continuity of the previous matter and structure in the new product can be documented by describing the production process also as an instance of E81 Transformation.
Whereas interventions of conservation and repair are not regarded to produce a new Human-Made thing, the results of preparation of natural history specimens that substantially change their natural or original state should be regarded as physical Human-Made things, including the uncovering of petrified biological features from a solid piece of stone. On the other side, scribbling a museum number on a natural object should not be regarded to make it Human-Made. This notwithstanding, parts, sections, segments, or features of a physical Human-Made thing may continue to be non-Human-Made and preserved during the production process, for example natural pearls used as a part of an eardrop.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E18_Physical_Thing" />
<rdfs:subClassOf rdf:resource="E71_Human-Made_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E25_Human-Made_Feature">
<rdfs:label xml:lang="en">Human-Made Feature</rdfs:label>
<rdfs:comment>This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. In particular, it includes the information encoding features on mechanical or digital carriers.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E24_Physical_Human-Made_Thing" />
<rdfs:subClassOf rdf:resource="E26_Physical_Feature" />
</rdfs:Class>
<rdfs:Class rdf:about="E26_Physical_Feature">
<rdfs:label xml:lang="en">Physical Feature</rdfs:label>
<rdfs:label xml:lang="de">Materielles Merkmal</rdfs:label>
<rdfs:label xml:lang="el">Υλικό Μόρφωμα</rdfs:label>
<rdfs:label xml:lang="fr">Caractéristique matérielle</rdfs:label>
<rdfs:label xml:lang="pt">Característica Material</rdfs:label>
<rdfs:label xml:lang="ru">Физический Признак</rdfs:label>
<rdfs:label xml:lang="zh">物理特征</rdfs:label>
<rdfs:comment>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 &amp; Varzi, 2000, pp.401-420), with the exception of aggregates of “bona fide objects”.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E18_Physical_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E27_Site">
<rdfs:label xml:lang="en">Site</rdfs:label>
<rdfs:label xml:lang="de">Gelände</rdfs:label>
<rdfs:label xml:lang="el">Φυσικός Χώρος</rdfs:label>
<rdfs:label xml:lang="fr">Site</rdfs:label>
<rdfs:label xml:lang="pt">Lugar</rdfs:label>
<rdfs:label xml:lang="ru">Участок</rdfs:label>
<rdfs:label xml:lang="zh">场地</rdfs:label>
<rdfs:comment>This class comprises pieces of land or sea floor.
In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps.
Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E26_Physical_Feature" />
</rdfs:Class>
<rdfs:Class rdf:about="E28_Conceptual_Object">
<rdfs:label xml:lang="en">Conceptual Object</rdfs:label>
<rdfs:label xml:lang="de">Begrifflicher Gegenstand</rdfs:label>
<rdfs:label xml:lang="el">Νοητικό Αντικείμενο</rdfs:label>
<rdfs:label xml:lang="fr">Objet conceptuel</rdfs:label>
<rdfs:label xml:lang="pt">Objeto Conceitual</rdfs:label>
<rdfs:label xml:lang="ru">Концептуальный Объект</rdfs:label>
<rdfs:label xml:lang="zh">概念对象</rdfs:label>
<rdfs:comment>This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation or historical implication. The production of such information may have been supported by the use of technical devices such as cameras or computers.
Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc.
They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E71_Human-Made_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E29_Design_or_Procedure">
<rdfs:label xml:lang="en">Design or Procedure</rdfs:label>
<rdfs:label xml:lang="de">Entwurf oder Verfahren</rdfs:label>
<rdfs:label xml:lang="el">Σχέδιο</rdfs:label>
<rdfs:label xml:lang="fr">Conception ou procédure</rdfs:label>
<rdfs:label xml:lang="pt">Projeto ou Procedimento</rdfs:label>
<rdfs:label xml:lang="ru">Проект или Процедура</rdfs:label>
<rdfs:label xml:lang="zh">设计或程序</rdfs:label>
<rdfs:comment>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 new instances of E71 Human-Made Thing or for shaping or guiding the execution of an instance of E7 Activity.
Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others.
This is modelled using P69 has association with (is associated with): E29 Design or Procedure.
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 CIDOC CRM models a loose relationship between the plan and the respective product.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E73_Information_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E30_Right">
<rdfs:label xml:lang="en">Right</rdfs:label>
<rdfs:label xml:lang="de">Recht</rdfs:label>
<rdfs:label xml:lang="el">Δικαίωμα</rdfs:label>
<rdfs:label xml:lang="fr">Droit</rdfs:label>
<rdfs:label xml:lang="pt">Direitos</rdfs:label>
<rdfs:label xml:lang="ru">Право</rdfs:label>
<rdfs:label xml:lang="zh">权限</rdfs:label>
<rdfs:comment>This class comprises legal privileges concerning material and immaterial things or their derivatives.
These include reproduction and property rights.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E89_Propositional_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E31_Document">
<rdfs:label xml:lang="en">Document</rdfs:label>
<rdfs:label xml:lang="de">Dokument</rdfs:label>
<rdfs:label xml:lang="el">Τεκμήριο</rdfs:label>
<rdfs:label xml:lang="fr">Document</rdfs:label>
<rdfs:label xml:lang="pt">Documento</rdfs:label>
<rdfs:label xml:lang="ru">Документ</rdfs:label>
<rdfs:label xml:lang="zh">文献</rdfs:label>
<rdfs:comment>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 instances of E31 Document. This class should not be confused with the concept “document” in Information Technology, which is compatible with E73 Information Object.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E73_Information_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E32_Authority_Document">
<rdfs:label xml:lang="en">Authority Document</rdfs:label>
<rdfs:label xml:lang="de">Referenzdokument</rdfs:label>
<rdfs:label xml:lang="el">Πηγή Καθιερωμένων Όρων</rdfs:label>
<rdfs:label xml:lang="fr">Document de référence</rdfs:label>
<rdfs:label xml:lang="pt">Documento de Referência</rdfs:label>
<rdfs:label xml:lang="ru">Официальный Документ</rdfs:label>
<rdfs:label xml:lang="zh">规范文档</rdfs:label>
<rdfs:comment>This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E31_Document" />
</rdfs:Class>
<rdfs:Class rdf:about="E33_Linguistic_Object">
<rdfs:label xml:lang="en">Linguistic Object</rdfs:label>
<rdfs:label xml:lang="de">Sprachlicher Gegenstand</rdfs:label>
<rdfs:label xml:lang="el">Γλωσσικό Αντικείμενο</rdfs:label>
<rdfs:label xml:lang="fr">Objet linguistique</rdfs:label>
<rdfs:label xml:lang="pt">Objeto Lingüístico</rdfs:label>
<rdfs:label xml:lang="ru">Линвистический Объект</rdfs:label>
<rdfs:label xml:lang="zh">语言对象</rdfs:label>
<rdfs:comment>This class comprises identifiable expressions in natural language or languages.
Instances of E33 Linguistic Object can be expressed in many ways: e.g., as written texts, recorded speech or sign language. However, the CIDOC CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CIDOC CRM. These should be modelled as instances of E73 Information Object.
In general, an instance of E33 Linguistic Object may also contain non-linguistic information, often of artistic or aesthetic value. Only in cases in which the content of an instance of E33 Linguistic Object can completely be expressed by a series of binary-encoded symbols, its content may be documented within a respective knowledge base by the property P190 has symbolic content: E62 String. Otherwise, it should be understood as an identifiable digital resource only available independently from the respective knowledge base.
In other cases, such as pages of an illuminated manuscript or recordings containing speech in a language supported by a writing system, the linguistic part of the content of an instance of E33 Linguistic Object may be documented within a respective knowledge base in a note by P3 has note: E62 String. Otherwise, it may be described using the property P165 incorporates (is incorporated in): E73 Information Object as a different object with its own identity.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E73_Information_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E33_E41_Linguistic_Appellation">
<rdfs:label xml:lang="en">Linguistic Appellation</rdfs:label>
<rdfs:subClassOf rdf:resource="E33_Linguistic_Object" />
<rdfs:subClassOf rdf:resource="E41_Appellation" />
</rdfs:Class>
<rdfs:Class rdf:about="E34_Inscription">
<rdfs:label xml:lang="en">Inscription</rdfs:label>
<rdfs:label xml:lang="de">Inschrift</rdfs:label>
<rdfs:label xml:lang="el">Επιγραφή</rdfs:label>
<rdfs:label xml:lang="fr">Inscription</rdfs:label>
<rdfs:label xml:lang="pt">Inscrição</rdfs:label>
<rdfs:label xml:lang="ru">Надпись</rdfs:label>
<rdfs:label xml:lang="zh">题识</rdfs:label>
<rdfs:comment>This class comprises recognisable, texts attached to instances of E24 Physical Human-Made Thing.
The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CIDOC CRM as instances of E24 Physical Human-Made Thing.
The relationship of a physical copy of a book to the text it contains is modelled using E18 Physical Thing. P128 carries (is carried by): E33 Linguistic Object.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E33_Linguistic_Object" />
<rdfs:subClassOf rdf:resource="E37_Mark" />
</rdfs:Class>
<rdfs:Class rdf:about="E35_Title">
<rdfs:label xml:lang="en">Title</rdfs:label>
<rdfs:label xml:lang="de">Titel</rdfs:label>
<rdfs:label xml:lang="el">Τίτλος</rdfs:label>
<rdfs:label xml:lang="fr">Titre</rdfs:label>
<rdfs:label xml:lang="pt">Título</rdfs:label>
<rdfs:label xml:lang="ru">Заголовок</rdfs:label>
<rdfs:label xml:lang="zh">题名</rdfs:label>
<rdfs:comment>This class comprises textual strings that within a cultural context can be clearly identified as titles due to their form. Being a subclass of E41 Appellation, E35 Title can only be used when such a string is actually used as a title of a work, such as a text, an artwork, or a piece of music.
Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group.
This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E33_Linguistic_Object" />
<rdfs:subClassOf rdf:resource="E41_Appellation" />
</rdfs:Class>
<rdfs:Class rdf:about="E36_Visual_Item">
<rdfs:label xml:lang="en">Visual Item</rdfs:label>
<rdfs:label xml:lang="de">Bildliches</rdfs:label>
<rdfs:label xml:lang="el">Οπτικό Στοιχείο</rdfs:label>
<rdfs:label xml:lang="fr">Item visuel</rdfs:label>
<rdfs:label xml:lang="pt">Item Visual</rdfs:label>
<rdfs:label xml:lang="ru">Визуальный Предмет</rdfs:label>
<rdfs:label xml:lang="zh">可视项</rdfs:label>
<rdfs:comment>This class comprises the intellectual or conceptual aspects of recognisable marks, images and other visual works.
This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of a visual item, but the underlying prototype. For example, a mark such as the ICOM logo is generally considered to be the same logo when used on any number of publications. The size, orientation and colour may change, but the logo remains uniquely identifiable. The same is true of images that are reproduced many times. This means that visual items are independent of their physical support.
The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Human-Made Thing that carry the same visual qualities (symbols, marks or images etc.). The property P62 depicts (is depicted by) between E24 Physical Human-Made Thing and depicted subjects (E1 CRM Entity) is a shortcut of the more fully developed path from E24 Physical Human-Made Thing through P65 shows visual item (is shown by), E36 Visual Item, P138 represents (has representation) to E1CRM Entity, which in addition captures the optical features of the depiction.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E73_Information_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E37_Mark">
<rdfs:label xml:lang="en">Mark</rdfs:label>
<rdfs:label xml:lang="de">Marke</rdfs:label>
<rdfs:label xml:lang="el">Σήμανση</rdfs:label>
<rdfs:label xml:lang="fr">Marque</rdfs:label>
<rdfs:label xml:lang="pt">Marca</rdfs:label>
<rdfs:label xml:lang="ru">Пометка</rdfs:label>
<rdfs:label xml:lang="zh">标记</rdfs:label>
<rdfs:comment>This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Human-Made Thing by arbitrary techniques, often in order to indicate such things as creator, owner, dedications, purpose or to communicate information generally. Instances of E37 Mark do not represent the actual image of a mark, but the abstract ideal (or archetype) as used for codification in reference documents forming cultural documentation.
This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Human-Made Feature.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E36_Visual_Item" />
</rdfs:Class>
<rdfs:Class rdf:about="E39_Actor">
<rdfs:label xml:lang="en">Actor</rdfs:label>
<rdfs:label xml:lang="de">Akteur</rdfs:label>
<rdfs:label xml:lang="el">Δράστης</rdfs:label>
<rdfs:label xml:lang="fr">Agent</rdfs:label>
<rdfs:label xml:lang="pt">Agente</rdfs:label>
<rdfs:label xml:lang="ru">Агент</rdfs:label>
<rdfs:label xml:lang="zh">参与者</rdfs:label>
<rdfs:comment>This class comprises people, either individually or in groups, who have the potential to perform intentional actions of kinds for which someone may be held responsible.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E77_Persistent_Item" />
</rdfs:Class>
<rdfs:Class rdf:about="E41_Appellation">
<rdfs:label xml:lang="en">Appellation</rdfs:label>
<rdfs:label xml:lang="de">Benennung</rdfs:label>
<rdfs:label xml:lang="el">Ονομασία</rdfs:label>
<rdfs:label xml:lang="fr">Appellation</rdfs:label>
<rdfs:label xml:lang="pt">Designação</rdfs:label>
<rdfs:label xml:lang="ru">Обозначение</rdfs:label>
<rdfs:label xml:lang="zh">称谓</rdfs:label>
<rdfs:comment>This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class or category within a certain context.
Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but instead by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes.
Different languages may use different appellations for the same thing, such as the names of major cities. Some appellations may be formulated using a valid noun phrase of a particular language. In these cases, the respective instances of E41 Appellation should also be declared as instances of E33 Linguistic Object. Then the language using the appellation can be declared with the property P72 has language: E56 Language.
Instances of E41 Appellation may be used to identify any instance of E1 CRM Entity and sometimes are characteristic for instances of more specific subclasses E1 CRM Entity, such as for instances of E52 Time-Span (for instance “dates”), E39 Actor, E53 Place or E28 Conceptual Object. Postal addresses and E-mail addresses are characteristic examples of identifiers used by services transporting things between clients.
Even numerically expressed identifiers for extents in space or time are also regarded as instances of E41 Appellation, such as Gregorian dates or spatial coordinates, even though they allow for determining some time or location by a known procedure starting from a reference point and by virtue of that fact play a double role as instances of E59 Primitive Value.
E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment</rdfs:comment>
<rdfs:subClassOf rdf:resource="E90_Symbolic_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E42_Identifier">
<rdfs:label xml:lang="en">Identifier</rdfs:label>
<rdfs:label xml:lang="de">Kennung</rdfs:label>
<rdfs:label xml:lang="el">Κωδικός Αναγνώρισης</rdfs:label>
<rdfs:label xml:lang="fr">Identificateur d'objet</rdfs:label>
<rdfs:label xml:lang="pt">Identificador de Objeto</rdfs:label>
<rdfs:label xml:lang="ru">Идентификатор Объекта</rdfs:label>
<rdfs:label xml:lang="zh">标识符</rdfs:label>
<rdfs:comment>This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. Postal addresses, telephone numbers, urls and e-mail addresses are characteristic examples of identifiers used by services transporting things between clients.
The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E41_Appellation" />
</rdfs:Class>
<rdfs:Class rdf:about="E52_Time-Span">
<rdfs:label xml:lang="en">Time-Span</rdfs:label>
<rdfs:label xml:lang="de">Zeitspanne</rdfs:label>
<rdfs:label xml:lang="el">Χρονικό Διάστημα</rdfs:label>
<rdfs:label xml:lang="fr">Durée</rdfs:label>
<rdfs:label xml:lang="pt">Período de Tempo</rdfs:label>
<rdfs:label xml:lang="ru">Интервал Времени</rdfs:label>
<rdfs:label xml:lang="zh">时段</rdfs:label>
<rdfs:comment>This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Instances of E52 Time-Span have no semantic connotations about phenomena happening within the temporal extent they represent. They do not convey any meaning other than a positioning on the “time-line” of chronology. The actual extent of an instance of E52 Time-Span can be approximated by properties of E52 Time-Span giving inner and outer bounds in the form of dates (instances of E61 Time Primitive). Comparing knowledge about time-spans is fundamental for chronological reasoning.
Some instances of E52 Time-Span may be defined as the actual, in principle observable, temporal extent of instances of E2 Temporal Entity via the property P4 has time-span (is time-span of): E52 Time-Span. They constitute phenomenal time-spans as defined in CRMgeo (Doerr &amp; Hiebel 2013). Since our knowledge of history is imperfect and physical phenomena are fuzzy in nature, the extent of phenomenal time-spans can only be described in approximation. An extreme case of approximation, might, for example, define an instance of E52 Time-Span having unknown beginning, end and duration. It may, nevertheless, be associated with other descriptions by which we can infer knowledge about it, such as in relative chronologies.
Some instances of E52 may be defined precisely as representing a declaration of a temporal extent, as, for instance, done in a business contract. They constitute declarative time-spans as defined in CRMgeo (Doerr &amp; Hiebel 2013) and can be described via the property E61 Time Primitive P170 defines time (time is defined by): E52 Time-Span.
When used as a common E52 Time-Span for two events, it will nevertheless describe them as being simultaneous, even if nothing else is known.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E1_CRM_Entity" />
</rdfs:Class>
<rdfs:Class rdf:about="E53_Place">
<rdfs:label xml:lang="en">Place</rdfs:label>
<rdfs:label xml:lang="de">Ort</rdfs:label>
<rdfs:label xml:lang="el">Τόπος</rdfs:label>
<rdfs:label xml:lang="fr">Lieu</rdfs:label>
<rdfs:label xml:lang="pt">Local</rdfs:label>
<rdfs:label xml:lang="ru">Место</rdfs:label>
<rdfs:label xml:lang="zh">地点</rdfs:label>
<rdfs:comment>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, but may also be determined by reference to mobile objects. A Place can be determined by combining a frame of reference and a location with respect to this frame.
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 instance of E18 Physical Thing can serve as a frame of reference for an instance of E53 Place. This may be documented using the property P157 is at rest relative to (provides reference space for).</rdfs:comment>
<rdfs:subClassOf rdf:resource="E1_CRM_Entity" />
</rdfs:Class>
<rdfs:Class rdf:about="E54_Dimension">
<rdfs:label xml:lang="en">Dimension</rdfs:label>
<rdfs:label xml:lang="de">Maß</rdfs:label>
<rdfs:label xml:lang="el">Μέγεθος</rdfs:label>
<rdfs:label xml:lang="fr">Dimensions</rdfs:label>
<rdfs:label xml:lang="pt">Dimensão</rdfs:label>
<rdfs:label xml:lang="ru">Величина</rdfs:label>
<rdfs:label xml:lang="zh">度量规格</rdfs:label>
<rdfs:comment>This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e., by points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc.
An instance of E54 Dimension represents the empirical or theoretically derived quantity, including the precision tolerances resulting from the particular method or calculation. The identity of an instance of E54 Dimension depends on the method of its determination because each method may produce different values even when determining comparable qualities. For instance, the wingspan of a bird alive or dead is a different dimension. Thermoluninescence dating and Rehydroxylation [RHX] dating are different dimensions of temporal distance from now, even if they aim at dating the same object. The method of determination should be expressed using the property P2 has type (is type of). Note that simple terms such as “diameter” or “length” are normally insufficient to unambiguously describe a respective dimension. In contrast, “maximum linear extent” may be sufficient.
The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of instances of E54 Dimension adequate to the precision of the applied method of determination. If the respective quantity belongs to a non-discrete space according to the laws of physics, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that comparability of values described in different units depends critically on the representation as value regions.
Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension, as appropriate.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E1_CRM_Entity" />
</rdfs:Class>
<rdfs:Class rdf:about="E55_Type">
<rdfs:label xml:lang="en">Type</rdfs:label>
<rdfs:label xml:lang="de">Typus</rdfs:label>
<rdfs:label xml:lang="el">Τύπος</rdfs:label>
<rdfs:label xml:lang="fr">Type</rdfs:label>
<rdfs:label xml:lang="pt">Tipo</rdfs:label>
<rdfs:label xml:lang="ru">Тип</rdfs:label>
<rdfs:label xml:lang="zh">类型</rdfs:label>
<rdfs:comment>This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CIDOC CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CIDOC CRM classes.
E55 Type is the CIDOC CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CIDOC CRM as subclasses of E55 Type, forming hierarchies of terms, i.e., instances of E55 Type linked via P127 has broader term (has narrower term): E55 Type. Such hierarchies may be extended with additional properties.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E28_Conceptual_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E56_Language">
<rdfs:label xml:lang="en">Language</rdfs:label>
<rdfs:label xml:lang="de">Sprache</rdfs:label>
<rdfs:label xml:lang="el">Γλώσσα</rdfs:label>
<rdfs:label xml:lang="fr">Langue</rdfs:label>
<rdfs:label xml:lang="pt">Língua</rdfs:label>
<rdfs:label xml:lang="ru">Язык</rdfs:label>
<rdfs:label xml:lang="zh">语种</rdfs:label>
<rdfs:comment>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-1:2002 and later versions.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E55_Type" />
</rdfs:Class>
<rdfs:Class rdf:about="E57_Material">
<rdfs:label xml:lang="en">Material</rdfs:label>
<rdfs:label xml:lang="de">Material</rdfs:label>
<rdfs:label xml:lang="el">Υλικό</rdfs:label>
<rdfs:label xml:lang="fr">Matériau</rdfs:label>
<rdfs:label xml:lang="pt">Material</rdfs:label>
<rdfs:label xml:lang="ru">Материал</rdfs:label>
<rdfs:label xml:lang="zh">材质</rdfs:label>
<rdfs:comment>This class is a specialization of E55 Type and comprises the concepts of materials.
Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi's temple, should be modelled as parts (cf. P46 is composed of (forms part of): E18 Physical Thing).
This type is used categorically in the model without reference to instances of it, i.e., the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”.
It is recommended that internationally or nationally agreed codes and terminology are used.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E55_Type" />
</rdfs:Class>
<rdfs:Class rdf:about="E58_Measurement_Unit">
<rdfs:label xml:lang="en">Measurement Unit</rdfs:label>
<rdfs:label xml:lang="de">Maßeinheit</rdfs:label>
<rdfs:label xml:lang="el">Μονάδα Μέτρησης</rdfs:label>
<rdfs:label xml:lang="fr">Unité de mesure</rdfs:label>
<rdfs:label xml:lang="pt">Unidade de Medida</rdfs:label>
<rdfs:label xml:lang="ru">Единица Измерения</rdfs:label>
<rdfs:label xml:lang="zh">测量单位</rdfs:label>
<rdfs:comment>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, such as those defined by ISO80000:2009. Archaic Measurement Units used in historical records should be preserved.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E55_Type" />
</rdfs:Class>
<rdfs:Class rdf:about="E63_Beginning_of_Existence">
<rdfs:label xml:lang="en">Beginning of Existence</rdfs:label>
<rdfs:label xml:lang="de">Daseinsbeginn</rdfs:label>
<rdfs:label xml:lang="el">Αρχή Ύπαρξης</rdfs:label>
<rdfs:label xml:lang="fr">Début d'existence</rdfs:label>
<rdfs:label xml:lang="pt">Início da Existência</rdfs:label>
<rdfs:label xml:lang="ru">Начало Существования</rdfs:label>
<rdfs:label xml:lang="zh">初始</rdfs:label>
<rdfs:comment>This class comprises events that bring into existence any instance of E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E5_Event" />
</rdfs:Class>
<rdfs:Class rdf:about="E64_End_of_Existence">
<rdfs:label xml:lang="en">End of Existence</rdfs:label>
<rdfs:label xml:lang="de">Daseinsende</rdfs:label>
<rdfs:label xml:lang="el">Τέλος Ύπαρξης</rdfs:label>
<rdfs:label xml:lang="fr">Fin d'existence</rdfs:label>
<rdfs:label xml:lang="pt">Fim da Existência</rdfs:label>
<rdfs:label xml:lang="ru">Конец Существования</rdfs:label>
<rdfs:label xml:lang="zh">结束</rdfs:label>
<rdfs:comment>This class comprises events that end the existence of any instance of 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 post quem” or “terminus ante quem”. In cases where substance from an instance of E64 Persistent Item continues to exist in a new form, the process would be documented as instances of E81 Transformation.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E5_Event" />
</rdfs:Class>
<rdfs:Class rdf:about="E65_Creation">
<rdfs:label xml:lang="en">Creation</rdfs:label>
<rdfs:label xml:lang="de">Begriffliche Schöpfung</rdfs:label>
<rdfs:label xml:lang="el">Δημιουργία</rdfs:label>
<rdfs:label xml:lang="fr">Création</rdfs:label>
<rdfs:label xml:lang="pt">Criação</rdfs:label>
<rdfs:label xml:lang="ru">Событие Творения</rdfs:label>
<rdfs:label xml:lang="zh">创建</rdfs:label>
<rdfs:comment>This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
<rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E66_Formation">
<rdfs:label xml:lang="en">Formation</rdfs:label>
<rdfs:label xml:lang="de">Gruppenbildung</rdfs:label>
<rdfs:label xml:lang="el">Συγκρότηση Ομάδας</rdfs:label>
<rdfs:label xml:lang="fr">Formation</rdfs:label>
<rdfs:label xml:lang="pt">Formação</rdfs:label>
<rdfs:label xml:lang="ru">Событие Формирования</rdfs:label>
<rdfs:label xml:lang="zh">组成</rdfs:label>
<rdfs:comment>This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E7_Activity" />
<rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E67_Birth">
<rdfs:label xml:lang="en">Birth</rdfs:label>
<rdfs:label xml:lang="de">Geburt</rdfs:label>
<rdfs:label xml:lang="el">Γέννηση</rdfs:label>
<rdfs:label xml:lang="fr">Naissance</rdfs:label>
<rdfs:label xml:lang="pt">Nascimento</rdfs:label>
<rdfs:label xml:lang="ru">Рождение</rdfs:label>
<rdfs:label xml:lang="zh">出生</rdfs:label>
<rdfs:comment>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 being).
Twins, triplets etc. are typically brought into life by the same instance of E67 Birth. The introduction of E67 Birth 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 birth.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E63_Beginning_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E68_Dissolution">
<rdfs:label xml:lang="en">Dissolution</rdfs:label>
<rdfs:label xml:lang="de">Gruppenauflösung</rdfs:label>
<rdfs:label xml:lang="el">Διάλυση Ομάδας</rdfs:label>
<rdfs:label xml:lang="fr">Dissolution</rdfs:label>
<rdfs:label xml:lang="pt">Dissolução</rdfs:label>
<rdfs:label xml:lang="ru">Роспуск</rdfs:label>
<rdfs:label xml:lang="zh">解散</rdfs:label>
<rdfs:comment>This class comprises the events that result in the formal or informal termination of an instance of E74 Group.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an instance of E7 Activity.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E64_End_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E69_Death">
<rdfs:label xml:lang="en">Death</rdfs:label>
<rdfs:label xml:lang="de">Tod</rdfs:label>
<rdfs:label xml:lang="el">Θάνατος</rdfs:label>
<rdfs:label xml:lang="fr">Mort</rdfs:label>
<rdfs:label xml:lang="pt">Morte</rdfs:label>
<rdfs:label xml:lang="ru">Смерть</rdfs:label>
<rdfs:label xml:lang="zh">死亡</rdfs:label>
<rdfs:comment>This class comprises the deaths of human beings.
If a person is killed, the death should be documented as an instance of both E69 Death and E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E64_End_of_Existence" />
</rdfs:Class>
<rdfs:Class rdf:about="E70_Thing">
<rdfs:label xml:lang="en">Thing</rdfs:label>
<rdfs:label xml:lang="de">Sache</rdfs:label>
<rdfs:label xml:lang="el">Πράγμα</rdfs:label>
<rdfs:label xml:lang="fr">Chose</rdfs:label>
<rdfs:label xml:lang="pt">Coisa</rdfs:label>
<rdfs:label xml:lang="ru">Вещь</rdfs:label>
<rdfs:label xml:lang="zh">事物</rdfs:label>
<rdfs:comment>This general class comprises discrete, identifiable, instances of E77 Persistent Item that are documented as single units, that either consist of matter or depend on being carried by matter and are characterized by relative stability.
They may be intellectual products or physical things. They may for instance have a solid physical form, an electronic encoding, or they may be a logical concept or structure.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E77_Persistent_Item" />
</rdfs:Class>
<rdfs:Class rdf:about="E71_Human-Made_Thing">
<rdfs:label xml:lang="en">Human-Made Thing</rdfs:label>
<rdfs:comment>This class comprises discrete, identifiable human-made items that are documented as single units.
These items are either intellectual products or human-made physical things, and are characterized by relative stability. They may for instance have a solid physical form, an electronic encoding, or they may be logical concepts or structures.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E70_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E72_Legal_Object">
<rdfs:label xml:lang="en">Legal Object</rdfs:label>
<rdfs:label xml:lang="de">Rechtsobjekt</rdfs:label>
<rdfs:label xml:lang="el">Νομικό Αντικείμενο</rdfs:label>
<rdfs:label xml:lang="fr">Objet juridique</rdfs:label>
<rdfs:label xml:lang="pt">Objeto Jurídico</rdfs:label>
<rdfs:label xml:lang="ru">Объект Права</rdfs:label>
<rdfs:label xml:lang="zh">法律对象</rdfs:label>
<rdfs:comment>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 instances of E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of an instance of 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 CIDOC CRM.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E70_Thing" />
</rdfs:Class>
<rdfs:Class rdf:about="E73_Information_Object">
<rdfs:label xml:lang="en">Information Object</rdfs:label>
<rdfs:label xml:lang="de">Informationsgegenstand</rdfs:label>
<rdfs:label xml:lang="el">Πληροφοριακό Αντικείμενο</rdfs:label>
<rdfs:label xml:lang="fr">Objet d'information</rdfs:label>
<rdfs:label xml:lang="pt">Objeto de Informação</rdfs:label>
<rdfs:label xml:lang="ru">Информационный Объект</rdfs:label>
<rdfs:label xml:lang="zh">信息对象</rdfs:label>
<rdfs:comment>This class comprises identifiable immaterial items, such as poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. The encoding structure known as a "named graph" also falls under this class, so that each "named graph" is an instance of E73 Information Object.
An instance of 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.</rdfs:comment>
<rdfs:subClassOf rdf:resource="E89_Propositional_Object" />
<rdfs:subClassOf rdf:resource="E90_Symbolic_Object" />
</rdfs:Class>
<rdfs:Class rdf:about="E74_Group">
<rdfs:label xml:lang="en">Group</rdfs:label>
<rdfs:label xml:lang="de">Menschliche Gruppe</rdfs:label>
<rdfs:label xml:lang="el">Ομάδα</rdfs:label>
<rdfs:label xml:lang="fr">Groupe</rdfs:label>
<rdfs:label xml:lang="pt">Grupo</rdfs:label>
<rdfs:label xml:lang="ru">Группа</rdfs:label>
<rdfs:label xml:lang="zh">团体</rdfs:label>
<rdfs:comment>This class comprises any gatherings or organizations of human individuals or groups 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. In such cases, it may happen that the group never had more than one member. A joint pseudonym (i.e., a name that seems indicative of an individual but that is actually used as a persona by two or more people) is a particular case of E74 Group.
A gathering of people becomes an instance of 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 modelled as membership in an instance of E74 Group. Married couples and other concepts of family are regarded as particular examples of E74 Group.</rdfs:comment>