rdf-vocab 3.0.0 → 3.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/VERSION +1 -1
- data/lib/rdf/vocab/crm.rb +344 -344
- data/lib/rdf/vocab/datacite.rb +19 -19
- data/lib/rdf/vocab/dcat.rb +70 -94
- data/lib/rdf/vocab/disco.rb +72 -72
- data/lib/rdf/vocab/doap.rb +101 -112
- data/lib/rdf/vocab/ebucore.rb +125 -127
- data/lib/rdf/vocab/edm.rb +28 -28
- data/lib/rdf/vocab/exif.rb +70 -70
- data/lib/rdf/vocab/geonames.rb +1276 -1276
- data/lib/rdf/vocab/gr.rb +52 -52
- data/lib/rdf/vocab/ical.rb +68 -68
- data/lib/rdf/vocab/identifiers.rb +4 -4
- data/lib/rdf/vocab/ma.rb +4 -4
- data/lib/rdf/vocab/mads.rb +5 -5
- data/lib/rdf/vocab/mo.rb +69 -69
- data/lib/rdf/vocab/ogc.rb +1 -1
- data/lib/rdf/vocab/org.rb +113 -114
- data/lib/rdf/vocab/premis.rb +168 -168
- data/lib/rdf/vocab/premis_event_type.rb +18 -18
- data/lib/rdf/vocab/prov.rb +34 -34
- data/lib/rdf/vocab/skosxl.rb +2 -2
- data/lib/rdf/vocab/vcard.rb +48 -48
- data/lib/rdf/vocab/xkos.rb +48 -48
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 8ba87947f17e4fcbd1c46398188efcb9640ea5aa8906e0c7d369ba64678983f5
|
4
|
+
data.tar.gz: cef965ad01660a0325732b45a9a7dd19e3ac7ad58b04df597ecbeffe70e4ee46
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1a1524af92c10ad2751a9784932474a6e4547bc8b65597c7a7220b0d2239e614c0c532591a1ae64a12c211e3503845c611b25a35fbaa0efddf57bd64b5c7673b
|
7
|
+
data.tar.gz: dd97baecfda67084bceb8f36c039fe307a2c26d458524ef5b52fddc53eedf1e29753cd479772da0d9678b42f12c2fff620b19ef295467339d598492250b5c0b4
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
3.0.
|
1
|
+
3.0.1
|
data/lib/rdf/vocab/crm.rb
CHANGED
@@ -21,7 +21,7 @@ The recording of the donor and/or recipient is optional. It is possible that in
|
|
21
21
|
The distinction between the legal responsibility for custody and the actual physical possession of the object should be expressed using the property P2 has type \(is type of\). A specific case of transfer of custody is theft.
|
22
22
|
The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership and physical custody separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
|
23
23
|
).freeze,
|
24
|
-
label:
|
24
|
+
label: "Transfer of Custody".freeze,
|
25
25
|
subClassOf: "crm:E7_Activity".freeze,
|
26
26
|
type: "rdfs:Class".freeze
|
27
27
|
term :E11_Modification,
|
@@ -30,7 +30,7 @@ This class includes the production of an item from raw materials, and other so f
|
|
30
30
|
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 a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities.
|
31
31
|
If the instance of the 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.
|
32
32
|
).freeze,
|
33
|
-
label:
|
33
|
+
label: "Modification".freeze,
|
34
34
|
subClassOf: "crm:E7_Activity".freeze,
|
35
35
|
type: "rdfs:Class".freeze
|
36
36
|
term :E12_Production,
|
@@ -39,7 +39,7 @@ It specializes the notion of modification into production. The decision as to wh
|
|
39
39
|
This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event.
|
40
40
|
An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not.
|
41
41
|
).freeze,
|
42
|
-
label:
|
42
|
+
label: "Production".freeze,
|
43
43
|
subClassOf: ["crm:E11_Modification".freeze, "crm:E63_Beginning_of_Existence".freeze],
|
44
44
|
type: "rdfs:Class".freeze
|
45
45
|
term :E13_Attribute_Assignment,
|
@@ -47,14 +47,14 @@ An event should also be documented using E81 Transformation if it results in the
|
|
47
47
|
This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as "short cuts" of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules.
|
48
48
|
In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries.
|
49
49
|
).freeze,
|
50
|
-
label:
|
50
|
+
label: "Attribute Assignment".freeze,
|
51
51
|
subClassOf: "crm:E7_Activity".freeze,
|
52
52
|
type: "rdfs:Class".freeze
|
53
53
|
term :E14_Condition_Assessment,
|
54
54
|
comment: %(This class describes the act of assessing the state of preservation of an object during a particular period.
|
55
55
|
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.
|
56
56
|
).freeze,
|
57
|
-
label:
|
57
|
+
label: "Condition Assessment".freeze,
|
58
58
|
subClassOf: "crm:E13_Attribute_Assignment".freeze,
|
59
59
|
type: "rdfs:Class".freeze
|
60
60
|
term :E15_Identifier_Assignment,
|
@@ -62,7 +62,7 @@ The condition assessment may be carried out by inspection, measurement or throug
|
|
62
62
|
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.
|
63
63
|
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.
|
64
64
|
).freeze,
|
65
|
-
label:
|
65
|
+
label: "Identifier Assignment".freeze,
|
66
66
|
subClassOf: "crm:E13_Attribute_Assignment".freeze,
|
67
67
|
type: "rdfs:Class".freeze
|
68
68
|
term :E16_Measurement,
|
@@ -70,14 +70,14 @@ The fact that an identifier is a preferred one for an organisation can be expres
|
|
70
70
|
Examples include measuring the monetary value of a collection of coins or the running time of a specific video cassette.
|
71
71
|
The E16 Measurement may use 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. Details of methods and devices are best handled as free text, whereas basic techniques such as "carbon 14 dating" should be encoded using P2 has type \(is type of:\) E55 Type.
|
72
72
|
).freeze,
|
73
|
-
label:
|
73
|
+
label: "Measurement".freeze,
|
74
74
|
subClassOf: "crm:E13_Attribute_Assignment".freeze,
|
75
75
|
type: "rdfs:Class".freeze
|
76
76
|
term :E17_Type_Assignment,
|
77
77
|
comment: %(This class comprises the actions of classifying items of whatever kind. Such items include objects, specimens, people, actions and concepts.
|
78
78
|
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.
|
79
79
|
).freeze,
|
80
|
-
label:
|
80
|
+
label: "Type Assignment".freeze,
|
81
81
|
subClassOf: "crm:E13_Attribute_Assignment".freeze,
|
82
82
|
type: "rdfs:Class".freeze
|
83
83
|
term :E18_Physical_Thing,
|
@@ -85,7 +85,7 @@ This class allows for the documentation of the context of classification acts in
|
|
85
85
|
Depending on the existence of natural boundaries of such things, the CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved \(if not too heavy\), whereas features are integral to the surrounding matter.
|
86
86
|
The CRM is generally not concerned with amounts of matter in fluid or gaseous states.
|
87
87
|
).freeze,
|
88
|
-
label:
|
88
|
+
label: "Physical Thing".freeze,
|
89
89
|
subClassOf: "crm:E72_Legal_Object".freeze,
|
90
90
|
type: "rdfs:Class".freeze
|
91
91
|
term :E19_Physical_Object,
|
@@ -94,7 +94,7 @@ The class also includes all aggregates of objects made for functional purposes o
|
|
94
94
|
In some contexts, such objects, except for aggregates, are also called “bona fide objects” \(Smith & Varzi, 2000, pp.401-420\), i.e. naturally defined objects.
|
95
95
|
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.
|
96
96
|
).freeze,
|
97
|
-
label:
|
97
|
+
label: "Physical Object".freeze,
|
98
98
|
subClassOf: "crm:E18_Physical_Thing".freeze,
|
99
99
|
type: "rdfs:Class".freeze
|
100
100
|
term :E1_CRM_Entity,
|
@@ -105,41 +105,41 @@ It is an abstract concept providing for three general properties:
|
|
105
105
|
3. Attachment of free text for the expression of anything not captured by formal properties
|
106
106
|
With the exception of E59 Primitive Value, all other classes within the CRM are directly or indirectly specialisations of E1 CRM Entity.
|
107
107
|
).freeze,
|
108
|
-
label:
|
108
|
+
label: "CRM Entity".freeze,
|
109
109
|
type: "rdfs:Class".freeze
|
110
110
|
term :E20_Biological_Object,
|
111
111
|
comment: %(This class comprises individual items of a material nature, which live, have lived or are natural products of or from living organisms.
|
112
112
|
Artificial objects that incorporate biological elements, such as Victorian butterfly frames, can be documented as both instances of E20 Biological Object and E22 Man-Made Object.
|
113
113
|
).freeze,
|
114
|
-
label:
|
114
|
+
label: "Biological Object".freeze,
|
115
115
|
subClassOf: "crm:E19_Physical_Object".freeze,
|
116
116
|
type: "rdfs:Class".freeze
|
117
117
|
term :E21_Person,
|
118
118
|
comment: %(This class comprises real persons who live or are assumed to have lived.
|
119
119
|
Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CRM does not propose a specific form to support reasoning about possible identity.
|
120
120
|
).freeze,
|
121
|
-
label:
|
121
|
+
label: "Person".freeze,
|
122
122
|
subClassOf: ["crm:E20_Biological_Object".freeze, "crm:E39_Actor".freeze],
|
123
123
|
type: "rdfs:Class".freeze
|
124
124
|
term :"E22_Man-Made_Object",
|
125
125
|
comment: %(This class comprises physical objects purposely created by human activity.
|
126
126
|
No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, an inscribed piece of rock or a preserved butterfly are both regarded as instances of E22 Man-Made Object.
|
127
127
|
).freeze,
|
128
|
-
label:
|
128
|
+
label: "Man-Made Object".freeze,
|
129
129
|
subClassOf: ["crm:E19_Physical_Object".freeze, "crm:E24_Physical_Man-Made_Thing".freeze],
|
130
130
|
type: "rdfs:Class".freeze
|
131
131
|
term :"E24_Physical_Man-Made_Thing",
|
132
132
|
comment: %(This class comprises all persistent physical items that are purposely created by human activity.
|
133
133
|
This class comprises man-made objects, such as a swords, and man-made features, such as rock art. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Man-Made Thing.
|
134
134
|
).freeze,
|
135
|
-
label:
|
135
|
+
label: "Physical Man-Made Thing".freeze,
|
136
136
|
subClassOf: ["crm:E18_Physical_Thing".freeze, "crm:E71_Man-Made_Thing".freeze],
|
137
137
|
type: "rdfs:Class".freeze
|
138
138
|
term :"E25_Man-Made_Feature",
|
139
139
|
comment: %(This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc.
|
140
140
|
No assumptions are made as to the extent of modification required to justify regarding a feature as man-made. For example, rock art or even “cup and ring” carvings on bedrock a regarded as types of E25 Man-Made Feature.
|
141
141
|
).freeze,
|
142
|
-
label:
|
142
|
+
label: "Man-Made Feature".freeze,
|
143
143
|
subClassOf: ["crm:E24_Physical_Man-Made_Thing".freeze, "crm:E26_Physical_Feature".freeze],
|
144
144
|
type: "rdfs:Class".freeze
|
145
145
|
term :E26_Physical_Feature,
|
@@ -148,14 +148,14 @@ Instances of E26 Physical Feature share many of the attributes of instances of E
|
|
148
148
|
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.
|
149
149
|
This definition coincides with the definition of "fiat objects" \(Smith & Varzi, 2000, pp.401-420\), with the exception of aggregates of “bona fide objects”.
|
150
150
|
).freeze,
|
151
|
-
label:
|
151
|
+
label: "Physical Feature".freeze,
|
152
152
|
subClassOf: "crm:E18_Physical_Thing".freeze,
|
153
153
|
type: "rdfs:Class".freeze
|
154
154
|
term :E27_Site,
|
155
155
|
comment: %(This class comprises pieces of land or sea floor.
|
156
156
|
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.
|
157
157
|
Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location).freeze,
|
158
|
-
label:
|
158
|
+
label: "Site".freeze,
|
159
159
|
subClassOf: "crm:E26_Physical_Feature".freeze,
|
160
160
|
type: "rdfs:Class".freeze
|
161
161
|
term :E28_Conceptual_Object,
|
@@ -163,7 +163,7 @@ In contrast to the purely geometric notion of E53 Place, this class describes co
|
|
163
163
|
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.
|
164
164
|
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.
|
165
165
|
).freeze,
|
166
|
-
label:
|
166
|
+
label: "Conceptual Object".freeze,
|
167
167
|
subClassOf: "crm:E71_Man-Made_Thing".freeze,
|
168
168
|
type: "rdfs:Class".freeze
|
169
169
|
term :E29_Design_or_Procedure,
|
@@ -175,33 +175,33 @@ Designs or procedures can be seen as one of the following:
|
|
175
175
|
3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci’s famous plans for flying machines.
|
176
176
|
Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product.
|
177
177
|
).freeze,
|
178
|
-
label:
|
178
|
+
label: "Design or Procedure".freeze,
|
179
179
|
subClassOf: "crm:E73_Information_Object".freeze,
|
180
180
|
type: "rdfs:Class".freeze
|
181
181
|
term :E2_Temporal_Entity,
|
182
182
|
comment: %(This class comprises all phenomena, such as the instances of E4 Periods, E5 Events and states, which happen over a limited extent in time.
|
183
183
|
In some contexts, these are also called perdurants. This class is disjoint from E77 Persistent Item. This is an abstract class and has no direct instances. E2 Temporal Entity is specialized into E4 Period, which applies to a particular geographic area \(defined with a greater or lesser degree of precision\), and E3 Condition State, which applies to instances of E18 Physical Thing.
|
184
184
|
).freeze,
|
185
|
-
label:
|
185
|
+
label: "Temporal Entity".freeze,
|
186
186
|
subClassOf: "crm:E1_CRM_Entity".freeze,
|
187
187
|
type: "rdfs:Class".freeze
|
188
188
|
term :E30_Right,
|
189
189
|
comment: %(This class comprises legal privileges concerning material and immaterial things or their derivatives.
|
190
190
|
These include reproduction and property rights).freeze,
|
191
|
-
label:
|
191
|
+
label: "Right".freeze,
|
192
192
|
subClassOf: "crm:E89_Propositional_Object".freeze,
|
193
193
|
type: "rdfs:Class".freeze
|
194
194
|
term :E31_Document,
|
195
195
|
comment: %(This class comprises identifiable immaterial items that make propositions about reality.
|
196
196
|
These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as a special case of E31 Document. This class should not be confused with the term “document” in Information Technology, which is compatible with E73 Information Object.
|
197
197
|
).freeze,
|
198
|
-
label:
|
198
|
+
label: "Document".freeze,
|
199
199
|
subClassOf: "crm:E73_Information_Object".freeze,
|
200
200
|
type: "rdfs:Class".freeze
|
201
201
|
term :E32_Authority_Document,
|
202
202
|
comment: %(This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use.
|
203
203
|
).freeze,
|
204
|
-
label:
|
204
|
+
label: "Authority Document".freeze,
|
205
205
|
subClassOf: "crm:E31_Document".freeze,
|
206
206
|
type: "rdfs:Class".freeze
|
207
207
|
term :E33_Linguistic_Object,
|
@@ -209,7 +209,7 @@ These propositions may be expressed in text, graphics, images, audiograms, video
|
|
209
209
|
Instances of E33 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech or sign language. However, the 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 CRM. These should be modelled as instances of E73 Information Object.
|
210
210
|
The text of an instance of E33 Linguistic Object can be documented in a note by P3 has note: E62 String
|
211
211
|
).freeze,
|
212
|
-
label:
|
212
|
+
label: "Linguistic Object".freeze,
|
213
213
|
subClassOf: "crm:E73_Information_Object".freeze,
|
214
214
|
type: "rdfs:Class".freeze
|
215
215
|
term :E34_Inscription,
|
@@ -217,7 +217,7 @@ The text of an instance of E33 Linguistic Object can be documented in a note by
|
|
217
217
|
The transcription of the text can be documented in a note by P3 has note: E62 String. The alphabet used can be documented by P2 has type: E55 Type. This class does not intend to describe the idiosyncratic characteristics of an individual physical embodiment of an inscription, but the underlying prototype. The physical embodiment is modelled in the CRM as E24 Physical Man-Made Thing.
|
218
218
|
The relationship of a physical copy of a book to the text it contains is modelled using E84 Information Carrier. P128 carries \(is carried by\): E33 Linguistic Object.
|
219
219
|
).freeze,
|
220
|
-
label:
|
220
|
+
label: "Inscription".freeze,
|
221
221
|
subClassOf: ["crm:E33_Linguistic_Object".freeze, "crm:E37_Mark".freeze],
|
222
222
|
type: "rdfs:Class".freeze
|
223
223
|
term :E35_Title,
|
@@ -225,7 +225,7 @@ The relationship of a physical copy of a book to the text it contains is modelle
|
|
225
225
|
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.
|
226
226
|
This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts.
|
227
227
|
).freeze,
|
228
|
-
label:
|
228
|
+
label: "Title".freeze,
|
229
229
|
subClassOf: ["crm:E33_Linguistic_Object".freeze, "crm:E41_Appellation".freeze],
|
230
230
|
type: "rdfs:Class".freeze
|
231
231
|
term :E36_Visual_Item,
|
@@ -233,28 +233,28 @@ This class also comprises the translations of titles that are used as surrogates
|
|
233
233
|
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.
|
234
234
|
The class E36 Visual Item provides a means of identifying and linking together instances of E24 Physical Man-Made Thing that carry the same visual symbols, marks or images etc. The property P62 depicts \(is depicted by\) between E24 Physical Man-Made Thing and depicted subjects \(E1 CRM Entity\) can be regarded as a short-cut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item \(is shown by\), E36 Visual Item, P138 represents \(has representation\) to E1CRM Entity, which in addition captures the optical features of the depiction.
|
235
235
|
).freeze,
|
236
|
-
label:
|
236
|
+
label: "Visual Item".freeze,
|
237
237
|
subClassOf: "crm:E73_Information_Object".freeze,
|
238
238
|
type: "rdfs:Class".freeze
|
239
239
|
term :E37_Mark,
|
240
240
|
comment: %(This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Man-Made Thing by arbitrary techniques in order to indicate the creator, owner, dedications, purpose, etc.
|
241
241
|
This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Man-Made Feature.
|
242
242
|
).freeze,
|
243
|
-
label:
|
243
|
+
label: "Mark".freeze,
|
244
244
|
subClassOf: "crm:E36_Visual_Item".freeze,
|
245
245
|
type: "rdfs:Class".freeze
|
246
246
|
term :E38_Image,
|
247
247
|
comment: %(This class comprises distributions of form, tone and colour that may be found on surfaces such as photos, paintings, prints and sculptures or directly on electronic media.
|
248
248
|
The degree to which variations in the distribution of form and colour affect the identity of an instance of E38 Image depends on a given purpose. The original painting of the Mona Lisa in the Louvre may be said to bear the same instance of E38 Image as reproductions in the form of transparencies, postcards, posters or T-shirts, even though they may differ in size and carrier and may vary in tone and colour. The images in a “spot the difference” competition are not the same with respect to their context, however similar they may at first appear.
|
249
249
|
).freeze,
|
250
|
-
label:
|
250
|
+
label: "Image".freeze,
|
251
251
|
subClassOf: "crm:E36_Visual_Item".freeze,
|
252
252
|
type: "rdfs:Class".freeze
|
253
253
|
term :E39_Actor,
|
254
254
|
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.
|
255
255
|
The CRM does not attempt to model the inadvertent actions of such actors. Individual people should be documented as instances of E21 Person, whereas groups should be documented as instances of either E74 Group or its subclass E40 Legal Body.
|
256
256
|
).freeze,
|
257
|
-
label:
|
257
|
+
label: "Actor".freeze,
|
258
258
|
subClassOf: "crm:E77_Persistent_Item".freeze,
|
259
259
|
type: "rdfs:Class".freeze
|
260
260
|
term :E3_Condition_State,
|
@@ -262,14 +262,14 @@ The CRM does not attempt to model the inadvertent actions of such actors. Indivi
|
|
262
262
|
An instance of this class describes the prevailing physical condition of any material object or feature during a specific 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.
|
263
263
|
The nature of that condition can be described using P2 has type. For example, the E3 Condition State “condition of the SS Great Britain between 22 September 1846 and 27 August 1847” can be characterized as E55 Type “wrecked”.
|
264
264
|
).freeze,
|
265
|
-
label:
|
265
|
+
label: "Condition State".freeze,
|
266
266
|
subClassOf: "crm:E2_Temporal_Entity".freeze,
|
267
267
|
type: "rdfs:Class".freeze
|
268
268
|
term :E40_Legal_Body,
|
269
269
|
comment: %(This class comprises institutions or groups of people that have obtained a legal recognition as a group and can act collectively as agents.
|
270
270
|
This means that they can perform actions, own property, create or destroy things and can be held collectively responsible for their actions like individual people. The term 'personne morale' is often used for this in French.
|
271
271
|
).freeze,
|
272
|
-
label:
|
272
|
+
label: "Legal Body".freeze,
|
273
273
|
subClassOf: "crm:E74_Group".freeze,
|
274
274
|
type: "rdfs:Class".freeze
|
275
275
|
term :E41_Appellation,
|
@@ -278,33 +278,33 @@ Instances of E41 Appellation do not identify things by their meaning, even if th
|
|
278
278
|
Specific subclasses of E41 Appellation should be used when instances of E41 Appellation of a characteristic form are used for particular objects. Instances of E49 Time Appellation, for example, which take the form of instances of E50 Date, can be easily recognised.
|
279
279
|
E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment
|
280
280
|
).freeze,
|
281
|
-
label:
|
281
|
+
label: "Appellation".freeze,
|
282
282
|
subClassOf: "crm:E90_Symbolic_Object".freeze,
|
283
283
|
type: "rdfs:Class".freeze
|
284
284
|
term :E42_Identifier,
|
285
285
|
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. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents.).freeze,
|
286
|
-
label:
|
286
|
+
label: "Identifier".freeze,
|
287
287
|
subClassOf: "crm:E41_Appellation".freeze,
|
288
288
|
type: "rdfs:Class".freeze
|
289
289
|
term :E44_Place_Appellation,
|
290
290
|
comment: %(This class comprises any sort of identifier characteristically used to refer to an E53 Place.
|
291
291
|
Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time - the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation.
|
292
292
|
).freeze,
|
293
|
-
label:
|
293
|
+
label: "Place Appellation".freeze,
|
294
294
|
subClassOf: "crm:E41_Appellation".freeze,
|
295
295
|
type: "rdfs:Class".freeze
|
296
296
|
term :E45_Address,
|
297
297
|
comment: %(This class comprises identifiers expressed in coding systems for places, such as postal addresses used for mailing.
|
298
298
|
An E45 Address can be considered both as the name of an E53 Place and as an E51 Contact Point for an E39 Actor. This dual aspect is reflected in the multiple inheritance. However, some forms of mailing addresses, such as a postal box, are only instances of E51 Contact Point, since they do not identify any particular Place. These should not be documented as instances of E45 Address.
|
299
299
|
).freeze,
|
300
|
-
label:
|
300
|
+
label: "Address".freeze,
|
301
301
|
subClassOf: ["crm:E44_Place_Appellation".freeze, "crm:E51_Contact_Point".freeze],
|
302
302
|
type: "rdfs:Class".freeze
|
303
303
|
term :E46_Section_Definition,
|
304
304
|
comment: %(This class comprises areas of objects referred to in terms specific to the general geometry or structure of its kind.
|
305
305
|
The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building are all instances of E46 Section Definition. The class highlights the fact that parts of objects can be treated as locations. This holds in particular for features without natural boundaries, such as the “head” of a marble statue made out of one block \(cf. E53 Place\). In answer to the question 'where is the signature?' one might reply 'on the lower left corner'. \(Section Definition is closely related to the term “segment” in Gerstl, P.& Pribbenow, S, 1996 “ A conceptual theory of part – whole relations and its applications”, Data & Knowledge Engineering 20 305-322, North Holland- Elsevier \).
|
306
306
|
).freeze,
|
307
|
-
label:
|
307
|
+
label: "Section Definition".freeze,
|
308
308
|
subClassOf: "crm:E44_Place_Appellation".freeze,
|
309
309
|
type: "rdfs:Class".freeze
|
310
310
|
term :E47_Spatial_Coordinates,
|
@@ -312,19 +312,19 @@ The 'prow' of the boat, the 'frame' of the picture, the 'front' of the building
|
|
312
312
|
|
313
313
|
Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates.
|
314
314
|
).freeze,
|
315
|
-
label:
|
315
|
+
label: "Spatial Coordinates".freeze,
|
316
316
|
subClassOf: "crm:E44_Place_Appellation".freeze,
|
317
317
|
type: "rdfs:Class".freeze
|
318
318
|
term :E48_Place_Name,
|
319
319
|
comment: %(This class comprises particular and common forms of E44 Place Appellation.
|
320
320
|
Place Names may change their application over time: the name of an E53 Place may change, and a name may be reused for a different E53 Place. Instances of E48 Place Name are typically subject to place name gazetteers.).freeze,
|
321
|
-
label:
|
321
|
+
label: "Place Name".freeze,
|
322
322
|
subClassOf: "crm:E44_Place_Appellation".freeze,
|
323
323
|
type: "rdfs:Class".freeze
|
324
324
|
term :E49_Time_Appellation,
|
325
325
|
comment: %(This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span.
|
326
326
|
The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’.).freeze,
|
327
|
-
label:
|
327
|
+
label: "Time Appellation".freeze,
|
328
328
|
subClassOf: "crm:E41_Appellation".freeze,
|
329
329
|
type: "rdfs:Class".freeze
|
330
330
|
term :E4_Period,
|
@@ -339,19 +339,19 @@ There are no assumptions about the scale of the associated phenomena. In particu
|
|
339
339
|
There are two different conceptualisations of ‘artistic style’, defined either by physical features or by historical context. For example, “Impressionism” can be viewed as a period lasting from approximately 1870 to 1905 during which paintings with particular characteristics were produced by a group of artists that included \(among others\) Monet, Renoir, Pissarro, Sisley and Degas. Alternatively, it can be regarded as a style applicable to all paintings sharing the characteristics of the works produced by the Impressionist painters, regardless of historical context. The first interpretation is an E4 Period, and the second defines morphological object types that fall under E55 Type.
|
340
340
|
Another specific case of an E4 Period is the set of activities and phenomena associated with a settlement, such as the populated period of Nineveh.
|
341
341
|
).freeze,
|
342
|
-
label:
|
342
|
+
label: "Period".freeze,
|
343
343
|
subClassOf: "crm:E2_Temporal_Entity".freeze,
|
344
344
|
type: "rdfs:Class".freeze
|
345
345
|
term :E50_Date,
|
346
346
|
comment: %(This class comprises specific forms of E49 Time Appellation.).freeze,
|
347
|
-
label:
|
347
|
+
label: "Date".freeze,
|
348
348
|
subClassOf: "crm:E49_Time_Appellation".freeze,
|
349
349
|
type: "rdfs:Class".freeze
|
350
350
|
term :E51_Contact_Point,
|
351
351
|
comment: %(This class comprises identifiers employed, or understood, by communication services to direct communications to an instance of E39 Actor. These include E-mail addresses, telephone numbers, post office boxes, Fax numbers, URLs etc. Most postal addresses can be considered both as instances of E44 Place Appellation and E51 Contact Point. In such cases the subclass E45 Address should be used.
|
352
352
|
URLs are addresses used by machines to access another machine through an http request. Since the accessed machine acts on behalf of the E39 Actor providing the machine, URLs are considered as instances of E51 Contact Point to that E39 Actor.
|
353
353
|
).freeze,
|
354
|
-
label:
|
354
|
+
label: "Contact Point".freeze,
|
355
355
|
subClassOf: "crm:E41_Appellation".freeze,
|
356
356
|
type: "rdfs:Class".freeze
|
357
357
|
term :"E52_Time-Span",
|
@@ -360,7 +360,7 @@ Time Span has no other semantic connotations. Time-Spans are used to define the
|
|
360
360
|
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
|
361
361
|
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
|
362
362
|
).freeze,
|
363
|
-
label:
|
363
|
+
label: "Time-Span".freeze,
|
364
364
|
subClassOf: "crm:E1_CRM_Entity".freeze,
|
365
365
|
type: "rdfs:Class".freeze
|
366
366
|
term :E53_Place,
|
@@ -368,7 +368,7 @@ Since our knowledge of history is imperfect, instances of E52 Time-Span can best
|
|
368
368
|
The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation.
|
369
369
|
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.
|
370
370
|
Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a "section" of an E19 Physical Object as a valid E53 Place determination.).freeze,
|
371
|
-
label:
|
371
|
+
label: "Place".freeze,
|
372
372
|
subClassOf: "crm:E1_CRM_Entity".freeze,
|
373
373
|
type: "rdfs:Class".freeze
|
374
374
|
term :E54_Dimension,
|
@@ -376,14 +376,14 @@ Any object can serve as a frame of reference for E53 Place determination. The mo
|
|
376
376
|
An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, 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 interoperability of values described in different units depends critically on the representation as value regions.
|
377
377
|
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.
|
378
378
|
).freeze,
|
379
|
-
label:
|
379
|
+
label: "Dimension".freeze,
|
380
380
|
subClassOf: "crm:E1_CRM_Entity".freeze,
|
381
381
|
type: "rdfs:Class".freeze
|
382
382
|
term :E55_Type,
|
383
383
|
comment: %(This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes.
|
384
384
|
E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term \(has narrower term\). Such hierarchies may be extended with additional properties.
|
385
385
|
).freeze,
|
386
|
-
label:
|
386
|
+
label: "Type".freeze,
|
387
387
|
subClassOf: "crm:E28_Conceptual_Object".freeze,
|
388
388
|
type: "rdfs:Class".freeze
|
389
389
|
term :E56_Language,
|
@@ -391,7 +391,7 @@ E55 Type is the CRM’s interface to domain specific ontologies and thesauri. Th
|
|
391
391
|
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”.
|
392
392
|
It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988.
|
393
393
|
).freeze,
|
394
|
-
label:
|
394
|
+
label: "Language".freeze,
|
395
395
|
subClassOf: "crm:E55_Type".freeze,
|
396
396
|
type: "rdfs:Class".freeze
|
397
397
|
term :E57_Material,
|
@@ -399,7 +399,7 @@ It is recommended that internationally or nationally agreed codes and terminolog
|
|
399
399
|
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\).
|
400
400
|
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”.
|
401
401
|
It is recommended that internationally or nationally agreed codes and terminology are used.).freeze,
|
402
|
-
label:
|
402
|
+
label: "Material".freeze,
|
403
403
|
subClassOf: "crm:E55_Type".freeze,
|
404
404
|
type: "rdfs:Class".freeze
|
405
405
|
term :E58_Measurement_Unit,
|
@@ -407,33 +407,33 @@ It is recommended that internationally or nationally agreed codes and terminolog
|
|
407
407
|
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”.
|
408
408
|
Syst?me International \(SI\) units or internationally recognized non-SI terms should be used whenever possible. \(ISO 1000:1992\). Archaic Measurement Units used in historical records should be preserved.
|
409
409
|
).freeze,
|
410
|
-
label:
|
410
|
+
label: "Measurement Unit".freeze,
|
411
411
|
subClassOf: "crm:E55_Type".freeze,
|
412
412
|
type: "rdfs:Class".freeze
|
413
413
|
term :E5_Event,
|
414
414
|
comment: %(This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses.
|
415
415
|
The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state.
|
416
416
|
).freeze,
|
417
|
-
label:
|
417
|
+
label: "Event".freeze,
|
418
418
|
subClassOf: "crm:E4_Period".freeze,
|
419
419
|
type: "rdfs:Class".freeze
|
420
420
|
term :E63_Beginning_of_Existence,
|
421
421
|
comment: %(This class comprises events that bring into existence any E77 Persistent Item.
|
422
422
|
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 and ante quem. ).freeze,
|
423
|
-
label:
|
423
|
+
label: "Beginning of Existence".freeze,
|
424
424
|
subClassOf: "crm:E5_Event".freeze,
|
425
425
|
type: "rdfs:Class".freeze
|
426
426
|
term :E64_End_of_Existence,
|
427
427
|
comment: %(This class comprises events that end the existence of any E77 Persistent Item.
|
428
428
|
It may be used for temporal reasoning about things \(physical items, groups of people, living beings\) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
|
429
429
|
).freeze,
|
430
|
-
label:
|
430
|
+
label: "End of Existence".freeze,
|
431
431
|
subClassOf: "crm:E5_Event".freeze,
|
432
432
|
type: "rdfs:Class".freeze
|
433
433
|
term :E65_Creation,
|
434
434
|
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.
|
435
435
|
).freeze,
|
436
|
-
label:
|
436
|
+
label: "Creation".freeze,
|
437
437
|
subClassOf: ["crm:E63_Beginning_of_Existence".freeze, "crm:E7_Activity".freeze],
|
438
438
|
type: "rdfs:Class".freeze
|
439
439
|
term :E66_Formation,
|
@@ -441,28 +441,28 @@ It may be used for temporal reasoning about things \(physical items, groups of p
|
|
441
441
|
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
|
442
442
|
The formation of an instance of E74 Group does not mean 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.
|
443
443
|
).freeze,
|
444
|
-
label:
|
444
|
+
label: "Formation".freeze,
|
445
445
|
subClassOf: ["crm:E63_Beginning_of_Existence".freeze, "crm:E7_Activity".freeze],
|
446
446
|
type: "rdfs:Class".freeze
|
447
447
|
term :E67_Birth,
|
448
448
|
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 beings\).
|
449
449
|
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
|
450
450
|
).freeze,
|
451
|
-
label:
|
451
|
+
label: "Birth".freeze,
|
452
452
|
subClassOf: "crm:E63_Beginning_of_Existence".freeze,
|
453
453
|
type: "rdfs:Class".freeze
|
454
454
|
term :E68_Dissolution,
|
455
455
|
comment: %(This class comprises the events that result in the formal or informal termination of an E74 Group of people.
|
456
456
|
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
|
457
457
|
).freeze,
|
458
|
-
label:
|
458
|
+
label: "Dissolution".freeze,
|
459
459
|
subClassOf: "crm:E64_End_of_Existence".freeze,
|
460
460
|
type: "rdfs:Class".freeze
|
461
461
|
term :E69_Death,
|
462
462
|
comment: %(This class comprises the deaths of human beings.
|
463
463
|
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
|
464
464
|
).freeze,
|
465
|
-
label:
|
465
|
+
label: "Death".freeze,
|
466
466
|
subClassOf: "crm:E64_End_of_Existence".freeze,
|
467
467
|
type: "rdfs:Class".freeze
|
468
468
|
term :E6_Destruction,
|
@@ -473,28 +473,28 @@ The decision to document an object as destroyed, transformed or modified is cont
|
|
473
473
|
2. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the original. In this case, the new items have separate identities. Matter is preserved, but identity is not.
|
474
474
|
3. When the initial identity of the changed instance of E18 Physical Thing is preserved, the event should be documented as E11 Modification.
|
475
475
|
).freeze,
|
476
|
-
label:
|
476
|
+
label: "Destruction".freeze,
|
477
477
|
subClassOf: "crm:E64_End_of_Existence".freeze,
|
478
478
|
type: "rdfs:Class".freeze
|
479
479
|
term :E70_Thing,
|
480
480
|
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.
|
481
481
|
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.
|
482
482
|
).freeze,
|
483
|
-
label: ["".freeze, "
|
483
|
+
label: ["".freeze, "Thing".freeze],
|
484
484
|
subClassOf: "crm:E77_Persistent_Item".freeze,
|
485
485
|
type: "rdfs:Class".freeze
|
486
486
|
term :"E71_Man-Made_Thing",
|
487
487
|
comment: %(This class comprises discrete, identifiable man-made items that are documented as single units.
|
488
488
|
These items are either intellectual products or man-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.
|
489
489
|
).freeze,
|
490
|
-
label:
|
490
|
+
label: "Man-Made Thing".freeze,
|
491
491
|
subClassOf: "crm:E70_Thing".freeze,
|
492
492
|
type: "rdfs:Class".freeze
|
493
493
|
term :E72_Legal_Object,
|
494
494
|
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.
|
495
495
|
This is true for all E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of the E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CRM.
|
496
496
|
).freeze,
|
497
|
-
label:
|
497
|
+
label: "Legal Object".freeze,
|
498
498
|
subClassOf: "crm:E70_Thing".freeze,
|
499
499
|
type: "rdfs:Class".freeze
|
500
500
|
term :E73_Information_Object,
|
@@ -502,19 +502,19 @@ This is true for all E18 Physical Thing. In the case of instances of E28 Concept
|
|
502
502
|
An E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously.
|
503
503
|
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.
|
504
504
|
).freeze,
|
505
|
-
label:
|
505
|
+
label: "Information Object".freeze,
|
506
506
|
subClassOf: ["crm:E89_Propositional_Object".freeze, "crm:E90_Symbolic_Object".freeze],
|
507
507
|
type: "rdfs:Class".freeze
|
508
508
|
term :E74_Group,
|
509
509
|
comment: %(This class comprises any gatherings or organizations of E39 Actors 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.
|
510
510
|
A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Nationality can be modeled as membership in an E74 Group \(cf. HumanML markup\). Married couples and other concepts of family are regarded as particular examples of E74 Group.
|
511
511
|
).freeze,
|
512
|
-
label:
|
512
|
+
label: "Group".freeze,
|
513
513
|
subClassOf: "crm:E39_Actor".freeze,
|
514
514
|
type: "rdfs:Class".freeze
|
515
515
|
term :E75_Conceptual_Object_Appellation,
|
516
516
|
comment: %(This class comprises appellations that are by their form or syntax specific to identifying instances of E28 Conceptual Object, such as intellectual products, standardized patterns etc.).freeze,
|
517
|
-
label:
|
517
|
+
label: "Conceptual Object Appellation".freeze,
|
518
518
|
subClassOf: "crm:E41_Appellation".freeze,
|
519
519
|
type: "rdfs:Class".freeze
|
520
520
|
term :E77_Persistent_Item,
|
@@ -522,7 +522,7 @@ A gathering of people becomes an E74 Group when it exhibits organizational chara
|
|
522
522
|
They can be repeatedly recognized within the duration of their existence by identity criteria rather than by continuity or observation. Persistent Items can be either physical entities, such as people, animals or things, or conceptual entities such as ideas, concepts, products of the imagination or common names.
|
523
523
|
The criteria that determine the identity of an item are often difficult to establish -; the decision depends largely on the judgement of the observer. For example, a building is regarded as no longer existing if it is dismantled and the materials reused in a different configuration. On the other hand, human beings go through radical and profound changes during their life-span, affecting both material composition and form, yet preserve their identity by other criteria. Similarly, inanimate objects may be subject to exchange of parts and matter. The class E77 Persistent Item does not take any position about the nature of the applicable identity criteria and if actual knowledge about identity of an instance of this class exists. There may be cases, where the identity of an E77 Persistent Item is not decidable by a certain state of knowledge.
|
524
524
|
The main classes of objects that fall outside the scope the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties. ).freeze,
|
525
|
-
label:
|
525
|
+
label: "Persistent Item".freeze,
|
526
526
|
subClassOf: "crm:E1_CRM_Entity".freeze,
|
527
527
|
type: "rdfs:Class".freeze
|
528
528
|
term :E78_Collection,
|
@@ -530,69 +530,69 @@ The main classes of objects that fall outside the scope the E77 Persistent Item
|
|
530
530
|
Items may be added or removed from an E78 Collection in pursuit of this plan. This class should not be confused with the E39 Actor maintaining the E78 Collection often referred to with the name of the E78 Collection \(e.g. “The Wallace Collection decided…”\).
|
531
531
|
Collective objects in the general sense, like a tomb full of gifts, a folder with stamps or a set of chessmen, should be documented as instances of E19 Physical Object, and not as instances of E78 Collection. This is because they form wholes either because they are physically bound together or because they are kept together for their functionality.
|
532
532
|
).freeze,
|
533
|
-
label:
|
533
|
+
label: "Collection".freeze,
|
534
534
|
subClassOf: "crm:E24_Physical_Man-Made_Thing".freeze,
|
535
535
|
type: "rdfs:Class".freeze
|
536
536
|
term :E79_Part_Addition,
|
537
537
|
comment: %(This class comprises activities that result in an instance of E24 Physical Man-Made Thing being increased, enlarged or augmented by the addition of a part.
|
538
538
|
Typical scenarios include the attachment of an accessory, the integration of a component, the addition of an element to an aggregate object, or the accessioning of an object into a curated E78 Collection. Objects to which parts are added are, by definition, man-made, since the addition of a part implies a human activity. Following the addition of parts, the resulting man-made assemblages are treated objectively as single identifiable wholes, made up of constituent or component parts bound together either physically \(for example the engine becoming a part of the car\), or by sharing a common purpose \(such as the 32 chess pieces that make up a chess set\). This class of activities forms a basis for reasoning about the history and continuity of identity of objects that are integrated into other objects over time, such as precious gemstones being repeatedly incorporated into different items of jewellery, or cultural artifacts being added to different museum instances of E78 Collection over their lifespan.
|
539
539
|
).freeze,
|
540
|
-
label:
|
540
|
+
label: "Part Addition".freeze,
|
541
541
|
subClassOf: "crm:E11_Modification".freeze,
|
542
542
|
type: "rdfs:Class".freeze
|
543
543
|
term :E7_Activity,
|
544
544
|
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.
|
545
545
|
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.
|
546
546
|
).freeze,
|
547
|
-
label:
|
547
|
+
label: "Activity".freeze,
|
548
548
|
subClassOf: "crm:E5_Event".freeze,
|
549
549
|
type: "rdfs:Class".freeze
|
550
550
|
term :E80_Part_Removal,
|
551
551
|
comment: %(This class comprises the activities that result in an instance of E18 Physical Thing being decreased by the removal of a part.
|
552
552
|
Typical scenarios include the detachment of an accessory, the removal of a component or part of a composite object, or the deaccessioning of an object from a curated E78 Collection. If the E80 Part Removal results in the total decomposition of the original object into pieces, such that the whole ceases to exist, the activity should instead be modelled as an E81 Transformation, i.e. a simultaneous destruction and production. In cases where the part removed has no discernible identity prior to its removal but does have an identity subsequent to its removal, the activity should be regarded as both E80 Part Removal and E12 Production. This class of activities forms a basis for reasoning about the history, and continuity of identity over time, of objects that are removed from other objects, such as precious gemstones being extracted from different items of jewelry, or cultural artifacts being deaccessioned from different museum collections over their lifespan.
|
553
553
|
).freeze,
|
554
|
-
label:
|
554
|
+
label: "Part Removal".freeze,
|
555
555
|
subClassOf: "crm:E11_Modification".freeze,
|
556
556
|
type: "rdfs:Class".freeze
|
557
557
|
term :E81_Transformation,
|
558
558
|
comment: %(This class comprises the events that result in the simultaneous destruction of one or more than one E77 Persistent Item and the creation of one or more than one E77 Persistent Item that preserves recognizable substance from the first one\(s\) but has fundamentally different nature and identity.
|
559
559
|
Although the old and the new instances of E77 Persistent Item are treated as discrete entities having separate, unique identities, they are causally connected through the E81 Transformation; the destruction of the old E77 Persistent Item\(s\) directly causes the creation of the new one\(s\) using or preserving some relevant substance. Instances of E81 Transformation are therefore distinct from re-classifications \(documented using E17 Type Assignment\) or modifications \(documented using E11 Modification\) of objects that do not fundamentally change their nature or identity. Characteristic cases are reconstructions and repurposing of historical buildings or ruins, fires leaving buildings in ruins, taxidermy of specimen in natural history and the reorganization of a corporate body into a new one.
|
560
560
|
).freeze,
|
561
|
-
label:
|
561
|
+
label: "Transformation".freeze,
|
562
562
|
subClassOf: ["crm:E63_Beginning_of_Existence".freeze, "crm:E64_End_of_Existence".freeze],
|
563
563
|
type: "rdfs:Class".freeze
|
564
564
|
term :E82_Actor_Appellation,
|
565
565
|
comment: %(This class comprises any sort of name, number, code or symbol characteristically used to identify an E39 Actor.
|
566
566
|
An E39 Actor will typically have more than one E82 Actor Appellation, and instances of E82 Actor Appellation in turn may have alternative representations. The distinction between corporate and personal names, which is particularly important in library applications, should be made by explicitly linking the E82 Actor Appellation to an instance of either E21 Person or E74 Group/E40 Legal Body. If this is not possible, the distinction can be made through the use of the P2 has type mechanism.
|
567
567
|
).freeze,
|
568
|
-
label:
|
568
|
+
label: "Actor Appellation".freeze,
|
569
569
|
subClassOf: "crm:E41_Appellation".freeze,
|
570
570
|
type: "rdfs:Class".freeze
|
571
571
|
term :E83_Type_Creation,
|
572
572
|
comment: %(This class comprises activities formally defining new types of items.
|
573
573
|
It is typically a rigorous scholarly or scientific process that ensures a type is exhaustively described and appropriately named. In some cases, particularly in archaeology and the life sciences, E83 Type Creation requires the identification of an exemplary specimen and the publication of the type definition in an appropriate scholarly forum. The activity of E83 Type Creation is central to research in the life sciences, where a type would be referred to as a “taxon,” the type description as a “protologue,” and the exemplary specimens as “orgininal element” or “holotype”.
|
574
574
|
).freeze,
|
575
|
-
label:
|
575
|
+
label: "Type Creation".freeze,
|
576
576
|
subClassOf: "crm:E65_Creation".freeze,
|
577
577
|
type: "rdfs:Class".freeze
|
578
578
|
term :E84_Information_Carrier,
|
579
579
|
comment: %(This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical carriers for instances of E73 Information Object.
|
580
580
|
An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an Information Carrier. Therefore the property P128 carries \(is carried by\) applies to E18 Physical Thing in general.
|
581
581
|
).freeze,
|
582
|
-
label:
|
582
|
+
label: "Information Carrier".freeze,
|
583
583
|
subClassOf: "crm:E22_Man-Made_Object".freeze,
|
584
584
|
type: "rdfs:Class".freeze
|
585
585
|
term :E85_Joining,
|
586
586
|
comment: %(This class comprises the activities that result in an instance of E39 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party.
|
587
587
|
Typical scenarios include becoming a member of a social organisation, becoming employee of a company, marriage, the adoption of a child by a family and the inauguration of somebody into an official position.
|
588
588
|
).freeze,
|
589
|
-
label:
|
589
|
+
label: "Joining".freeze,
|
590
590
|
subClassOf: "crm:E7_Activity".freeze,
|
591
591
|
type: "rdfs:Class".freeze
|
592
592
|
term :E86_Leaving,
|
593
593
|
comment: %(This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party.
|
594
594
|
Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position.).freeze,
|
595
|
-
label:
|
595
|
+
label: "Leaving".freeze,
|
596
596
|
subClassOf: "crm:E7_Activity".freeze,
|
597
597
|
type: "rdfs:Class".freeze
|
598
598
|
term :E87_Curation_Activity,
|
@@ -600,7 +600,7 @@ Typical scenarios include the termination of membership in a social organisation
|
|
600
600
|
It specializes the notion of activity into the curation of a collection and allows the history of curation to be recorded.
|
601
601
|
Items are accumulated and organized following criteria like subject, chronological period, material type, style of art etc. and can be added or removed from an E78 Collection for a specific purpose and/or audience. The initial aggregation of items of a collection is regarded as an instance of E12 Production Event while the activity of evolving, preserving and promoting a collection is regarded as an instance of E87 Curation Activity.
|
602
602
|
).freeze,
|
603
|
-
label:
|
603
|
+
label: "Curation Activity".freeze,
|
604
604
|
subClassOf: "crm:E7_Activity".freeze,
|
605
605
|
type: "rdfs:Class".freeze
|
606
606
|
term :E89_Propositional_Object,
|
@@ -608,7 +608,7 @@ Items are accumulated and organized following criteria like subject, chronologic
|
|
608
608
|
|
609
609
|
This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object.
|
610
610
|
).freeze,
|
611
|
-
label:
|
611
|
+
label: "Propositional Object".freeze,
|
612
612
|
subClassOf: "crm:E28_Conceptual_Object".freeze,
|
613
613
|
type: "rdfs:Class".freeze
|
614
614
|
term :E8_Acquisition,
|
@@ -621,7 +621,7 @@ The class also applies to the establishment or loss of ownership of instances of
|
|
621
621
|
5. the loss of title due to destruction of the item
|
622
622
|
It may also describe events where a collector appropriates legal title, for example by annexation or field collection. The interpretation of the museum notion of "accession" differs between institutions. The CRM therefore models legal ownership \(E8 Acquisition\) and physical custody \(E10 Transfer of Custody\) separately. Institutions will then model their specific notions of accession and deaccession as combinations of these.
|
623
623
|
).freeze,
|
624
|
-
label:
|
624
|
+
label: "Acquisition".freeze,
|
625
625
|
subClassOf: "crm:E7_Activity".freeze,
|
626
626
|
type: "rdfs:Class".freeze
|
627
627
|
term :E90_Symbolic_Object,
|
@@ -630,7 +630,7 @@ It may also describe events where a collector appropriates legal title, for exam
|
|
630
630
|
An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string.
|
631
631
|
In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized content model, such.. as the property P3 has note allows for describing this content model…P3.1 has type: E55 Type to specify the encoding..
|
632
632
|
).freeze,
|
633
|
-
label:
|
633
|
+
label: "Symbolic Object".freeze,
|
634
634
|
subClassOf: ["crm:E28_Conceptual_Object".freeze, "crm:E72_Legal_Object".freeze],
|
635
635
|
type: "rdfs:Class".freeze
|
636
636
|
term :"E91_Co-Reference_Assignment",
|
@@ -661,7 +661,7 @@ This class can be used to define temporal snapshots at a particular time-span, s
|
|
661
661
|
comment: %(This class comprises changes of the physical location of the instances of E19 Physical Object.
|
662
662
|
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.
|
663
663
|
).freeze,
|
664
|
-
label:
|
664
|
+
label: "Move".freeze,
|
665
665
|
subClassOf: "crm:E7_Activity".freeze,
|
666
666
|
type: "rdfs:Class".freeze
|
667
667
|
|
@@ -669,13 +669,13 @@ Note, that the class E9 Move inherits the property P7 took place at \(witnessed\
|
|
669
669
|
property :P100_was_death_of,
|
670
670
|
comment: %(This property property links an E69 Death event to the E21 Person that died.).freeze,
|
671
671
|
domain: "crm:E69_Death".freeze,
|
672
|
-
label:
|
672
|
+
label: "was death of".freeze,
|
673
673
|
range: "crm:E21_Person".freeze,
|
674
674
|
subPropertyOf: "crm:P93_took_out_of_existence".freeze,
|
675
675
|
type: "rdf:Property".freeze
|
676
676
|
property :P100i_died_in,
|
677
677
|
domain: "crm:E21_Person".freeze,
|
678
|
-
label:
|
678
|
+
label: "died in".freeze,
|
679
679
|
range: "crm:E69_Death".freeze,
|
680
680
|
subPropertyOf: "crm:P93i_was_taken_out_of_existence_by".freeze,
|
681
681
|
type: "rdf:Property".freeze
|
@@ -684,12 +684,12 @@ Note, that the class E9 Move inherits the property P7 took place at \(witnessed\
|
|
684
684
|
It allows the relationship between particular things, both physical and immaterial, and general methods and techniques of use to be documented. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery.
|
685
685
|
).freeze,
|
686
686
|
domain: "crm:E70_Thing".freeze,
|
687
|
-
label:
|
687
|
+
label: "had as general use".freeze,
|
688
688
|
range: "crm:E55_Type".freeze,
|
689
689
|
type: "rdf:Property".freeze
|
690
690
|
property :P101i_was_use_of,
|
691
691
|
domain: "crm:E55_Type".freeze,
|
692
|
-
label:
|
692
|
+
label: "was use of".freeze,
|
693
693
|
range: "crm:E70_Thing".freeze,
|
694
694
|
type: "rdf:Property".freeze
|
695
695
|
property :P102_has_title,
|
@@ -698,13 +698,13 @@ The P102.1 has type property of the P102 has title \(is title of\) property enab
|
|
698
698
|
It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind.
|
699
699
|
).freeze,
|
700
700
|
domain: "crm:E71_Man-Made_Thing".freeze,
|
701
|
-
label:
|
701
|
+
label: "has title".freeze,
|
702
702
|
range: "crm:E35_Title".freeze,
|
703
703
|
subPropertyOf: "crm:P1_is_identified_by".freeze,
|
704
704
|
type: "rdf:Property".freeze
|
705
705
|
property :P102i_is_title_of,
|
706
706
|
domain: "crm:E35_Title".freeze,
|
707
|
-
label:
|
707
|
+
label: "is title of".freeze,
|
708
708
|
range: "crm:E71_Man-Made_Thing".freeze,
|
709
709
|
subPropertyOf: "crm:P1i_identifies".freeze,
|
710
710
|
type: "rdf:Property".freeze
|
@@ -712,12 +712,12 @@ It allows any man-made material or immaterial thing to be given a Title. It is p
|
|
712
712
|
comment: %(This property links an instance of E71 Man-Made Thing to an E55 Type of usage.
|
713
713
|
It creates a property between specific man-made things, both physical and immaterial, to Types of intended methods and techniques of use. Note: A link between specific man-made things and a specific use activity should be expressed using P19 was intended use of \(was made for\).).freeze,
|
714
714
|
domain: "crm:E71_Man-Made_Thing".freeze,
|
715
|
-
label:
|
715
|
+
label: "was intended for".freeze,
|
716
716
|
range: "crm:E55_Type".freeze,
|
717
717
|
type: "rdf:Property".freeze
|
718
718
|
property :P103i_was_intention_of,
|
719
719
|
domain: "crm:E55_Type".freeze,
|
720
|
-
label:
|
720
|
+
label: "was intention of".freeze,
|
721
721
|
range: "crm:E71_Man-Made_Thing".freeze,
|
722
722
|
type: "rdf:Property".freeze
|
723
723
|
property :P104_is_subject_to,
|
@@ -725,12 +725,12 @@ It creates a property between specific man-made things, both physical and immate
|
|
725
725
|
The Right is held by an E39 Actor as described by P75 possesses \(is possessed by\).
|
726
726
|
).freeze,
|
727
727
|
domain: "crm:E72_Legal_Object".freeze,
|
728
|
-
label:
|
728
|
+
label: "is subject to".freeze,
|
729
729
|
range: "crm:E30_Right".freeze,
|
730
730
|
type: "rdf:Property".freeze
|
731
731
|
property :P104i_applies_to,
|
732
732
|
domain: "crm:E30_Right".freeze,
|
733
|
-
label:
|
733
|
+
label: "applies to".freeze,
|
734
734
|
range: "crm:E72_Legal_Object".freeze,
|
735
735
|
type: "rdf:Property".freeze
|
736
736
|
property :P105_right_held_by,
|
@@ -739,24 +739,24 @@ The Right is held by an E39 Actor as described by P75 possesses \(is possessed b
|
|
739
739
|
P105 right held by \(has right on\) is a shortcut of the fully developed path from E72 Legal Object through P104 is subject to \(applies to\), E30 Right, P75 possesses \(is possessed by\) to E39 Actor.
|
740
740
|
).freeze,
|
741
741
|
domain: "crm:E72_Legal_Object".freeze,
|
742
|
-
label:
|
742
|
+
label: "right held by".freeze,
|
743
743
|
range: "crm:E39_Actor".freeze,
|
744
744
|
type: "rdf:Property".freeze
|
745
745
|
property :P105i_has_right_on,
|
746
746
|
domain: "crm:E39_Actor".freeze,
|
747
|
-
label:
|
747
|
+
label: "has right on".freeze,
|
748
748
|
range: "crm:E72_Legal_Object".freeze,
|
749
749
|
type: "rdf:Property".freeze
|
750
750
|
property :P106_is_composed_of,
|
751
751
|
comment: %(This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image.
|
752
752
|
).freeze,
|
753
753
|
domain: "crm:E90_Symbolic_Object".freeze,
|
754
|
-
label:
|
754
|
+
label: "is composed of".freeze,
|
755
755
|
range: "crm:E90_Symbolic_Object".freeze,
|
756
756
|
type: "rdf:Property".freeze
|
757
757
|
property :P106i_forms_part_of,
|
758
758
|
domain: "crm:E90_Symbolic_Object".freeze,
|
759
|
-
label:
|
759
|
+
label: "forms part of".freeze,
|
760
760
|
range: "crm:E90_Symbolic_Object".freeze,
|
761
761
|
type: "rdf:Property".freeze
|
762
762
|
property :P107_has_current_or_former_member,
|
@@ -766,12 +766,12 @@ This property is a shortcut of the more fully developed path from E74 Group thro
|
|
766
766
|
The property P107.1 kind of member can be used to specify the type of membership or the role the member has in the group.
|
767
767
|
).freeze,
|
768
768
|
domain: "crm:E74_Group".freeze,
|
769
|
-
label:
|
769
|
+
label: "has current or former member".freeze,
|
770
770
|
range: "crm:E39_Actor".freeze,
|
771
771
|
type: "rdf:Property".freeze
|
772
772
|
property :P107i_is_current_or_former_member_of,
|
773
773
|
domain: "crm:E39_Actor".freeze,
|
774
|
-
label:
|
774
|
+
label: "is current or former member of".freeze,
|
775
775
|
range: "crm:E74_Group".freeze,
|
776
776
|
type: "rdf:Property".freeze
|
777
777
|
property :P108_has_produced,
|
@@ -779,13 +779,13 @@ The property P107.1 kind of member can be used to specify the type of membership
|
|
779
779
|
The identity of an instance of E24 Physical Man-Made Thing is not defined by its matter, but by its existence as a subject of documentation. An E12 Production can result in the creation of multiple instances of E24 Physical Man-Made Thing.
|
780
780
|
).freeze,
|
781
781
|
domain: "crm:E12_Production".freeze,
|
782
|
-
label:
|
782
|
+
label: "has produced".freeze,
|
783
783
|
range: "crm:E24_Physical_Man-Made_Thing".freeze,
|
784
784
|
subPropertyOf: ["crm:P31_has_modified".freeze, "crm:P92_brought_into_existence".freeze],
|
785
785
|
type: "rdf:Property".freeze
|
786
786
|
property :P108i_was_produced_by,
|
787
787
|
domain: "crm:E24_Physical_Man-Made_Thing".freeze,
|
788
|
-
label:
|
788
|
+
label: "was produced by".freeze,
|
789
789
|
range: "crm:E12_Production".freeze,
|
790
790
|
subPropertyOf: ["crm:P31i_was_modified_by".freeze, "crm:P92i_was_brought_into_existence_by".freeze],
|
791
791
|
type: "rdf:Property".freeze
|
@@ -794,13 +794,13 @@ The identity of an instance of E24 Physical Man-Made Thing is not defined by its
|
|
794
794
|
This property is effectively a short-cut. It does not allow a history of curation to be recorded. This would require use of an Event assigning responsibility for a Collection to a curator.
|
795
795
|
).freeze,
|
796
796
|
domain: "crm:E78_Collection".freeze,
|
797
|
-
label:
|
797
|
+
label: "has current or former curator".freeze,
|
798
798
|
range: "crm:E39_Actor".freeze,
|
799
799
|
subPropertyOf: "crm:P49_has_former_or_current_keeper".freeze,
|
800
800
|
type: "rdf:Property".freeze
|
801
801
|
property :P109i_is_current_or_former_curator_of,
|
802
802
|
domain: "crm:E39_Actor".freeze,
|
803
|
-
label:
|
803
|
+
label: "is current or former curator of".freeze,
|
804
804
|
range: "crm:E78_Collection".freeze,
|
805
805
|
subPropertyOf: "crm:P49i_is_former_or_current_keeper_of".freeze,
|
806
806
|
type: "rdf:Property".freeze
|
@@ -809,12 +809,12 @@ This property is effectively a short-cut. It does not allow a history of curatio
|
|
809
809
|
The difference with P9 consists of \(forms part of\) is subtle. Unlike P9 consists of \(forms part of\), P10 falls within \(contains\) does not imply any logical connection between the two periods and it may refer to a period of a completely different type.
|
810
810
|
).freeze,
|
811
811
|
domain: "crm:E4_Period".freeze,
|
812
|
-
label:
|
812
|
+
label: "falls within".freeze,
|
813
813
|
range: "crm:E4_Period".freeze,
|
814
814
|
type: "rdf:Property".freeze
|
815
815
|
property :P10i_contains,
|
816
816
|
domain: "crm:E4_Period".freeze,
|
817
|
-
label:
|
817
|
+
label: "contains".freeze,
|
818
818
|
range: "crm:E4_Period".freeze,
|
819
819
|
type: "rdf:Property".freeze
|
820
820
|
property :P110_augmented,
|
@@ -822,13 +822,13 @@ The difference with P9 consists of \(forms part of\) is subtle. Unlike P9 consis
|
|
822
822
|
Although a Part Addition event normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be added to \(augmented\). For example, the artist Jackson Pollock trailing paint onto multiple canvasses.
|
823
823
|
).freeze,
|
824
824
|
domain: "crm:E79_Part_Addition".freeze,
|
825
|
-
label:
|
825
|
+
label: "augmented".freeze,
|
826
826
|
range: "crm:E24_Physical_Man-Made_Thing".freeze,
|
827
827
|
subPropertyOf: "crm:P31_has_modified".freeze,
|
828
828
|
type: "rdf:Property".freeze
|
829
829
|
property :P110i_was_augmented_by,
|
830
830
|
domain: "crm:E24_Physical_Man-Made_Thing".freeze,
|
831
|
-
label:
|
831
|
+
label: "was augmented by".freeze,
|
832
832
|
range: "crm:E79_Part_Addition".freeze,
|
833
833
|
subPropertyOf: "crm:P31i_was_modified_by".freeze,
|
834
834
|
type: "rdf:Property".freeze
|
@@ -836,13 +836,13 @@ Although a Part Addition event normally concerns only one item of Physical Man-M
|
|
836
836
|
comment: %(This property identifies the E18 Physical Thing that is added during an E79 Part Addition activity
|
837
837
|
).freeze,
|
838
838
|
domain: "crm:E79_Part_Addition".freeze,
|
839
|
-
label:
|
839
|
+
label: "added".freeze,
|
840
840
|
range: "crm:E18_Physical_Thing".freeze,
|
841
841
|
subPropertyOf: ["crm:P12_occurred_in_the_presence_of".freeze, "crm:P16_used_specific_object".freeze],
|
842
842
|
type: "rdf:Property".freeze
|
843
843
|
property :P111i_was_added_by,
|
844
844
|
domain: "crm:E18_Physical_Thing".freeze,
|
845
|
-
label:
|
845
|
+
label: "was added by".freeze,
|
846
846
|
range: "crm:E79_Part_Addition".freeze,
|
847
847
|
subPropertyOf: ["crm:P12i_was_present_at".freeze, "crm:P16i_was_used_for".freeze],
|
848
848
|
type: "rdf:Property".freeze
|
@@ -851,26 +851,26 @@ Although a Part Addition event normally concerns only one item of Physical Man-M
|
|
851
851
|
Although a Part removal activity normally concerns only one item of Physical Man-Made Thing, it is possible to imagine circumstances under which more than one item might be diminished by a single Part Removal activity.
|
852
852
|
).freeze,
|
853
853
|
domain: "crm:E80_Part_Removal".freeze,
|
854
|
-
label:
|
854
|
+
label: "diminished".freeze,
|
855
855
|
range: "crm:E24_Physical_Man-Made_Thing".freeze,
|
856
856
|
subPropertyOf: "crm:P31_has_modified".freeze,
|
857
857
|
type: "rdf:Property".freeze
|
858
858
|
property :P112i_was_diminished_by,
|
859
859
|
domain: "crm:E24_Physical_Man-Made_Thing".freeze,
|
860
|
-
label:
|
860
|
+
label: "was diminished by".freeze,
|
861
861
|
range: "crm:E80_Part_Removal".freeze,
|
862
862
|
subPropertyOf: "crm:P31i_was_modified_by".freeze,
|
863
863
|
type: "rdf:Property".freeze
|
864
864
|
property :P113_removed,
|
865
865
|
comment: %(This property identifies the E18 Physical Thing that is removed during an E80 Part Removal activity.).freeze,
|
866
866
|
domain: "crm:E80_Part_Removal".freeze,
|
867
|
-
label:
|
867
|
+
label: "removed".freeze,
|
868
868
|
range: "crm:E18_Physical_Thing".freeze,
|
869
869
|
subPropertyOf: "crm:P12_occurred_in_the_presence_of".freeze,
|
870
870
|
type: "rdf:Property".freeze
|
871
871
|
property :P113i_was_removed_by,
|
872
872
|
domain: "crm:E18_Physical_Thing".freeze,
|
873
|
-
label:
|
873
|
+
label: "was removed by".freeze,
|
874
874
|
range: "crm:E80_Part_Removal".freeze,
|
875
875
|
subPropertyOf: "crm:P12i_was_present_at".freeze,
|
876
876
|
type: "rdf:Property".freeze
|
@@ -880,7 +880,7 @@ This property is only necessary if the time span is unknown \(otherwise the equi
|
|
880
880
|
This property is the same as the "equal" relationship of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
881
881
|
).freeze,
|
882
882
|
domain: "crm:E2_Temporal_Entity".freeze,
|
883
|
-
label:
|
883
|
+
label: "is equal in time to".freeze,
|
884
884
|
range: "crm:E2_Temporal_Entity".freeze,
|
885
885
|
type: "rdf:Property".freeze
|
886
886
|
property :P115_finishes,
|
@@ -888,12 +888,12 @@ This property is the same as the "equal" relationship of Allen’s temporal logi
|
|
888
888
|
This property is only necessary if the time span is unknown \(otherwise the relationship can be calculated\). This property is the same as the "finishes / finished-by" relationships of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
889
889
|
).freeze,
|
890
890
|
domain: "crm:E2_Temporal_Entity".freeze,
|
891
|
-
label:
|
891
|
+
label: "finishes".freeze,
|
892
892
|
range: "crm:E2_Temporal_Entity".freeze,
|
893
893
|
type: "rdf:Property".freeze
|
894
894
|
property :P115i_is_finished_by,
|
895
895
|
domain: "crm:E2_Temporal_Entity".freeze,
|
896
|
-
label:
|
896
|
+
label: "is finished by".freeze,
|
897
897
|
range: "crm:E2_Temporal_Entity".freeze,
|
898
898
|
type: "rdf:Property".freeze
|
899
899
|
property :P116_starts,
|
@@ -901,12 +901,12 @@ This property is only necessary if the time span is unknown \(otherwise the rela
|
|
901
901
|
This property is only necessary if the time span is unknown \(otherwise the relationship can be calculated\). This property is the same as the "starts / started-by" relationships of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
902
902
|
).freeze,
|
903
903
|
domain: "crm:E2_Temporal_Entity".freeze,
|
904
|
-
label:
|
904
|
+
label: "starts".freeze,
|
905
905
|
range: "crm:E2_Temporal_Entity".freeze,
|
906
906
|
type: "rdf:Property".freeze
|
907
907
|
property :P116i_is_started_by,
|
908
908
|
domain: "crm:E2_Temporal_Entity".freeze,
|
909
|
-
label:
|
909
|
+
label: "is started by".freeze,
|
910
910
|
range: "crm:E2_Temporal_Entity".freeze,
|
911
911
|
type: "rdf:Property".freeze
|
912
912
|
property :P117_occurs_during,
|
@@ -914,12 +914,12 @@ This property is only necessary if the time span is unknown \(otherwise the rela
|
|
914
914
|
This property is only necessary if the time span is unknown \(otherwise the relationship can be calculated\). This property is the same as the "during / includes" relationships of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
915
915
|
).freeze,
|
916
916
|
domain: "crm:E2_Temporal_Entity".freeze,
|
917
|
-
label:
|
917
|
+
label: "occurs during".freeze,
|
918
918
|
range: "crm:E2_Temporal_Entity".freeze,
|
919
919
|
type: "rdf:Property".freeze
|
920
920
|
property :P117i_includes,
|
921
921
|
domain: "crm:E2_Temporal_Entity".freeze,
|
922
|
-
label:
|
922
|
+
label: "includes".freeze,
|
923
923
|
range: "crm:E2_Temporal_Entity".freeze,
|
924
924
|
type: "rdf:Property".freeze
|
925
925
|
property :P118_overlaps_in_time_with,
|
@@ -928,12 +928,12 @@ It implies a temporal order between the two entities: if A overlaps in time B, t
|
|
928
928
|
This property is the same as the "overlaps / overlapped-by" relationships of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
929
929
|
).freeze,
|
930
930
|
domain: "crm:E2_Temporal_Entity".freeze,
|
931
|
-
label:
|
931
|
+
label: "overlaps in time with".freeze,
|
932
932
|
range: "crm:E2_Temporal_Entity".freeze,
|
933
933
|
type: "rdf:Property".freeze
|
934
934
|
property :P118i_is_overlapped_in_time_by,
|
935
935
|
domain: "crm:E2_Temporal_Entity".freeze,
|
936
|
-
label:
|
936
|
+
label: "is overlapped in time by".freeze,
|
937
937
|
range: "crm:E2_Temporal_Entity".freeze,
|
938
938
|
type: "rdf:Property".freeze
|
939
939
|
property :P119_meets_in_time_with,
|
@@ -942,12 +942,12 @@ It implies a particular order between the two entities: if A meets in time with
|
|
942
942
|
This property is the same as the "meets / met-by" relationships of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
943
943
|
).freeze,
|
944
944
|
domain: "crm:E2_Temporal_Entity".freeze,
|
945
|
-
label:
|
945
|
+
label: "meets in time with".freeze,
|
946
946
|
range: "crm:E2_Temporal_Entity".freeze,
|
947
947
|
type: "rdf:Property".freeze
|
948
948
|
property :P119i_is_met_in_time_by,
|
949
949
|
domain: "crm:E2_Temporal_Entity".freeze,
|
950
|
-
label:
|
950
|
+
label: "is met in time by".freeze,
|
951
951
|
range: "crm:E2_Temporal_Entity".freeze,
|
952
952
|
type: "rdf:Property".freeze
|
953
953
|
property :P11_had_participant,
|
@@ -955,13 +955,13 @@ This property is the same as the "meets / met-by" relationships of Allen’s tem
|
|
955
955
|
It connects the life-line of the related E39 Actor with the E53 Place and E50 Date of the event. The property implies that the Actor was involved in the event but does not imply any causal relationship. The subject of a portrait can be said to have participated in the creation of the portrait.
|
956
956
|
).freeze,
|
957
957
|
domain: "crm:E5_Event".freeze,
|
958
|
-
label:
|
958
|
+
label: "had participant".freeze,
|
959
959
|
range: "crm:E39_Actor".freeze,
|
960
960
|
subPropertyOf: "crm:P12_occurred_in_the_presence_of".freeze,
|
961
961
|
type: "rdf:Property".freeze
|
962
962
|
property :P11i_participated_in,
|
963
963
|
domain: "crm:E39_Actor".freeze,
|
964
|
-
label:
|
964
|
+
label: "participated in".freeze,
|
965
965
|
range: "crm:E5_Event".freeze,
|
966
966
|
subPropertyOf: "crm:P12i_was_present_at".freeze,
|
967
967
|
type: "rdf:Property".freeze
|
@@ -971,12 +971,12 @@ It implies that a temporal gap exists between the end of A and the start of B. T
|
|
971
971
|
This property is the same as the "before / after" relationships of Allen’s temporal logic \(Allen, 1983, pp. 832-843\).
|
972
972
|
).freeze,
|
973
973
|
domain: "crm:E2_Temporal_Entity".freeze,
|
974
|
-
label:
|
974
|
+
label: "occurs before".freeze,
|
975
975
|
range: "crm:E2_Temporal_Entity".freeze,
|
976
976
|
type: "rdf:Property".freeze
|
977
977
|
property :P120i_occurs_after,
|
978
978
|
domain: "crm:E2_Temporal_Entity".freeze,
|
979
|
-
label:
|
979
|
+
label: "occurs after".freeze,
|
980
980
|
range: "crm:E2_Temporal_Entity".freeze,
|
981
981
|
type: "rdf:Property".freeze
|
982
982
|
property :P121_overlaps_with,
|
@@ -984,7 +984,7 @@ This property is the same as the "before / after" relationships of Allen’s tem
|
|
984
984
|
It does not specify anything about the shared area. This property is purely spatial, in contrast to Allen operators, which are purely temporal.
|
985
985
|
).freeze,
|
986
986
|
domain: "crm:E53_Place".freeze,
|
987
|
-
label:
|
987
|
+
label: "overlaps with".freeze,
|
988
988
|
range: "crm:E53_Place".freeze,
|
989
989
|
type: "rdf:Property".freeze
|
990
990
|
property :P122_borders_with,
|
@@ -992,7 +992,7 @@ It does not specify anything about the shared area. This property is purely spat
|
|
992
992
|
This property is purely spatial, in contrast to Allen operators, which are purely temporal.
|
993
993
|
).freeze,
|
994
994
|
domain: "crm:E53_Place".freeze,
|
995
|
-
label:
|
995
|
+
label: "borders with".freeze,
|
996
996
|
range: "crm:E53_Place".freeze,
|
997
997
|
type: "rdf:Property".freeze
|
998
998
|
property :P123_resulted_in,
|
@@ -1000,13 +1000,13 @@ This property is purely spatial, in contrast to Allen operators, which are purel
|
|
1000
1000
|
New items replace the transformed item or items, which cease to exist as units of documentation. The physical continuity between the old and the new is expressed by the link to the common Transformation.
|
1001
1001
|
).freeze,
|
1002
1002
|
domain: "crm:E81_Transformation".freeze,
|
1003
|
-
label:
|
1003
|
+
label: "resulted in".freeze,
|
1004
1004
|
range: "crm:E77_Persistent_Item".freeze,
|
1005
1005
|
subPropertyOf: "crm:P92_brought_into_existence".freeze,
|
1006
1006
|
type: "rdf:Property".freeze
|
1007
1007
|
property :P123i_resulted_from,
|
1008
1008
|
domain: "crm:E77_Persistent_Item".freeze,
|
1009
|
-
label:
|
1009
|
+
label: "resulted from".freeze,
|
1010
1010
|
range: "crm:E81_Transformation".freeze,
|
1011
1011
|
subPropertyOf: "crm:P92i_was_brought_into_existence_by".freeze,
|
1012
1012
|
type: "rdf:Property".freeze
|
@@ -1015,13 +1015,13 @@ New items replace the transformed item or items, which cease to exist as units o
|
|
1015
1015
|
It is replaced by the result of the Transformation, which becomes a new unit of documentation. The continuity between both items, the new and the old, is expressed by the link to the common Transformation.
|
1016
1016
|
).freeze,
|
1017
1017
|
domain: "crm:E81_Transformation".freeze,
|
1018
|
-
label:
|
1018
|
+
label: "transformed".freeze,
|
1019
1019
|
range: "crm:E77_Persistent_Item".freeze,
|
1020
1020
|
subPropertyOf: "crm:P93_took_out_of_existence".freeze,
|
1021
1021
|
type: "rdf:Property".freeze
|
1022
1022
|
property :P124i_was_transformed_by,
|
1023
1023
|
domain: "crm:E77_Persistent_Item".freeze,
|
1024
|
-
label:
|
1024
|
+
label: "was transformed by".freeze,
|
1025
1025
|
range: "crm:E81_Transformation".freeze,
|
1026
1026
|
subPropertyOf: "crm:P93i_was_taken_out_of_existence_by".freeze,
|
1027
1027
|
type: "rdf:Property".freeze
|
@@ -1029,12 +1029,12 @@ It is replaced by the result of the Transformation, which becomes a new unit of
|
|
1029
1029
|
comment: %(This property defines the kind of objects used in an E7 Activity, when the specific instance is either unknown or not of interest, such as use of "a hammer".
|
1030
1030
|
).freeze,
|
1031
1031
|
domain: "crm:E7_Activity".freeze,
|
1032
|
-
label:
|
1032
|
+
label: "used object of type".freeze,
|
1033
1033
|
range: "crm:E55_Type".freeze,
|
1034
1034
|
type: "rdf:Property".freeze
|
1035
1035
|
property :P125i_was_type_of_object_used_in,
|
1036
1036
|
domain: "crm:E55_Type".freeze,
|
1037
|
-
label:
|
1037
|
+
label: "was type of object used in".freeze,
|
1038
1038
|
range: "crm:E7_Activity".freeze,
|
1039
1039
|
type: "rdf:Property".freeze
|
1040
1040
|
property :P126_employed,
|
@@ -1042,12 +1042,12 @@ It is replaced by the result of the Transformation, which becomes a new unit of
|
|
1042
1042
|
The E57 Material used during the E11 Modification does not necessarily become incorporated into the E24 Physical Man-Made Thing that forms the subject of the E11 Modification.
|
1043
1043
|
).freeze,
|
1044
1044
|
domain: "crm:E11_Modification".freeze,
|
1045
|
-
label:
|
1045
|
+
label: "employed".freeze,
|
1046
1046
|
range: "crm:E57_Material".freeze,
|
1047
1047
|
type: "rdf:Property".freeze
|
1048
1048
|
property :P126i_was_employed_in,
|
1049
1049
|
domain: "crm:E57_Material".freeze,
|
1050
|
-
label:
|
1050
|
+
label: "was employed in".freeze,
|
1051
1051
|
range: "crm:E11_Modification".freeze,
|
1052
1052
|
type: "rdf:Property".freeze
|
1053
1053
|
property :P127_has_broader_term,
|
@@ -1055,25 +1055,25 @@ The E57 Material used during the E11 Modification does not necessarily become in
|
|
1055
1055
|
It allows Types to be organised into hierarchies. This is the sense of "broader term generic \(BTG\)" as defined in ISO 2788
|
1056
1056
|
).freeze,
|
1057
1057
|
domain: "crm:E55_Type".freeze,
|
1058
|
-
label:
|
1058
|
+
label: "has broader term".freeze,
|
1059
1059
|
range: "crm:E55_Type".freeze,
|
1060
1060
|
type: "rdf:Property".freeze
|
1061
1061
|
property :P127i_has_narrower_term,
|
1062
1062
|
domain: "crm:E55_Type".freeze,
|
1063
|
-
label:
|
1063
|
+
label: "has narrower term".freeze,
|
1064
1064
|
range: "crm:E55_Type".freeze,
|
1065
1065
|
type: "rdf:Property".freeze
|
1066
1066
|
property :P128_carries,
|
1067
1067
|
comment: %(This property identifies an E90 Symbolic Object carried by an instance of E18 Physical Thing.
|
1068
1068
|
).freeze,
|
1069
1069
|
domain: "crm:E18_Physical_Thing".freeze,
|
1070
|
-
label:
|
1070
|
+
label: "carries".freeze,
|
1071
1071
|
range: "crm:E90_Symbolic_Object".freeze,
|
1072
1072
|
subPropertyOf: "crm:P130_shows_features_of".freeze,
|
1073
1073
|
type: "rdf:Property".freeze
|
1074
1074
|
property :P128i_is_carried_by,
|
1075
1075
|
domain: "crm:E90_Symbolic_Object".freeze,
|
1076
|
-
label:
|
1076
|
+
label: "is carried by".freeze,
|
1077
1077
|
range: "crm:E18_Physical_Thing".freeze,
|
1078
1078
|
subPropertyOf: "crm:P130i_features_are_also_found_on".freeze,
|
1079
1079
|
type: "rdf:Property".freeze
|
@@ -1081,13 +1081,13 @@ The E57 Material used during the E11 Modification does not necessarily become in
|
|
1081
1081
|
comment: %(This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity.
|
1082
1082
|
).freeze,
|
1083
1083
|
domain: "crm:E89_Propositional_Object".freeze,
|
1084
|
-
label:
|
1084
|
+
label: "is about".freeze,
|
1085
1085
|
range: "crm:E1_CRM_Entity".freeze,
|
1086
1086
|
subPropertyOf: "crm:P67_refers_to".freeze,
|
1087
1087
|
type: "rdf:Property".freeze
|
1088
1088
|
property :P129i_is_subject_of,
|
1089
1089
|
domain: "crm:E1_CRM_Entity".freeze,
|
1090
|
-
label:
|
1090
|
+
label: "is subject of".freeze,
|
1091
1091
|
range: "crm:E89_Propositional_Object".freeze,
|
1092
1092
|
subPropertyOf: "crm:P67i_is_referred_to_by".freeze,
|
1093
1093
|
type: "rdf:Property".freeze
|
@@ -1096,12 +1096,12 @@ The E57 Material used during the E11 Modification does not necessarily become in
|
|
1096
1096
|
It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers.
|
1097
1097
|
).freeze,
|
1098
1098
|
domain: "crm:E5_Event".freeze,
|
1099
|
-
label:
|
1099
|
+
label: "occurred in the presence of".freeze,
|
1100
1100
|
range: "crm:E77_Persistent_Item".freeze,
|
1101
1101
|
type: "rdf:Property".freeze
|
1102
1102
|
property :P12i_was_present_at,
|
1103
1103
|
domain: "crm:E77_Persistent_Item".freeze,
|
1104
|
-
label:
|
1104
|
+
label: "was present at".freeze,
|
1105
1105
|
range: "crm:E5_Event".freeze,
|
1106
1106
|
type: "rdf:Property".freeze
|
1107
1107
|
property :P130_shows_features_of,
|
@@ -1109,13 +1109,13 @@ It connects the history of a thing with the E53 Place and E50 Date of an event.
|
|
1109
1109
|
Otherwise, the relationship is symmetric. It is a short-cut of P15 was influenced by \(influenced\) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons.
|
1110
1110
|
).freeze,
|
1111
1111
|
domain: "crm:E70_Thing".freeze,
|
1112
|
-
label:
|
1112
|
+
label: "shows features of".freeze,
|
1113
1113
|
range: "crm:E70_Thing".freeze,
|
1114
1114
|
subPropertyOf: "crm:P73i_is_translation_of".freeze,
|
1115
1115
|
type: "rdf:Property".freeze
|
1116
1116
|
property :P130i_features_are_also_found_on,
|
1117
1117
|
domain: "crm:E70_Thing".freeze,
|
1118
|
-
label:
|
1118
|
+
label: "features are also found on".freeze,
|
1119
1119
|
range: "crm:E70_Thing".freeze,
|
1120
1120
|
type: "rdf:Property".freeze
|
1121
1121
|
property :P131_is_identified_by,
|
@@ -1123,13 +1123,13 @@ Otherwise, the relationship is symmetric. It is a short-cut of P15 was influence
|
|
1123
1123
|
This property is a specialisation of P1 is identified by \(identifies\) is identified by.
|
1124
1124
|
).freeze,
|
1125
1125
|
domain: "crm:E39_Actor".freeze,
|
1126
|
-
label:
|
1126
|
+
label: "is identified by".freeze,
|
1127
1127
|
range: "crm:E82_Actor_Appellation".freeze,
|
1128
1128
|
subPropertyOf: "crm:P1_is_identified_by".freeze,
|
1129
1129
|
type: "rdf:Property".freeze
|
1130
1130
|
property :P131i_identifies,
|
1131
1131
|
domain: "crm:E82_Actor_Appellation".freeze,
|
1132
|
-
label:
|
1132
|
+
label: "identifies".freeze,
|
1133
1133
|
range: "crm:E39_Actor".freeze,
|
1134
1134
|
subPropertyOf: "crm:P1i_identifies".freeze,
|
1135
1135
|
type: "rdf:Property".freeze
|
@@ -1138,7 +1138,7 @@ This property is a specialisation of P1 is identified by \(identifies\) is ident
|
|
1138
1138
|
This property does not imply any ordering or sequence between the two periods, either spatial or temporal.
|
1139
1139
|
).freeze,
|
1140
1140
|
domain: "crm:E4_Period".freeze,
|
1141
|
-
label:
|
1141
|
+
label: "overlaps with".freeze,
|
1142
1142
|
range: "crm:E4_Period".freeze,
|
1143
1143
|
type: "rdf:Property".freeze
|
1144
1144
|
property :P133_is_separated_from,
|
@@ -1146,33 +1146,33 @@ This property does not imply any ordering or sequence between the two periods, e
|
|
1146
1146
|
This property does not imply any ordering or sequence between the two periods either spatial or temporal.
|
1147
1147
|
).freeze,
|
1148
1148
|
domain: "crm:E4_Period".freeze,
|
1149
|
-
label:
|
1149
|
+
label: "is separated from".freeze,
|
1150
1150
|
range: "crm:E4_Period".freeze,
|
1151
1151
|
type: "rdf:Property".freeze
|
1152
1152
|
property :P134_continued,
|
1153
1153
|
comment: %(This property associates two instances of E7 Activity, where the domain is considered as an intentional continuation of the range. A continuation of an activity may happen when the continued activity is still ongoing or after the continued activity has completely ended. The continuing activity may have started already before it decided to continue the other one. Continuation implies a coherence of intentions and outcomes of the involved activities.
|
1154
1154
|
).freeze,
|
1155
1155
|
domain: "crm:E7_Activity".freeze,
|
1156
|
-
label:
|
1156
|
+
label: "continued".freeze,
|
1157
1157
|
range: "crm:E7_Activity".freeze,
|
1158
1158
|
subPropertyOf: "crm:P15_was_influenced_by".freeze,
|
1159
1159
|
type: "rdf:Property".freeze
|
1160
1160
|
property :P134i_was_continued_by,
|
1161
1161
|
domain: "crm:E7_Activity".freeze,
|
1162
|
-
label:
|
1162
|
+
label: "was continued by".freeze,
|
1163
1163
|
range: "crm:E7_Activity".freeze,
|
1164
1164
|
subPropertyOf: "crm:P15i_influenced".freeze,
|
1165
1165
|
type: "rdf:Property".freeze
|
1166
1166
|
property :P135_created_type,
|
1167
1167
|
comment: %(This property identifies the E55 Type, which is created in an E83Type Creation activity.).freeze,
|
1168
1168
|
domain: "crm:E83_Type_Creation".freeze,
|
1169
|
-
label:
|
1169
|
+
label: "created type".freeze,
|
1170
1170
|
range: "crm:E55_Type".freeze,
|
1171
1171
|
subPropertyOf: "crm:P94_has_created".freeze,
|
1172
1172
|
type: "rdf:Property".freeze
|
1173
1173
|
property :P135i_was_created_by,
|
1174
1174
|
domain: "crm:E55_Type".freeze,
|
1175
|
-
label:
|
1175
|
+
label: "was created by".freeze,
|
1176
1176
|
range: "crm:E83_Type_Creation".freeze,
|
1177
1177
|
subPropertyOf: "crm:P94i_was_created_by".freeze,
|
1178
1178
|
type: "rdf:Property".freeze
|
@@ -1181,13 +1181,13 @@ This property does not imply any ordering or sequence between the two periods ei
|
|
1181
1181
|
The examination of these items is often the only objective way to understand the precise characteristics of a new Type. Such items should be deposited in a museum or similar institution for that reason. The taxonomic role renders the specific relationship of each item to the Type, such as "holotype" or "original element".
|
1182
1182
|
).freeze,
|
1183
1183
|
domain: "crm:E83_Type_Creation".freeze,
|
1184
|
-
label:
|
1184
|
+
label: "was based on".freeze,
|
1185
1185
|
range: "crm:E1_CRM_Entity".freeze,
|
1186
1186
|
subPropertyOf: "crm:P15_was_influenced_by".freeze,
|
1187
1187
|
type: "rdf:Property".freeze
|
1188
1188
|
property :P136i_supported_type_creation,
|
1189
1189
|
domain: "crm:E1_CRM_Entity".freeze,
|
1190
|
-
label:
|
1190
|
+
label: "supported type creation".freeze,
|
1191
1191
|
range: "crm:E83_Type_Creation".freeze,
|
1192
1192
|
subPropertyOf: "crm:P15i_influenced".freeze,
|
1193
1193
|
type: "rdf:Property".freeze
|
@@ -1196,13 +1196,13 @@ The examination of these items is often the only objective way to understand the
|
|
1196
1196
|
The P137.1 in the taxonomic role property of P137 exemplifies \(is exemplified by\) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the Type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the Type Creation \(E83\) itself, but selected in a later phase.
|
1197
1197
|
).freeze,
|
1198
1198
|
domain: "crm:E1_CRM_Entity".freeze,
|
1199
|
-
label:
|
1199
|
+
label: "exemplifies".freeze,
|
1200
1200
|
range: "crm:E55_Type".freeze,
|
1201
1201
|
subPropertyOf: "crm:P2_has_type".freeze,
|
1202
1202
|
type: "rdf:Property".freeze
|
1203
1203
|
property :P137i_is_exemplified_by,
|
1204
1204
|
domain: "crm:E55_Type".freeze,
|
1205
|
-
label:
|
1205
|
+
label: "is exemplified by".freeze,
|
1206
1206
|
range: "crm:E1_CRM_Entity".freeze,
|
1207
1207
|
subPropertyOf: "crm:P2i_is_type_of".freeze,
|
1208
1208
|
type: "rdf:Property".freeze
|
@@ -1212,13 +1212,13 @@ Any entity may be represented visually. This property is part of the fully devel
|
|
1212
1212
|
This property is also used for the relationship between an original and a digitisation of the original by the use of techniques such as digital photography, flatbed or infrared scanning. Digitisation is here seen as a process with a mechanical, causal component rendering the spatial distribution of structural and optical properties of the original and does not necessarily include any visual similarity identifiable by human observation.
|
1213
1213
|
).freeze,
|
1214
1214
|
domain: "crm:E36_Visual_Item".freeze,
|
1215
|
-
label:
|
1215
|
+
label: "represents".freeze,
|
1216
1216
|
range: "crm:E1_CRM_Entity".freeze,
|
1217
1217
|
subPropertyOf: "crm:P67_refers_to".freeze,
|
1218
1218
|
type: "rdf:Property".freeze
|
1219
1219
|
property :P138i_has_representation,
|
1220
1220
|
domain: "crm:E1_CRM_Entity".freeze,
|
1221
|
-
label:
|
1221
|
+
label: "has representation".freeze,
|
1222
1222
|
range: "crm:E36_Visual_Item".freeze,
|
1223
1223
|
subPropertyOf: "crm:P67i_is_referred_to_by".freeze,
|
1224
1224
|
type: "rdf:Property".freeze
|
@@ -1228,7 +1228,7 @@ The equivalence applies to all cases of use of an instance of E41 Appellation. M
|
|
1228
1228
|
P139.1 has type allows the type of derivation, such as “transliteration from Latin 1 to ASCII” be refined..
|
1229
1229
|
).freeze,
|
1230
1230
|
domain: "crm:E41_Appellation".freeze,
|
1231
|
-
label:
|
1231
|
+
label: "has alternative form".freeze,
|
1232
1232
|
range: "crm:E41_Appellation".freeze,
|
1233
1233
|
type: "rdf:Property".freeze
|
1234
1234
|
property :P13_destroyed,
|
@@ -1236,50 +1236,50 @@ P139.1 has type allows the type of derivation, such as “transliteration from L
|
|
1236
1236
|
Destruction implies the end of an item’s life as a subject of cultural documentation – the physical matter of which the item was composed may in fact continue to exist. A destruction event may be contiguous with a Production that brings into existence a derived object composed partly of matter from the destroyed object.
|
1237
1237
|
).freeze,
|
1238
1238
|
domain: "crm:E6_Destruction".freeze,
|
1239
|
-
label:
|
1239
|
+
label: "destroyed".freeze,
|
1240
1240
|
range: "crm:E18_Physical_Thing".freeze,
|
1241
1241
|
subPropertyOf: "crm:P93_took_out_of_existence".freeze,
|
1242
1242
|
type: "rdf:Property".freeze
|
1243
1243
|
property :P13i_was_destroyed_by,
|
1244
1244
|
domain: "crm:E18_Physical_Thing".freeze,
|
1245
|
-
label:
|
1245
|
+
label: "was destroyed by".freeze,
|
1246
1246
|
range: "crm:E6_Destruction".freeze,
|
1247
1247
|
subPropertyOf: "crm:P93i_was_taken_out_of_existence_by".freeze,
|
1248
1248
|
type: "rdf:Property".freeze
|
1249
1249
|
property :P140_assigned_attribute_to,
|
1250
1250
|
comment: %(This property indicates the item to which an attribute or relation is assigned. ).freeze,
|
1251
1251
|
domain: "crm:E13_Attribute_Assignment".freeze,
|
1252
|
-
label:
|
1252
|
+
label: "assigned attribute to".freeze,
|
1253
1253
|
range: "crm:E1_CRM_Entity".freeze,
|
1254
1254
|
type: "rdf:Property".freeze
|
1255
1255
|
property :P140i_was_attributed_by,
|
1256
1256
|
domain: "crm:E1_CRM_Entity".freeze,
|
1257
|
-
label:
|
1257
|
+
label: "was attributed by".freeze,
|
1258
1258
|
range: "crm:E13_Attribute_Assignment".freeze,
|
1259
1259
|
type: "rdf:Property".freeze
|
1260
1260
|
property :P141_assigned,
|
1261
1261
|
comment: %(This property indicates the attribute that was assigned or the item that was related to the item denoted by a property P140 assigned attribute to in an Attribute assignment action.
|
1262
1262
|
).freeze,
|
1263
1263
|
domain: "crm:E13_Attribute_Assignment".freeze,
|
1264
|
-
label:
|
1264
|
+
label: "assigned".freeze,
|
1265
1265
|
range: "crm:E1_CRM_Entity".freeze,
|
1266
1266
|
type: "rdf:Property".freeze
|
1267
1267
|
property :P141i_was_assigned_by,
|
1268
1268
|
domain: "crm:E1_CRM_Entity".freeze,
|
1269
|
-
label:
|
1269
|
+
label: "was assigned by".freeze,
|
1270
1270
|
range: "crm:E13_Attribute_Assignment".freeze,
|
1271
1271
|
type: "rdf:Property".freeze
|
1272
1272
|
property :P142_used_constituent,
|
1273
1273
|
comment: %(This property associates the event of assigning an instance of E42 Identifier to an entity, with the instances of E41 Appellation that were used as elements of the identifier.
|
1274
1274
|
).freeze,
|
1275
1275
|
domain: "crm:E15_Identifier_Assignment".freeze,
|
1276
|
-
label:
|
1276
|
+
label: "used constituent".freeze,
|
1277
1277
|
range: "crm:E90_Symbolic_Object".freeze,
|
1278
1278
|
subPropertyOf: "crm:P16_used_specific_object".freeze,
|
1279
1279
|
type: "rdf:Property".freeze
|
1280
1280
|
property :P142i_was_used_in,
|
1281
1281
|
domain: "crm:E90_Symbolic_Object".freeze,
|
1282
|
-
label:
|
1282
|
+
label: "was used in".freeze,
|
1283
1283
|
range: "crm:E15_Identifier_Assignment".freeze,
|
1284
1284
|
subPropertyOf: "crm:P16i_was_used_for".freeze,
|
1285
1285
|
type: "rdf:Property".freeze
|
@@ -1288,13 +1288,13 @@ Destruction implies the end of an item’s life as a subject of cultural documen
|
|
1288
1288
|
Joining events allow for describing people becoming members of a group with a more detailed path from E74 Group through P144 joined with \(gained member by\), E85 Joining, P143 joined \(was joined by\) to E39 Actor, compared to the shortcut offered by P107 has current or former member \(is current or former member of\).
|
1289
1289
|
).freeze,
|
1290
1290
|
domain: "crm:E85_Joining".freeze,
|
1291
|
-
label:
|
1291
|
+
label: "joined".freeze,
|
1292
1292
|
range: "crm:E39_Actor".freeze,
|
1293
1293
|
subPropertyOf: "crm:P11_had_participant".freeze,
|
1294
1294
|
type: "rdf:Property".freeze
|
1295
1295
|
property :P143i_was_joined_by,
|
1296
1296
|
domain: "crm:E39_Actor".freeze,
|
1297
|
-
label:
|
1297
|
+
label: "was joined by".freeze,
|
1298
1298
|
range: "crm:E85_Joining".freeze,
|
1299
1299
|
subPropertyOf: "crm:P11i_participated_in".freeze,
|
1300
1300
|
type: "rdf:Property".freeze
|
@@ -1305,26 +1305,26 @@ Joining events allow for describing people becoming members of a group with a mo
|
|
1305
1305
|
The property P144.1 kind of member can be used to specify the type of membership or the role the member has in the group.
|
1306
1306
|
).freeze,
|
1307
1307
|
domain: "crm:E85_Joining".freeze,
|
1308
|
-
label:
|
1308
|
+
label: "joined with".freeze,
|
1309
1309
|
range: "crm:E74_Group".freeze,
|
1310
1310
|
subPropertyOf: "crm:P11_had_participant".freeze,
|
1311
1311
|
type: "rdf:Property".freeze
|
1312
1312
|
property :P144i_gained_member_by,
|
1313
1313
|
domain: "crm:E74_Group".freeze,
|
1314
|
-
label:
|
1314
|
+
label: "gained member by".freeze,
|
1315
1315
|
range: "crm:E85_Joining".freeze,
|
1316
1316
|
subPropertyOf: "crm:P11i_participated_in".freeze,
|
1317
1317
|
type: "rdf:Property".freeze
|
1318
1318
|
property :P145_separated,
|
1319
1319
|
comment: %(This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving.).freeze,
|
1320
1320
|
domain: "crm:E86_Leaving".freeze,
|
1321
|
-
label:
|
1321
|
+
label: "separated".freeze,
|
1322
1322
|
range: "crm:E39_Actor".freeze,
|
1323
1323
|
subPropertyOf: "crm:P11_had_participant".freeze,
|
1324
1324
|
type: "rdf:Property".freeze
|
1325
1325
|
property :P145i_left_by,
|
1326
1326
|
domain: "crm:E39_Actor".freeze,
|
1327
|
-
label:
|
1327
|
+
label: "left by".freeze,
|
1328
1328
|
range: "crm:E86_Leaving".freeze,
|
1329
1329
|
subPropertyOf: "crm:P11i_participated_in".freeze,
|
1330
1330
|
type: "rdf:Property".freeze
|
@@ -1333,13 +1333,13 @@ The property P144.1 kind of member can be used to specify the type of membership
|
|
1333
1333
|
Although a Leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well.
|
1334
1334
|
).freeze,
|
1335
1335
|
domain: "crm:E86_Leaving".freeze,
|
1336
|
-
label:
|
1336
|
+
label: "separated from".freeze,
|
1337
1337
|
range: "crm:E74_Group".freeze,
|
1338
1338
|
subPropertyOf: "crm:P11_had_participant".freeze,
|
1339
1339
|
type: "rdf:Property".freeze
|
1340
1340
|
property :P146i_lost_member_by,
|
1341
1341
|
domain: "crm:E74_Group".freeze,
|
1342
|
-
label:
|
1342
|
+
label: "lost member by".freeze,
|
1343
1343
|
range: "crm:E86_Leaving".freeze,
|
1344
1344
|
subPropertyOf: "crm:P11i_participated_in".freeze,
|
1345
1345
|
type: "rdf:Property".freeze
|
@@ -1347,23 +1347,23 @@ Although a Leaving activity normally concerns only one instance of E74 Group, it
|
|
1347
1347
|
comment: %(This property associates an instance of E87 Curation Activity with the instance of E78 Collection that is subject of that curation activity.
|
1348
1348
|
).freeze,
|
1349
1349
|
domain: "crm:E87_Curation_Activity".freeze,
|
1350
|
-
label:
|
1350
|
+
label: "curated".freeze,
|
1351
1351
|
range: "crm:E78_Collection".freeze,
|
1352
1352
|
type: "rdf:Property".freeze
|
1353
1353
|
property :P147i_was_curated_by,
|
1354
1354
|
domain: "crm:E78_Collection".freeze,
|
1355
|
-
label:
|
1355
|
+
label: "was curated by".freeze,
|
1356
1356
|
range: "crm:E87_Curation_Activity".freeze,
|
1357
1357
|
type: "rdf:Property".freeze
|
1358
1358
|
property :P148_has_component,
|
1359
1359
|
comment: %(This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object.).freeze,
|
1360
1360
|
domain: "crm:E89_Propositional_Object".freeze,
|
1361
|
-
label:
|
1361
|
+
label: "has component".freeze,
|
1362
1362
|
range: "crm:E89_Propositional_Object".freeze,
|
1363
1363
|
type: "rdf:Property".freeze
|
1364
1364
|
property :P148i_is_component_of,
|
1365
1365
|
domain: "crm:E89_Propositional_Object".freeze,
|
1366
|
-
label:
|
1366
|
+
label: "is component of".freeze,
|
1367
1367
|
range: "crm:E89_Propositional_Object".freeze,
|
1368
1368
|
type: "rdf:Property".freeze
|
1369
1369
|
property :P149_is_identified_by,
|
@@ -1384,13 +1384,13 @@ Although a Leaving activity normally concerns only one instance of E74 Group, it
|
|
1384
1384
|
It implies causal or legal responsibility. The P14.1 in the role of property of the property allows the nature of an Actor’s participation to be specified.
|
1385
1385
|
).freeze,
|
1386
1386
|
domain: "crm:E7_Activity".freeze,
|
1387
|
-
label:
|
1387
|
+
label: "carried out by".freeze,
|
1388
1388
|
range: "crm:E39_Actor".freeze,
|
1389
1389
|
subPropertyOf: "crm:P11_had_participant".freeze,
|
1390
1390
|
type: "rdf:Property".freeze
|
1391
1391
|
property :P14i_performed,
|
1392
1392
|
domain: "crm:E39_Actor".freeze,
|
1393
|
-
label:
|
1393
|
+
label: "performed".freeze,
|
1394
1394
|
range: "crm:E7_Activity".freeze,
|
1395
1395
|
subPropertyOf: "crm:P11i_participated_in".freeze,
|
1396
1396
|
type: "rdf:Property".freeze
|
@@ -1521,12 +1521,12 @@ Therefore it cannot be verified, if two different instances of E4 Period occupy
|
|
1521
1521
|
The property has more specific sub properties.
|
1522
1522
|
).freeze,
|
1523
1523
|
domain: "crm:E7_Activity".freeze,
|
1524
|
-
label:
|
1524
|
+
label: "was influenced by".freeze,
|
1525
1525
|
range: "crm:E1_CRM_Entity".freeze,
|
1526
1526
|
type: "rdf:Property".freeze
|
1527
1527
|
property :P15i_influenced,
|
1528
1528
|
domain: "crm:E1_CRM_Entity".freeze,
|
1529
|
-
label:
|
1529
|
+
label: "influenced".freeze,
|
1530
1530
|
range: "crm:E7_Activity".freeze,
|
1531
1531
|
type: "rdf:Property".freeze
|
1532
1532
|
property :P160_has_temporal_projection,
|
@@ -1571,13 +1571,13 @@ This property typically applies to tools, instruments, moulds, raw materials and
|
|
1571
1571
|
Another example is the use of a particular name by a particular group of people over some span to identify a thing, such as a settlement. In this case, the physical carriers of this name are at least the people understanding its use.
|
1572
1572
|
).freeze,
|
1573
1573
|
domain: "crm:E7_Activity".freeze,
|
1574
|
-
label:
|
1574
|
+
label: "used specific object".freeze,
|
1575
1575
|
range: "crm:E70_Thing".freeze,
|
1576
1576
|
subPropertyOf: ["crm:P12_occurred_in_the_presence_of".freeze, "crm:P15_was_influenced_by".freeze],
|
1577
1577
|
type: "rdf:Property".freeze
|
1578
1578
|
property :P16i_was_used_for,
|
1579
1579
|
domain: "crm:E70_Thing".freeze,
|
1580
|
-
label:
|
1580
|
+
label: "was used for".freeze,
|
1581
1581
|
range: "crm:E7_Activity".freeze,
|
1582
1582
|
subPropertyOf: ["crm:P12i_was_present_at".freeze, "crm:P15i_influenced".freeze],
|
1583
1583
|
type: "rdf:Property".freeze
|
@@ -1586,13 +1586,13 @@ Another example is the use of a particular name by a particular group of people
|
|
1586
1586
|
For example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre.
|
1587
1587
|
).freeze,
|
1588
1588
|
domain: "crm:E7_Activity".freeze,
|
1589
|
-
label:
|
1589
|
+
label: "was motivated by".freeze,
|
1590
1590
|
range: "crm:E1_CRM_Entity".freeze,
|
1591
1591
|
subPropertyOf: "crm:P15_was_influenced_by".freeze,
|
1592
1592
|
type: "rdf:Property".freeze
|
1593
1593
|
property :P17i_motivated,
|
1594
1594
|
domain: "crm:E1_CRM_Entity".freeze,
|
1595
|
-
label:
|
1595
|
+
label: "motivated".freeze,
|
1596
1596
|
range: "crm:E7_Activity".freeze,
|
1597
1597
|
subPropertyOf: "crm:P15i_influenced".freeze,
|
1598
1598
|
type: "rdf:Property".freeze
|
@@ -1600,12 +1600,12 @@ For example, the discovery of a large hoard of treasure may call for a celebrati
|
|
1600
1600
|
comment: %(This property relates an E7 Activity with objects created specifically for use in the activity.
|
1601
1601
|
This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services \(see P101 had as general use \(was use of\)\).).freeze,
|
1602
1602
|
domain: "crm:E7_Activity".freeze,
|
1603
|
-
label:
|
1603
|
+
label: "was intended use of".freeze,
|
1604
1604
|
range: "crm:E71_Man-Made_Thing".freeze,
|
1605
1605
|
type: "rdf:Property".freeze
|
1606
1606
|
property :P19i_was_made_for,
|
1607
1607
|
domain: "crm:E71_Man-Made_Thing".freeze,
|
1608
|
-
label:
|
1608
|
+
label: "was made for".freeze,
|
1609
1609
|
range: "crm:E7_Activity".freeze,
|
1610
1610
|
type: "rdf:Property".freeze
|
1611
1611
|
property :P1_is_identified_by,
|
@@ -1613,12 +1613,12 @@ This is distinct from the intended use of an item in some general type of activi
|
|
1613
1613
|
This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed \(i.e. indirect\) path through E15 Identifier Assignment.
|
1614
1614
|
).freeze,
|
1615
1615
|
domain: "crm:E1_CRM_Entity".freeze,
|
1616
|
-
label:
|
1616
|
+
label: "is identified by".freeze,
|
1617
1617
|
range: "crm:E41_Appellation".freeze,
|
1618
1618
|
type: "rdf:Property".freeze
|
1619
1619
|
property :P1i_identifies,
|
1620
1620
|
domain: "crm:E41_Appellation".freeze,
|
1621
|
-
label:
|
1621
|
+
label: "identifies".freeze,
|
1622
1622
|
range: "crm:E1_CRM_Entity".freeze,
|
1623
1623
|
type: "rdf:Property".freeze
|
1624
1624
|
property :P20_had_specific_purpose,
|
@@ -1626,12 +1626,12 @@ This property is intended for identifiers in general use, which form part of the
|
|
1626
1626
|
This includes activities, orders and other organisational actions, taken in preparation for other activities or events.
|
1627
1627
|
P20 had specific purpose \(was purpose of\) implies that an activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, one may document the unrealized intention using P21 had general purpose \(was purpose of\):E55 Type and/or P33 used specific technique \(was used by\): E29 Design or Procedure.).freeze,
|
1628
1628
|
domain: "crm:E7_Activity".freeze,
|
1629
|
-
label:
|
1629
|
+
label: "had specific purpose".freeze,
|
1630
1630
|
range: "crm:E5_Event".freeze,
|
1631
1631
|
type: "rdf:Property".freeze
|
1632
1632
|
property :P20i_was_purpose_of,
|
1633
1633
|
domain: "crm:E5_Event".freeze,
|
1634
|
-
label:
|
1634
|
+
label: "was purpose of".freeze,
|
1635
1635
|
range: "crm:E7_Activity".freeze,
|
1636
1636
|
type: "rdf:Property".freeze
|
1637
1637
|
property :P21_had_general_purpose,
|
@@ -1639,12 +1639,12 @@ P20 had specific purpose \(was purpose of\) implies that an activity succeeded i
|
|
1639
1639
|
This may involve activities intended as preparation for some type of activity or event. P21had general purpose \(was purpose of\) differs from P20 had specific purpose \(was purpose of\) in that no occurrence of an event is implied as the purpose.
|
1640
1640
|
).freeze,
|
1641
1641
|
domain: "crm:E7_Activity".freeze,
|
1642
|
-
label:
|
1642
|
+
label: "had general purpose".freeze,
|
1643
1643
|
range: "crm:E55_Type".freeze,
|
1644
1644
|
type: "rdf:Property".freeze
|
1645
1645
|
property :P21i_was_purpose_of,
|
1646
1646
|
domain: "crm:E55_Type".freeze,
|
1647
|
-
label:
|
1647
|
+
label: "was purpose of".freeze,
|
1648
1648
|
range: "crm:E7_Activity".freeze,
|
1649
1649
|
type: "rdf:Property".freeze
|
1650
1650
|
property :P22_transferred_title_to,
|
@@ -1653,13 +1653,13 @@ The property will typically describe an Actor purchasing or otherwise acquiring
|
|
1653
1653
|
In reality the title is either transferred to or from someone, or both.
|
1654
1654
|
).freeze,
|
1655
1655
|
domain: "crm:E8_Acquisition".freeze,
|
1656
|
-
label:
|
1656
|
+
label: "transferred title to".freeze,
|
1657
1657
|
range: "crm:E39_Actor".freeze,
|
1658
1658
|
subPropertyOf: "crm:P14_carried_out_by".freeze,
|
1659
1659
|
type: "rdf:Property".freeze
|
1660
1660
|
property :P22i_acquired_title_through,
|
1661
1661
|
domain: "crm:E39_Actor".freeze,
|
1662
|
-
label:
|
1662
|
+
label: "acquired title through".freeze,
|
1663
1663
|
range: "crm:E8_Acquisition".freeze,
|
1664
1664
|
subPropertyOf: "crm:P14i_performed".freeze,
|
1665
1665
|
type: "rdf:Property".freeze
|
@@ -1668,13 +1668,13 @@ In reality the title is either transferred to or from someone, or both.
|
|
1668
1668
|
The property will typically be used to describe a person donating or selling an object to a museum. In reality title is either transferred to or from someone, or both.
|
1669
1669
|
).freeze,
|
1670
1670
|
domain: "crm:E8_Acquisition".freeze,
|
1671
|
-
label:
|
1671
|
+
label: "transferred title from".freeze,
|
1672
1672
|
range: "crm:E39_Actor".freeze,
|
1673
1673
|
subPropertyOf: "crm:P14_carried_out_by".freeze,
|
1674
1674
|
type: "rdf:Property".freeze
|
1675
1675
|
property :P23i_surrendered_title_through,
|
1676
1676
|
domain: "crm:E39_Actor".freeze,
|
1677
|
-
label:
|
1677
|
+
label: "surrendered title through".freeze,
|
1678
1678
|
range: "crm:E8_Acquisition".freeze,
|
1679
1679
|
subPropertyOf: "crm:P14i_performed".freeze,
|
1680
1680
|
type: "rdf:Property".freeze
|
@@ -1683,12 +1683,12 @@ The property will typically be used to describe a person donating or selling an
|
|
1683
1683
|
In reality, an acquisition must refer to at least one transferred item.
|
1684
1684
|
).freeze,
|
1685
1685
|
domain: "crm:E8_Acquisition".freeze,
|
1686
|
-
label:
|
1686
|
+
label: "transferred title of".freeze,
|
1687
1687
|
range: "crm:E18_Physical_Thing".freeze,
|
1688
1688
|
type: "rdf:Property".freeze
|
1689
1689
|
property :P24i_changed_ownership_through,
|
1690
1690
|
domain: "crm:E18_Physical_Thing".freeze,
|
1691
|
-
label:
|
1691
|
+
label: "changed ownership through".freeze,
|
1692
1692
|
range: "crm:E8_Acquisition".freeze,
|
1693
1693
|
type: "rdf:Property".freeze
|
1694
1694
|
property :P25_moved,
|
@@ -1697,13 +1697,13 @@ The property implies the object’s passive participation. For example, Monet’
|
|
1697
1697
|
In reality, a move must concern at least one object.
|
1698
1698
|
).freeze,
|
1699
1699
|
domain: "crm:E9_Move".freeze,
|
1700
|
-
label:
|
1700
|
+
label: "moved".freeze,
|
1701
1701
|
range: "crm:E19_Physical_Object".freeze,
|
1702
1702
|
subPropertyOf: "crm:P12_occurred_in_the_presence_of".freeze,
|
1703
1703
|
type: "rdf:Property".freeze
|
1704
1704
|
property :P25i_moved_by,
|
1705
1705
|
domain: "crm:E19_Physical_Object".freeze,
|
1706
|
-
label:
|
1706
|
+
label: "moved by".freeze,
|
1707
1707
|
range: "crm:E9_Move".freeze,
|
1708
1708
|
subPropertyOf: "crm:P12i_was_present_at".freeze,
|
1709
1709
|
type: "rdf:Property".freeze
|
@@ -1712,13 +1712,13 @@ In reality, a move must concern at least one object.
|
|
1712
1712
|
A move will be linked to a destination, such as the move of an artefact from storage to display. A move may be linked to many terminal instances of E53 Places. In this case the move describes a distribution of a set of objects. The area of the move includes the origin, route and destination.
|
1713
1713
|
).freeze,
|
1714
1714
|
domain: "crm:E9_Move".freeze,
|
1715
|
-
label:
|
1715
|
+
label: "moved to".freeze,
|
1716
1716
|
range: "crm:E53_Place".freeze,
|
1717
1717
|
subPropertyOf: "crm:P7_took_place_at".freeze,
|
1718
1718
|
type: "rdf:Property".freeze
|
1719
1719
|
property :P26i_was_destination_of,
|
1720
1720
|
domain: "crm:E53_Place".freeze,
|
1721
|
-
label:
|
1721
|
+
label: "was destination of".freeze,
|
1722
1722
|
range: "crm:E9_Move".freeze,
|
1723
1723
|
subPropertyOf: "crm:P7i_witnessed".freeze,
|
1724
1724
|
type: "rdf:Property".freeze
|
@@ -1727,13 +1727,13 @@ A move will be linked to a destination, such as the move of an artefact from sto
|
|
1727
1727
|
A move will be linked to an origin, such as the move of an artefact from storage to display. A move may be linked to many origins. In this case the move describes the picking up of a set of objects. The area of the move includes the origin, route and destination.
|
1728
1728
|
).freeze,
|
1729
1729
|
domain: "crm:E9_Move".freeze,
|
1730
|
-
label:
|
1730
|
+
label: "moved from".freeze,
|
1731
1731
|
range: "crm:E53_Place".freeze,
|
1732
1732
|
subPropertyOf: "crm:P7_took_place_at".freeze,
|
1733
1733
|
type: "rdf:Property".freeze
|
1734
1734
|
property :P27i_was_origin_of,
|
1735
1735
|
domain: "crm:E53_Place".freeze,
|
1736
|
-
label:
|
1736
|
+
label: "was origin of".freeze,
|
1737
1737
|
range: "crm:E9_Move".freeze,
|
1738
1738
|
subPropertyOf: "crm:P7i_witnessed".freeze,
|
1739
1739
|
type: "rdf:Property".freeze
|
@@ -1743,13 +1743,13 @@ The property will typically describe an Actor surrendering custody of an object
|
|
1743
1743
|
In reality, custody is either transferred to someone or from someone, or both.
|
1744
1744
|
).freeze,
|
1745
1745
|
domain: "crm:E10_Transfer_of_Custody".freeze,
|
1746
|
-
label:
|
1746
|
+
label: "custody surrendered by".freeze,
|
1747
1747
|
range: "crm:E39_Actor".freeze,
|
1748
1748
|
subPropertyOf: "crm:P14_carried_out_by".freeze,
|
1749
1749
|
type: "rdf:Property".freeze
|
1750
1750
|
property :P28i_surrendered_custody_through,
|
1751
1751
|
domain: "crm:E39_Actor".freeze,
|
1752
|
-
label:
|
1752
|
+
label: "surrendered custody through".freeze,
|
1753
1753
|
range: "crm:E10_Transfer_of_Custody".freeze,
|
1754
1754
|
subPropertyOf: "crm:P14i_performed".freeze,
|
1755
1755
|
type: "rdf:Property".freeze
|
@@ -1759,13 +1759,13 @@ The property will typically describe Actors receiving custody of an object when
|
|
1759
1759
|
In reality, custody is either transferred to someone or from someone, or both.
|
1760
1760
|
).freeze,
|
1761
1761
|
domain: "crm:E10_Transfer_of_Custody".freeze,
|
1762
|
-
label:
|
1762
|
+
label: "custody received by".freeze,
|
1763
1763
|
range: "crm:E39_Actor".freeze,
|
1764
1764
|
subPropertyOf: "crm:P14_carried_out_by".freeze,
|
1765
1765
|
type: "rdf:Property".freeze
|
1766
1766
|
property :P29i_received_custody_through,
|
1767
1767
|
domain: "crm:E39_Actor".freeze,
|
1768
|
-
label:
|
1768
|
+
label: "received custody through".freeze,
|
1769
1769
|
range: "crm:E10_Transfer_of_Custody".freeze,
|
1770
1770
|
subPropertyOf: "crm:P14i_performed".freeze,
|
1771
1771
|
type: "rdf:Property".freeze
|
@@ -1774,12 +1774,12 @@ In reality, custody is either transferred to someone or from someone, or both.
|
|
1774
1774
|
The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question.
|
1775
1775
|
).freeze,
|
1776
1776
|
domain: "crm:E1_CRM_Entity".freeze,
|
1777
|
-
label:
|
1777
|
+
label: "has type".freeze,
|
1778
1778
|
range: "crm:E55_Type".freeze,
|
1779
1779
|
type: "rdf:Property".freeze
|
1780
1780
|
property :P2i_is_type_of,
|
1781
1781
|
domain: "crm:E55_Type".freeze,
|
1782
|
-
label:
|
1782
|
+
label: "is type of".freeze,
|
1783
1783
|
range: "crm:E1_CRM_Entity".freeze,
|
1784
1784
|
type: "rdf:Property".freeze
|
1785
1785
|
property :P30_transferred_custody_of,
|
@@ -1787,12 +1787,12 @@ The CRM is intended to focus on the high-level entities and relationships needed
|
|
1787
1787
|
The property will typically describe the object that is handed over by an E39 Actor to another Actor’s custody. On occasion, physical custody may be transferred involuntarily or illegally – through accident, unsolicited donation, or theft.
|
1788
1788
|
).freeze,
|
1789
1789
|
domain: "crm:E10_Transfer_of_Custody".freeze,
|
1790
|
-
label:
|
1790
|
+
label: "transferred custody of".freeze,
|
1791
1791
|
range: "crm:E18_Physical_Thing".freeze,
|
1792
1792
|
type: "rdf:Property".freeze
|
1793
1793
|
property :P30i_custody_transferred_through,
|
1794
1794
|
domain: "crm:E18_Physical_Thing".freeze,
|
1795
|
-
label:
|
1795
|
+
label: "custody transferred through".freeze,
|
1796
1796
|
range: "crm:E10_Transfer_of_Custody".freeze,
|
1797
1797
|
type: "rdf:Property".freeze
|
1798
1798
|
property :P31_has_modified,
|
@@ -1800,13 +1800,13 @@ The property will typically describe the object that is handed over by an E39 Ac
|
|
1800
1800
|
If a modification is applied to a non-man-made object, it is regarded as an E22 Man-Made Object from that time onwards.
|
1801
1801
|
).freeze,
|
1802
1802
|
domain: "crm:E11_Modification".freeze,
|
1803
|
-
label:
|
1803
|
+
label: "has modified".freeze,
|
1804
1804
|
range: "crm:E24_Physical_Man-Made_Thing".freeze,
|
1805
1805
|
subPropertyOf: "crm:P12_occurred_in_the_presence_of".freeze,
|
1806
1806
|
type: "rdf:Property".freeze
|
1807
1807
|
property :P31i_was_modified_by,
|
1808
1808
|
domain: "crm:E24_Physical_Man-Made_Thing".freeze,
|
1809
|
-
label:
|
1809
|
+
label: "was modified by".freeze,
|
1810
1810
|
range: "crm:E11_Modification".freeze,
|
1811
1811
|
subPropertyOf: "crm:P12i_was_present_at".freeze,
|
1812
1812
|
type: "rdf:Property".freeze
|
@@ -1815,13 +1815,13 @@ If a modification is applied to a non-man-made object, it is regarded as an E22
|
|
1815
1815
|
These techniques should be drawn from an external E55 Type hierarchy of consistent terminology of general techniques or methods such as embroidery, oil-painting, carbon dating, etc. Specific documented techniques should be described as instances of E29 Design or Procedure. This property identifies the technique that was employed in an act of modification.
|
1816
1816
|
).freeze,
|
1817
1817
|
domain: "crm:E7_Activity".freeze,
|
1818
|
-
label:
|
1818
|
+
label: "used general technique".freeze,
|
1819
1819
|
range: "crm:E55_Type".freeze,
|
1820
1820
|
subPropertyOf: "crm:P125_used_object_of_type".freeze,
|
1821
1821
|
type: "rdf:Property".freeze
|
1822
1822
|
property :P32i_was_technique_of,
|
1823
1823
|
domain: "crm:E55_Type".freeze,
|
1824
|
-
label:
|
1824
|
+
label: "was technique of".freeze,
|
1825
1825
|
range: "crm:E7_Activity".freeze,
|
1826
1826
|
subPropertyOf: "crm:P125i_was_type_of_object_used_in".freeze,
|
1827
1827
|
type: "rdf:Property".freeze
|
@@ -1831,13 +1831,13 @@ The property differs from P32 used general technique \(was technique of\) in tha
|
|
1831
1831
|
Typical examples would include intervention plans for conservation or the construction plans of a building.
|
1832
1832
|
).freeze,
|
1833
1833
|
domain: "crm:E7_Activity".freeze,
|
1834
|
-
label:
|
1834
|
+
label: "used specific technique".freeze,
|
1835
1835
|
range: "crm:E29_Design_or_Procedure".freeze,
|
1836
1836
|
subPropertyOf: "crm:P16_used_specific_object".freeze,
|
1837
1837
|
type: "rdf:Property".freeze
|
1838
1838
|
property :P33i_was_used_by,
|
1839
1839
|
domain: "crm:E29_Design_or_Procedure".freeze,
|
1840
|
-
label:
|
1840
|
+
label: "was used by".freeze,
|
1841
1841
|
range: "crm:E7_Activity".freeze,
|
1842
1842
|
subPropertyOf: "crm:P16i_was_used_for".freeze,
|
1843
1843
|
type: "rdf:Property".freeze
|
@@ -1846,26 +1846,26 @@ Typical examples would include intervention plans for conservation or the constr
|
|
1846
1846
|
Conditions may be assessed either by direct observation or using recorded evidence. In the latter case the E18 Physical Thing does not need to be present or extant.
|
1847
1847
|
).freeze,
|
1848
1848
|
domain: "crm:E14_Condition_Assessment".freeze,
|
1849
|
-
label:
|
1849
|
+
label: "concerned".freeze,
|
1850
1850
|
range: "crm:E18_Physical_Thing".freeze,
|
1851
1851
|
subPropertyOf: "crm:P140_assigned_attribute_to".freeze,
|
1852
1852
|
type: "rdf:Property".freeze
|
1853
1853
|
property :P34i_was_assessed_by,
|
1854
1854
|
domain: "crm:E18_Physical_Thing".freeze,
|
1855
|
-
label:
|
1855
|
+
label: "was assessed by".freeze,
|
1856
1856
|
range: "crm:E14_Condition_Assessment".freeze,
|
1857
1857
|
subPropertyOf: "crm:P140i_was_attributed_by".freeze,
|
1858
1858
|
type: "rdf:Property".freeze
|
1859
1859
|
property :P35_has_identified,
|
1860
1860
|
comment: %(This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity.).freeze,
|
1861
1861
|
domain: "crm:E14_Condition_Assessment".freeze,
|
1862
|
-
label:
|
1862
|
+
label: "has identified".freeze,
|
1863
1863
|
range: "crm:E3_Condition_State".freeze,
|
1864
1864
|
subPropertyOf: "crm:P141_assigned".freeze,
|
1865
1865
|
type: "rdf:Property".freeze
|
1866
1866
|
property :P35i_was_identified_by,
|
1867
1867
|
domain: "crm:E3_Condition_State".freeze,
|
1868
|
-
label:
|
1868
|
+
label: "was identified by".freeze,
|
1869
1869
|
range: "crm:E14_Condition_Assessment".freeze,
|
1870
1870
|
subPropertyOf: "crm:P141i_was_assigned_by".freeze,
|
1871
1871
|
type: "rdf:Property".freeze
|
@@ -1875,13 +1875,13 @@ The same identifier may be assigned on more than one occasion.
|
|
1875
1875
|
An Identifier might be created prior to an assignment.
|
1876
1876
|
).freeze,
|
1877
1877
|
domain: "crm:E15_Identifier_Assignment".freeze,
|
1878
|
-
label:
|
1878
|
+
label: "assigned".freeze,
|
1879
1879
|
range: "crm:E42_Identifier".freeze,
|
1880
1880
|
subPropertyOf: "crm:P141_assigned".freeze,
|
1881
1881
|
type: "rdf:Property".freeze
|
1882
1882
|
property :P37i_was_assigned_by,
|
1883
1883
|
domain: "crm:E42_Identifier".freeze,
|
1884
|
-
label:
|
1884
|
+
label: "was assigned by".freeze,
|
1885
1885
|
range: "crm:E15_Identifier_Assignment".freeze,
|
1886
1886
|
subPropertyOf: "crm:P141i_was_assigned_by".freeze,
|
1887
1887
|
type: "rdf:Property".freeze
|
@@ -1891,13 +1891,13 @@ Deassignment of an identifier may be necessary when an item is taken out of an i
|
|
1891
1891
|
The same identifier may be deassigned on more than one occasion.
|
1892
1892
|
).freeze,
|
1893
1893
|
domain: "crm:E15_Identifier_Assignment".freeze,
|
1894
|
-
label:
|
1894
|
+
label: "deassigned".freeze,
|
1895
1895
|
range: "crm:E42_Identifier".freeze,
|
1896
1896
|
subPropertyOf: "crm:P141_assigned".freeze,
|
1897
1897
|
type: "rdf:Property".freeze
|
1898
1898
|
property :P38i_was_deassigned_by,
|
1899
1899
|
domain: "crm:E42_Identifier".freeze,
|
1900
|
-
label:
|
1900
|
+
label: "was deassigned by".freeze,
|
1901
1901
|
range: "crm:E15_Identifier_Assignment".freeze,
|
1902
1902
|
subPropertyOf: "crm:P141i_was_assigned_by".freeze,
|
1903
1903
|
type: "rdf:Property".freeze
|
@@ -1905,13 +1905,13 @@ The same identifier may be deassigned on more than one occasion.
|
|
1905
1905
|
comment: %(This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event.
|
1906
1906
|
).freeze,
|
1907
1907
|
domain: "crm:E16_Measurement".freeze,
|
1908
|
-
label:
|
1908
|
+
label: "measured".freeze,
|
1909
1909
|
range: "crm:E1_CRM_Entity".freeze,
|
1910
1910
|
subPropertyOf: "crm:P140_assigned_attribute_to".freeze,
|
1911
1911
|
type: "rdf:Property".freeze
|
1912
1912
|
property :P39i_was_measured_by,
|
1913
1913
|
domain: "crm:E1_CRM_Entity".freeze,
|
1914
|
-
label:
|
1914
|
+
label: "was measured by".freeze,
|
1915
1915
|
range: "crm:E16_Measurement".freeze,
|
1916
1916
|
subPropertyOf: "crm:P140i_was_attributed_by".freeze,
|
1917
1917
|
type: "rdf:Property".freeze
|
@@ -1922,7 +1922,7 @@ Like property P2 has type \(is type of\), this property is a consequence of the
|
|
1922
1922
|
An item may have many notes, but a note is attached to a specific item.
|
1923
1923
|
).freeze,
|
1924
1924
|
domain: "crm:E1_CRM_Entity".freeze,
|
1925
|
-
label:
|
1925
|
+
label: "has note".freeze,
|
1926
1926
|
range: "rdfs:Literal".freeze,
|
1927
1927
|
type: "rdf:Property".freeze
|
1928
1928
|
property :P40_observed_dimension,
|
@@ -1932,13 +1932,13 @@ Dimensions may be determined either by direct observation or using recorded evid
|
|
1932
1932
|
Even though knowledge of the value of a dimension requires measurement, the dimension may be an object of discourse prior to, or even without, any measurement being made.
|
1933
1933
|
).freeze,
|
1934
1934
|
domain: "crm:E16_Measurement".freeze,
|
1935
|
-
label:
|
1935
|
+
label: "observed dimension".freeze,
|
1936
1936
|
range: "crm:E54_Dimension".freeze,
|
1937
1937
|
subPropertyOf: "crm:P141_assigned".freeze,
|
1938
1938
|
type: "rdf:Property".freeze
|
1939
1939
|
property :P40i_was_observed_in,
|
1940
1940
|
domain: "crm:E54_Dimension".freeze,
|
1941
|
-
label:
|
1941
|
+
label: "was observed in".freeze,
|
1942
1942
|
range: "crm:E16_Measurement".freeze,
|
1943
1943
|
subPropertyOf: "crm:P141i_was_assigned_by".freeze,
|
1944
1944
|
type: "rdf:Property".freeze
|
@@ -1947,13 +1947,13 @@ Even though knowledge of the value of a dimension requires measurement, the dime
|
|
1947
1947
|
Any instance of a CRM entity may be assigned a type through type assignment. Type assignment events allow a more detailed path from E1 CRM Entity through P41 classified \(was classified\), E17 Type Assignment, P42 assigned \(was assigned by\) to E55 Type for assigning types to objects compared to the shortcut offered by P2 has type \(is type of\).
|
1948
1948
|
).freeze,
|
1949
1949
|
domain: "crm:E17_Type_Assignment".freeze,
|
1950
|
-
label:
|
1950
|
+
label: "classified".freeze,
|
1951
1951
|
range: "crm:E1_CRM_Entity".freeze,
|
1952
1952
|
subPropertyOf: "crm:P140_assigned_attribute_to".freeze,
|
1953
1953
|
type: "rdf:Property".freeze
|
1954
1954
|
property :P41i_was_classified_by,
|
1955
1955
|
domain: "crm:E1_CRM_Entity".freeze,
|
1956
|
-
label:
|
1956
|
+
label: "was classified by".freeze,
|
1957
1957
|
range: "crm:E17_Type_Assignment".freeze,
|
1958
1958
|
subPropertyOf: "crm:P140i_was_attributed_by".freeze,
|
1959
1959
|
type: "rdf:Property".freeze
|
@@ -1964,13 +1964,13 @@ For example, a fragment of an antique vessel could be assigned the type “attic
|
|
1964
1964
|
A Type may be intellectually constructed independent from assigning an instance of it.
|
1965
1965
|
).freeze,
|
1966
1966
|
domain: "crm:E17_Type_Assignment".freeze,
|
1967
|
-
label:
|
1967
|
+
label: "assigned".freeze,
|
1968
1968
|
range: "crm:E55_Type".freeze,
|
1969
1969
|
subPropertyOf: "crm:P141_assigned".freeze,
|
1970
1970
|
type: "rdf:Property".freeze
|
1971
1971
|
property :P42i_was_assigned_by,
|
1972
1972
|
domain: "crm:E55_Type".freeze,
|
1973
|
-
label:
|
1973
|
+
label: "was assigned by".freeze,
|
1974
1974
|
range: "crm:E17_Type_Assignment".freeze,
|
1975
1975
|
subPropertyOf: "crm:P141i_was_assigned_by".freeze,
|
1976
1976
|
type: "rdf:Property".freeze
|
@@ -1980,12 +1980,12 @@ It is a shortcut of the more fully developed path from E70 Thing through P39 mea
|
|
1980
1980
|
An instance of E54 Dimension is specific to an instance of E70 Thing.
|
1981
1981
|
).freeze,
|
1982
1982
|
domain: "crm:E70_Thing".freeze,
|
1983
|
-
label:
|
1983
|
+
label: "has dimension".freeze,
|
1984
1984
|
range: "crm:E54_Dimension".freeze,
|
1985
1985
|
type: "rdf:Property".freeze
|
1986
1986
|
property :P43i_is_dimension_of,
|
1987
1987
|
domain: "crm:E54_Dimension".freeze,
|
1988
|
-
label:
|
1988
|
+
label: "is dimension of".freeze,
|
1989
1989
|
range: "crm:E70_Thing".freeze,
|
1990
1990
|
type: "rdf:Property".freeze
|
1991
1991
|
property :P44_has_condition,
|
@@ -1994,12 +1994,12 @@ It is a shortcut of the more fully developed path from E18 Physical Thing throug
|
|
1994
1994
|
An instance of Condition State is specific to an instance of Physical Thing.
|
1995
1995
|
).freeze,
|
1996
1996
|
domain: "crm:E18_Physical_Thing".freeze,
|
1997
|
-
label:
|
1997
|
+
label: "has condition".freeze,
|
1998
1998
|
range: "crm:E3_Condition_State".freeze,
|
1999
1999
|
type: "rdf:Property".freeze
|
2000
2000
|
property :P44i_is_condition_of,
|
2001
2001
|
domain: "crm:E3_Condition_State".freeze,
|
2002
|
-
label:
|
2002
|
+
label: "is condition of".freeze,
|
2003
2003
|
range: "crm:E18_Physical_Thing".freeze,
|
2004
2004
|
type: "rdf:Property".freeze
|
2005
2005
|
property :P45_consists_of,
|
@@ -2007,12 +2007,12 @@ An instance of Condition State is specific to an instance of Physical Thing.
|
|
2007
2007
|
All physical things consist of physical materials. P45 consists of \(is incorporated in\) allows the different Materials to be recorded. P45 consists of \(is incorporated in\) refers here to observed Material as opposed to the consumed raw material.
|
2008
2008
|
A Material, such as a theoretical alloy, may not have any physical instances).freeze,
|
2009
2009
|
domain: "crm:E18_Physical_Thing".freeze,
|
2010
|
-
label:
|
2010
|
+
label: "consists of".freeze,
|
2011
2011
|
range: "crm:E57_Material".freeze,
|
2012
2012
|
type: "rdf:Property".freeze
|
2013
2013
|
property :P45i_is_incorporated_in,
|
2014
2014
|
domain: "crm:E57_Material".freeze,
|
2015
|
-
label:
|
2015
|
+
label: "is incorporated in".freeze,
|
2016
2016
|
range: "crm:E18_Physical_Thing".freeze,
|
2017
2017
|
type: "rdf:Property".freeze
|
2018
2018
|
property :P46_is_composed_of,
|
@@ -2022,12 +2022,12 @@ This property is intended to describe specific components that are individually
|
|
2022
2022
|
The instances of E57 Materials of which an item of E18 Physical Thing is composed should be documented using P45 consists of \(is incorporated in\).
|
2023
2023
|
).freeze,
|
2024
2024
|
domain: "crm:E18_Physical_Thing".freeze,
|
2025
|
-
label:
|
2025
|
+
label: "is composed of".freeze,
|
2026
2026
|
range: "crm:E18_Physical_Thing".freeze,
|
2027
2027
|
type: "rdf:Property".freeze
|
2028
2028
|
property :P46i_forms_part_of,
|
2029
2029
|
domain: "crm:E18_Physical_Thing".freeze,
|
2030
|
-
label:
|
2030
|
+
label: "forms part of".freeze,
|
2031
2031
|
range: "crm:E18_Physical_Thing".freeze,
|
2032
2032
|
type: "rdf:Property".freeze
|
2033
2033
|
property :P48_has_preferred_identifier,
|
@@ -2037,13 +2037,13 @@ Use of this property requires an external mechanism for assigning temporal valid
|
|
2037
2037
|
P48 has preferred identifier \(is preferred identifier of\), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to \(was attributed by\), E15 Identifier Assignment, P37 assigned \(was assigned by\) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property.
|
2038
2038
|
).freeze,
|
2039
2039
|
domain: "crm:E1_CRM_Entity".freeze,
|
2040
|
-
label:
|
2040
|
+
label: "has preferred identifier".freeze,
|
2041
2041
|
range: "crm:E42_Identifier".freeze,
|
2042
2042
|
subPropertyOf: "crm:P1_is_identified_by".freeze,
|
2043
2043
|
type: "rdf:Property".freeze
|
2044
2044
|
property :P48i_is_preferred_identifier_of,
|
2045
2045
|
domain: "crm:E42_Identifier".freeze,
|
2046
|
-
label:
|
2046
|
+
label: "is preferred identifier of".freeze,
|
2047
2047
|
range: "crm:E1_CRM_Entity".freeze,
|
2048
2048
|
subPropertyOf: "crm:P1i_identifies".freeze,
|
2049
2049
|
type: "rdf:Property".freeze
|
@@ -2053,12 +2053,12 @@ The distinction with P50 has current keeper \(is current keeper of\) is that P49
|
|
2053
2053
|
P49 has former or current keeper \(is former or current keeper of\) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of \(custody transferred through\), E10 Transfer of Custody, P28 custody surrendered by \(surrendered custody through\) or P29 custody received by \(received custody through\) to E39 Actor.
|
2054
2054
|
).freeze,
|
2055
2055
|
domain: "crm:E18_Physical_Thing".freeze,
|
2056
|
-
label:
|
2056
|
+
label: "has former or current keeper".freeze,
|
2057
2057
|
range: "crm:E39_Actor".freeze,
|
2058
2058
|
type: "rdf:Property".freeze
|
2059
2059
|
property :P49i_is_former_or_current_keeper_of,
|
2060
2060
|
domain: "crm:E39_Actor".freeze,
|
2061
|
-
label:
|
2061
|
+
label: "is former or current keeper of".freeze,
|
2062
2062
|
range: "crm:E18_Physical_Thing".freeze,
|
2063
2063
|
type: "rdf:Property".freeze
|
2064
2064
|
property :"P4_has_time-span",
|
@@ -2066,12 +2066,12 @@ P49 has former or current keeper \(is former or current keeper of\) is a shortcu
|
|
2066
2066
|
The related E52 Time-Span is understood as the real Time-Span during which the phenomena were active, which make up the temporal entity instance. It does not convey any other meaning than a positioning on the “time-line” of chronology. The Time-Span in turn is approximated by a set of dates \(E61 Time Primitive\). A temporal entity can have in reality only one Time-Span, but there may exist alternative opinions about it, which we would express by assigning multiple Time-Spans. Related temporal entities may share a Time-Span. Time-Spans may have completely unknown dates but other descriptions by which we can infer knowledge.
|
2067
2067
|
).freeze,
|
2068
2068
|
domain: "crm:E2_Temporal_Entity".freeze,
|
2069
|
-
label:
|
2069
|
+
label: "has time-span".freeze,
|
2070
2070
|
range: "crm:E52_Time-Span".freeze,
|
2071
2071
|
type: "rdf:Property".freeze
|
2072
2072
|
property :"P4i_is_time-span_of",
|
2073
2073
|
domain: "crm:E52_Time-Span".freeze,
|
2074
|
-
label:
|
2074
|
+
label: "is time-span of".freeze,
|
2075
2075
|
range: "crm:E2_Temporal_Entity".freeze,
|
2076
2076
|
type: "rdf:Property".freeze
|
2077
2077
|
property :P50_has_current_keeper,
|
@@ -2079,13 +2079,13 @@ The related E52 Time-Span is understood as the real Time-Span during which the p
|
|
2079
2079
|
P50 has current keeper \(is current keeper of\) is a shortcut for the more detailed path from E18 Physical Thing through P30 transferred custody of \(custody transferred through\), E10 Transfer of Custody, P29 custody received by \(received custody through\) to E39 Actor.
|
2080
2080
|
).freeze,
|
2081
2081
|
domain: "crm:E18_Physical_Thing".freeze,
|
2082
|
-
label:
|
2082
|
+
label: "has current keeper".freeze,
|
2083
2083
|
range: "crm:E39_Actor".freeze,
|
2084
2084
|
subPropertyOf: "crm:P49_has_former_or_current_keeper".freeze,
|
2085
2085
|
type: "rdf:Property".freeze
|
2086
2086
|
property :P50i_is_current_keeper_of,
|
2087
2087
|
domain: "crm:E39_Actor".freeze,
|
2088
|
-
label:
|
2088
|
+
label: "is current keeper of".freeze,
|
2089
2089
|
range: "crm:E18_Physical_Thing".freeze,
|
2090
2090
|
subPropertyOf: "crm:P49i_is_former_or_current_keeper_of".freeze,
|
2091
2091
|
type: "rdf:Property".freeze
|
@@ -2094,12 +2094,12 @@ The related E52 Time-Span is understood as the real Time-Span during which the p
|
|
2094
2094
|
The distinction with P52 has current owner \(is current owner of\) is that P51 has former or current owner \(is former or current owner of\) does not indicate whether the specified owners are current. P51 has former or current owner \(is former or current owner of\) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of \(changed ownership through\), E8 Acquisition, P23 transferred title from \(surrendered title through\), or P22 transferred title to \(acquired title through\) to E39 Actor.
|
2095
2095
|
).freeze,
|
2096
2096
|
domain: "crm:E18_Physical_Thing".freeze,
|
2097
|
-
label:
|
2097
|
+
label: "has former or current owner".freeze,
|
2098
2098
|
range: "crm:E39_Actor".freeze,
|
2099
2099
|
type: "rdf:Property".freeze
|
2100
2100
|
property :P51i_is_former_or_current_owner_of,
|
2101
2101
|
domain: "crm:E39_Actor".freeze,
|
2102
|
-
label:
|
2102
|
+
label: "is former or current owner of".freeze,
|
2103
2103
|
range: "crm:E18_Physical_Thing".freeze,
|
2104
2104
|
type: "rdf:Property".freeze
|
2105
2105
|
property :P52_has_current_owner,
|
@@ -2107,13 +2107,13 @@ The distinction with P52 has current owner \(is current owner of\) is that P51 h
|
|
2107
2107
|
P52 has current owner \(is current owner of\) is a shortcut for the more detailed path from E18 Physical Thing through P24 transferred title of \(changed ownership through\), E8 Acquisition, P22 transferred title to \(acquired title through\) to E39 Actor, if and only if this acquisition event is the most recent.
|
2108
2108
|
).freeze,
|
2109
2109
|
domain: "crm:E18_Physical_Thing".freeze,
|
2110
|
-
label:
|
2110
|
+
label: "has current owner".freeze,
|
2111
2111
|
range: "crm:E39_Actor".freeze,
|
2112
2112
|
subPropertyOf: ["crm:P105_right_held_by".freeze, "crm:P51_has_former_or_current_owner".freeze],
|
2113
2113
|
type: "rdf:Property".freeze
|
2114
2114
|
property :P52i_is_current_owner_of,
|
2115
2115
|
domain: "crm:E39_Actor".freeze,
|
2116
|
-
label:
|
2116
|
+
label: "is current owner of".freeze,
|
2117
2117
|
range: "crm:E18_Physical_Thing".freeze,
|
2118
2118
|
subPropertyOf: ["crm:P105i_has_right_on".freeze, "crm:P51i_is_former_or_current_owner_of".freeze],
|
2119
2119
|
type: "rdf:Property".freeze
|
@@ -2124,12 +2124,12 @@ In the case of immobile objects, the Place would normally correspond to the Plac
|
|
2124
2124
|
P53 has former or current location \(is former or current location of\) is a shortcut. A more detailed representation can make use of the fully developed \(i.e. indirect\) path from E19 Physical Object through P25 moved \(moved by\), E9 Move, P26 moved to \(was destination of\) or P27 moved from \(was origin of\) to E53 Place.
|
2125
2125
|
).freeze,
|
2126
2126
|
domain: "crm:E18_Physical_Thing".freeze,
|
2127
|
-
label:
|
2127
|
+
label: "has former or current location".freeze,
|
2128
2128
|
range: "crm:E53_Place".freeze,
|
2129
2129
|
type: "rdf:Property".freeze
|
2130
2130
|
property :P53i_is_former_or_current_location_of,
|
2131
2131
|
domain: "crm:E53_Place".freeze,
|
2132
|
-
label:
|
2132
|
+
label: "is former or current location of".freeze,
|
2133
2133
|
range: "crm:E18_Physical_Thing".freeze,
|
2134
2134
|
type: "rdf:Property".freeze
|
2135
2135
|
property :P54_has_current_permanent_location,
|
@@ -2137,12 +2137,12 @@ P53 has former or current location \(is former or current location of\) is a sho
|
|
2137
2137
|
P54 has current permanent location \(is current permanent location of\) is similar to P55 has current location \(currently holds\). However, it indicates the E53 Place currently reserved for an object, such as the permanent storage location or a permanent exhibit location. The object may be temporarily removed from the permanent location, for example when used in temporary exhibitions or loaned to another institution. The object may never actually be located at its permanent location.
|
2138
2138
|
).freeze,
|
2139
2139
|
domain: "crm:E19_Physical_Object".freeze,
|
2140
|
-
label:
|
2140
|
+
label: "has current permanent location".freeze,
|
2141
2141
|
range: "crm:E53_Place".freeze,
|
2142
2142
|
type: "rdf:Property".freeze
|
2143
2143
|
property :P54i_is_current_permanent_location_of,
|
2144
2144
|
domain: "crm:E53_Place".freeze,
|
2145
|
-
label:
|
2145
|
+
label: "is current permanent location of".freeze,
|
2146
2146
|
range: "crm:E19_Physical_Object".freeze,
|
2147
2147
|
type: "rdf:Property".freeze
|
2148
2148
|
property :P55_has_current_location,
|
@@ -2151,13 +2151,13 @@ P54 has current permanent location \(is current permanent location of\) is simil
|
|
2151
2151
|
P55 has current location \(currently holds\) is a shortcut. A more detailed representation can make use of the fully developed \(i.e. indirect\) path from E19 Physical Object through P25 moved \(moved by\), E9 Move P26 moved to \(was destination of\) to E53 Place if and only if this Move is the most recent.
|
2152
2152
|
).freeze,
|
2153
2153
|
domain: "crm:E19_Physical_Object".freeze,
|
2154
|
-
label:
|
2154
|
+
label: "has current location".freeze,
|
2155
2155
|
range: "crm:E53_Place".freeze,
|
2156
2156
|
subPropertyOf: "crm:P53_has_former_or_current_location".freeze,
|
2157
2157
|
type: "rdf:Property".freeze
|
2158
2158
|
property :P55i_currently_holds,
|
2159
2159
|
domain: "crm:E53_Place".freeze,
|
2160
|
-
label:
|
2160
|
+
label: "currently holds".freeze,
|
2161
2161
|
range: "crm:E19_Physical_Object".freeze,
|
2162
2162
|
subPropertyOf: "crm:P53i_is_former_or_current_location_of".freeze,
|
2163
2163
|
type: "rdf:Property".freeze
|
@@ -2169,13 +2169,13 @@ P56 bears feature \(is found on\) is a shortcut. A more detailed representation
|
|
2169
2169
|
Definition of the CIDOC Conceptual Reference Model 149 within\), E53 Place, P53 has former or current location \(is former or current location of\) to E26 Physical Feature.
|
2170
2170
|
).freeze,
|
2171
2171
|
domain: "crm:E19_Physical_Object".freeze,
|
2172
|
-
label:
|
2172
|
+
label: "bears feature".freeze,
|
2173
2173
|
range: "crm:E26_Physical_Feature".freeze,
|
2174
2174
|
subPropertyOf: "crm:P46_is_composed_of".freeze,
|
2175
2175
|
type: "rdf:Property".freeze
|
2176
2176
|
property :P56i_is_found_on,
|
2177
2177
|
domain: "crm:E26_Physical_Feature".freeze,
|
2178
|
-
label:
|
2178
|
+
label: "is found on".freeze,
|
2179
2179
|
range: "crm:E19_Physical_Object".freeze,
|
2180
2180
|
subPropertyOf: "crm:P46i_forms_part_of".freeze,
|
2181
2181
|
type: "rdf:Property".freeze
|
@@ -2185,7 +2185,7 @@ This may be used as a method of checking inventory counts with regard to aggrega
|
|
2185
2185
|
For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of \(forms parts of\) and P45 consists of \(is incorporated in\). This allows each element to be described individually.
|
2186
2186
|
).freeze,
|
2187
2187
|
domain: "crm:E19_Physical_Object".freeze,
|
2188
|
-
label:
|
2188
|
+
label: "has number of parts".freeze,
|
2189
2189
|
range: "rdfs:Literal".freeze,
|
2190
2190
|
type: "rdf:Property".freeze
|
2191
2191
|
property :P58_has_section_definition,
|
@@ -2194,12 +2194,12 @@ The CRM handles sections as locations \(instances of E53 Place\) within or on E1
|
|
2194
2194
|
This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by \(identifies\) that allows a more precise definition of a location found on an object than the shortcut P59 has section \(is located on or within\).
|
2195
2195
|
A particular instance of a Section Definition only applies to one instance of Physical Thing.).freeze,
|
2196
2196
|
domain: "crm:E18_Physical_Thing".freeze,
|
2197
|
-
label:
|
2197
|
+
label: "has section definition".freeze,
|
2198
2198
|
range: "crm:E46_Section_Definition".freeze,
|
2199
2199
|
type: "rdf:Property".freeze
|
2200
2200
|
property :P58i_defines_section,
|
2201
2201
|
domain: "crm:E46_Section_Definition".freeze,
|
2202
|
-
label:
|
2202
|
+
label: "defines section".freeze,
|
2203
2203
|
range: "crm:E18_Physical_Thing".freeze,
|
2204
2204
|
type: "rdf:Property".freeze
|
2205
2205
|
property :P59_has_section,
|
@@ -2209,24 +2209,24 @@ E18 Physical Thing may be subdivided into arbitrary regions.
|
|
2209
2209
|
P59 has section \(is located on or within\) is a shortcut. If the E53 Place is identified by a Section Definition, a more detailed representation can make use of the fully developed \(i.e. indirect\) path from E18 Physical Thing through P58 has section definition \(defines section\), E46 Section Definition, P87 is identified by \(identifies\) to E53 Place. A Place can only be located on or within one Physical Object.
|
2210
2210
|
).freeze,
|
2211
2211
|
domain: "crm:E18_Physical_Thing".freeze,
|
2212
|
-
label:
|
2212
|
+
label: "has section".freeze,
|
2213
2213
|
range: "crm:E53_Place".freeze,
|
2214
2214
|
type: "rdf:Property".freeze
|
2215
2215
|
property :P59i_is_located_on_or_within,
|
2216
2216
|
domain: "crm:E53_Place".freeze,
|
2217
|
-
label:
|
2217
|
+
label: "is located on or within".freeze,
|
2218
2218
|
range: "crm:E18_Physical_Thing".freeze,
|
2219
2219
|
type: "rdf:Property".freeze
|
2220
2220
|
property :P5_consists_of,
|
2221
2221
|
comment: %(This property describes the decomposition of an E3 Condition State into discrete, subsidiary states.
|
2222
2222
|
It is assumed that the sub-states into which the condition state is analysed form a logical whole - although the entire story may not be completely known – and that the sub-states are in fact constitutive of the general condition state. For example, a general condition state of “in ruins” may be decomposed into the individual stages of decay).freeze,
|
2223
2223
|
domain: "crm:E3_Condition_State".freeze,
|
2224
|
-
label:
|
2224
|
+
label: "consists of".freeze,
|
2225
2225
|
range: "crm:E3_Condition_State".freeze,
|
2226
2226
|
type: "rdf:Property".freeze
|
2227
2227
|
property :P5i_forms_part_of,
|
2228
2228
|
domain: "crm:E3_Condition_State".freeze,
|
2229
|
-
label:
|
2229
|
+
label: "forms part of".freeze,
|
2230
2230
|
range: "crm:E3_Condition_State".freeze,
|
2231
2231
|
type: "rdf:Property".freeze
|
2232
2232
|
property :P62_depicts,
|
@@ -2234,12 +2234,12 @@ It is assumed that the sub-states into which the condition state is analysed for
|
|
2234
2234
|
This property is a shortcut of the more fully developed path from E24 Physical Man-Made Thing through P65 shows visual item \(is shown by\), E36 Visual Item, P138 represents \(has representation\) to E1CRM Entity. P62.1 mode of depiction allows the nature of the depiction to be refined.
|
2235
2235
|
).freeze,
|
2236
2236
|
domain: "crm:E24_Physical_Man-Made_Thing".freeze,
|
2237
|
-
label:
|
2237
|
+
label: "depicts".freeze,
|
2238
2238
|
range: "crm:E1_CRM_Entity".freeze,
|
2239
2239
|
type: "rdf:Property".freeze
|
2240
2240
|
property :P62i_is_depicted_by,
|
2241
2241
|
domain: "crm:E1_CRM_Entity".freeze,
|
2242
|
-
label:
|
2242
|
+
label: "is depicted by".freeze,
|
2243
2243
|
range: "crm:E24_Physical_Man-Made_Thing".freeze,
|
2244
2244
|
type: "rdf:Property".freeze
|
2245
2245
|
property :P65_shows_visual_item,
|
@@ -2250,13 +2250,13 @@ P65 shows visual item \(is shown by\) may also be used for Visual Items such as
|
|
2250
2250
|
This property is part of the fully developed path from E24 Physical Man-Made Thing through P65 shows visual item \(is shown by\), E36 Visual Item, P138 represents \(has representation\) to E1 CRM Entity which is shortcut by, P62 depicts \(is depicted by\).
|
2251
2251
|
).freeze,
|
2252
2252
|
domain: "crm:E24_Physical_Man-Made_Thing".freeze,
|
2253
|
-
label:
|
2253
|
+
label: "shows visual item".freeze,
|
2254
2254
|
range: "crm:E36_Visual_Item".freeze,
|
2255
2255
|
subPropertyOf: "crm:P128_carries".freeze,
|
2256
2256
|
type: "rdf:Property".freeze
|
2257
2257
|
property :P65i_is_shown_by,
|
2258
2258
|
domain: "crm:E36_Visual_Item".freeze,
|
2259
|
-
label:
|
2259
|
+
label: "is shown by".freeze,
|
2260
2260
|
range: "crm:E24_Physical_Man-Made_Thing".freeze,
|
2261
2261
|
subPropertyOf: "crm:P128i_is_carried_by".freeze,
|
2262
2262
|
type: "rdf:Property".freeze
|
@@ -2264,12 +2264,12 @@ This property is part of the fully developed path from E24 Physical Man-Made Thi
|
|
2264
2264
|
comment: %(This property documents that an E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to \(is referred to by\) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about \(is subject of\), which describes the primary subject or subjects of the E89 Propositional Object.
|
2265
2265
|
).freeze,
|
2266
2266
|
domain: "crm:E89_Propositional_Object".freeze,
|
2267
|
-
label:
|
2267
|
+
label: "refers to".freeze,
|
2268
2268
|
range: "crm:E1_CRM_Entity".freeze,
|
2269
2269
|
type: "rdf:Property".freeze
|
2270
2270
|
property :P67i_is_referred_to_by,
|
2271
2271
|
domain: "crm:E1_CRM_Entity".freeze,
|
2272
|
-
label:
|
2272
|
+
label: "is referred to by".freeze,
|
2273
2273
|
range: "crm:E89_Propositional_Object".freeze,
|
2274
2274
|
type: "rdf:Property".freeze
|
2275
2275
|
property :P68_foresees_use_of,
|
@@ -2278,13 +2278,13 @@ E29 Designs and procedures commonly foresee the use of particular E57 Materials.
|
|
2278
2278
|
This property is not intended for the documentation of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed.
|
2279
2279
|
).freeze,
|
2280
2280
|
domain: "crm:E29_Design_or_Procedure".freeze,
|
2281
|
-
label:
|
2281
|
+
label: "foresees use of".freeze,
|
2282
2282
|
range: "crm:E57_Material".freeze,
|
2283
2283
|
subPropertyOf: "crm:P67_refers_to".freeze,
|
2284
2284
|
type: "rdf:Property".freeze
|
2285
2285
|
property :P68i_use_foreseen_by,
|
2286
2286
|
domain: "crm:E57_Material".freeze,
|
2287
|
-
label:
|
2287
|
+
label: "use foreseen by".freeze,
|
2288
2288
|
range: "crm:E29_Design_or_Procedure".freeze,
|
2289
2289
|
subPropertyOf: "crm:P67i_is_referred_to_by".freeze,
|
2290
2290
|
type: "rdf:Property".freeze
|
@@ -2294,7 +2294,7 @@ The P69.1 has type property of P69 has association with allows the nature of the
|
|
2294
2294
|
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
|
2295
2295
|
).freeze,
|
2296
2296
|
domain: "crm:E29_Design_or_Procedure".freeze,
|
2297
|
-
label:
|
2297
|
+
label: "is associated with".freeze,
|
2298
2298
|
range: "crm:E29_Design_or_Procedure".freeze,
|
2299
2299
|
type: "rdf:Property".freeze
|
2300
2300
|
property :P70_documents,
|
@@ -2302,13 +2302,13 @@ The property can typically be used to model the decomposition of the description
|
|
2302
2302
|
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense.
|
2303
2303
|
).freeze,
|
2304
2304
|
domain: "crm:E31_Document".freeze,
|
2305
|
-
label:
|
2305
|
+
label: "documents".freeze,
|
2306
2306
|
range: "crm:E1_CRM_Entity".freeze,
|
2307
2307
|
subPropertyOf: "crm:P67_refers_to".freeze,
|
2308
2308
|
type: "rdf:Property".freeze
|
2309
2309
|
property :P70i_is_documented_in,
|
2310
2310
|
domain: "crm:E1_CRM_Entity".freeze,
|
2311
|
-
label:
|
2311
|
+
label: "is documented in".freeze,
|
2312
2312
|
range: "crm:E31_Document".freeze,
|
2313
2313
|
subPropertyOf: "crm:P67i_is_referred_to_by".freeze,
|
2314
2314
|
type: "rdf:Property".freeze
|
@@ -2316,13 +2316,13 @@ Documents may describe any conceivable entity, hence the link to the highest-lev
|
|
2316
2316
|
comment: %(This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
|
2317
2317
|
).freeze,
|
2318
2318
|
domain: "crm:E32_Authority_Document".freeze,
|
2319
|
-
label:
|
2319
|
+
label: "lists".freeze,
|
2320
2320
|
range: "crm:E1_CRM_Entity".freeze,
|
2321
2321
|
subPropertyOf: "crm:P67_refers_to".freeze,
|
2322
2322
|
type: "rdf:Property".freeze
|
2323
2323
|
property :P71i_is_listed_in,
|
2324
2324
|
domain: "crm:E1_CRM_Entity".freeze,
|
2325
|
-
label:
|
2325
|
+
label: "is listed in".freeze,
|
2326
2326
|
range: "crm:E32_Authority_Document".freeze,
|
2327
2327
|
subPropertyOf: "crm:P67i_is_referred_to_by".freeze,
|
2328
2328
|
type: "rdf:Property".freeze
|
@@ -2331,12 +2331,12 @@ Documents may describe any conceivable entity, hence the link to the highest-lev
|
|
2331
2331
|
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
|
2332
2332
|
).freeze,
|
2333
2333
|
domain: "crm:E33_Linguistic_Object".freeze,
|
2334
|
-
label:
|
2334
|
+
label: "has language".freeze,
|
2335
2335
|
range: "crm:E56_Language".freeze,
|
2336
2336
|
type: "rdf:Property".freeze
|
2337
2337
|
property :P72i_is_language_of,
|
2338
2338
|
domain: "crm:E56_Language".freeze,
|
2339
|
-
label:
|
2339
|
+
label: "is language of".freeze,
|
2340
2340
|
range: "crm:E33_Linguistic_Object".freeze,
|
2341
2341
|
type: "rdf:Property".freeze
|
2342
2342
|
property :P73_has_translation,
|
@@ -2344,13 +2344,13 @@ Linguistic Objects are composed in one or more human Languages. This property al
|
|
2344
2344
|
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
|
2345
2345
|
).freeze,
|
2346
2346
|
domain: "crm:E33_Linguistic_Object".freeze,
|
2347
|
-
label:
|
2347
|
+
label: "has translation".freeze,
|
2348
2348
|
range: "crm:E33_Linguistic_Object".freeze,
|
2349
2349
|
subPropertyOf: "crm:P130_shows_features_of".freeze,
|
2350
2350
|
type: "rdf:Property".freeze
|
2351
2351
|
property :P73i_is_translation_of,
|
2352
2352
|
domain: "crm:E33_Linguistic_Object".freeze,
|
2353
|
-
label:
|
2353
|
+
label: "is translation of".freeze,
|
2354
2354
|
range: "crm:E33_Linguistic_Object".freeze,
|
2355
2355
|
subPropertyOf: "crm:P130i_features_are_also_found_on".freeze,
|
2356
2356
|
type: "rdf:Property".freeze
|
@@ -2359,47 +2359,47 @@ When a Linguistic Object is translated into a new language it becomes a new Ling
|
|
2359
2359
|
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
|
2360
2360
|
).freeze,
|
2361
2361
|
domain: "crm:E39_Actor".freeze,
|
2362
|
-
label:
|
2362
|
+
label: "has current or former residence".freeze,
|
2363
2363
|
range: "crm:E53_Place".freeze,
|
2364
2364
|
type: "rdf:Property".freeze
|
2365
2365
|
property :P74i_is_current_or_former_residence_of,
|
2366
2366
|
domain: "crm:E53_Place".freeze,
|
2367
|
-
label:
|
2367
|
+
label: "is current or former residence of".freeze,
|
2368
2368
|
range: "crm:E39_Actor".freeze,
|
2369
2369
|
type: "rdf:Property".freeze
|
2370
2370
|
property :P75_possesses,
|
2371
2371
|
comment: %(This property identifies former or current instances of E30 Rights held by an E39 Actor.).freeze,
|
2372
2372
|
domain: "crm:E39_Actor".freeze,
|
2373
|
-
label:
|
2373
|
+
label: "possesses".freeze,
|
2374
2374
|
range: "crm:E30_Right".freeze,
|
2375
2375
|
type: "rdf:Property".freeze
|
2376
2376
|
property :P75i_is_possessed_by,
|
2377
2377
|
domain: "crm:E30_Right".freeze,
|
2378
|
-
label:
|
2378
|
+
label: "is possessed by".freeze,
|
2379
2379
|
range: "crm:E39_Actor".freeze,
|
2380
2380
|
type: "rdf:Property".freeze
|
2381
2381
|
property :P76_has_contact_point,
|
2382
2382
|
comment: %(This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
|
2383
2383
|
).freeze,
|
2384
2384
|
domain: "crm:E39_Actor".freeze,
|
2385
|
-
label:
|
2385
|
+
label: "has contact point".freeze,
|
2386
2386
|
range: "crm:E51_Contact_Point".freeze,
|
2387
2387
|
type: "rdf:Property".freeze
|
2388
2388
|
property :P76i_provides_access_to,
|
2389
2389
|
domain: "crm:E51_Contact_Point".freeze,
|
2390
|
-
label:
|
2390
|
+
label: "provides access to".freeze,
|
2391
2391
|
range: "crm:E39_Actor".freeze,
|
2392
2392
|
type: "rdf:Property".freeze
|
2393
2393
|
property :P78_is_identified_by,
|
2394
2394
|
comment: %(This property identifies an E52 Time-Span using an E49Time Appellation.).freeze,
|
2395
2395
|
domain: "crm:E52_Time-Span".freeze,
|
2396
|
-
label:
|
2396
|
+
label: "is identified by".freeze,
|
2397
2397
|
range: "crm:E49_Time_Appellation".freeze,
|
2398
2398
|
subPropertyOf: "crm:P1_is_identified_by".freeze,
|
2399
2399
|
type: "rdf:Property".freeze
|
2400
2400
|
property :P78i_identifies,
|
2401
2401
|
domain: "crm:E49_Time_Appellation".freeze,
|
2402
|
-
label:
|
2402
|
+
label: "identifies".freeze,
|
2403
2403
|
range: "crm:E52_Time-Span".freeze,
|
2404
2404
|
subPropertyOf: "crm:P1i_identifies".freeze,
|
2405
2405
|
type: "rdf:Property".freeze
|
@@ -2408,7 +2408,7 @@ The residence may be either the Place where the Actor resides, or a legally regi
|
|
2408
2408
|
The nature of the qualification may be certainty, precision, source etc.
|
2409
2409
|
).freeze,
|
2410
2410
|
domain: "crm:E52_Time-Span".freeze,
|
2411
|
-
label:
|
2411
|
+
label: "beginning is qualified by".freeze,
|
2412
2412
|
range: "rdfs:Literal".freeze,
|
2413
2413
|
subPropertyOf: "crm:P3_has_note".freeze,
|
2414
2414
|
type: "rdf:Property".freeze
|
@@ -2418,12 +2418,12 @@ The related E53 Place should be seen as an approximation of the geographical are
|
|
2418
2418
|
A period can take place at multiple locations.
|
2419
2419
|
).freeze,
|
2420
2420
|
domain: "crm:E4_Period".freeze,
|
2421
|
-
label:
|
2421
|
+
label: "took place at".freeze,
|
2422
2422
|
range: "crm:E53_Place".freeze,
|
2423
2423
|
type: "rdf:Property".freeze
|
2424
2424
|
property :P7i_witnessed,
|
2425
2425
|
domain: "crm:E53_Place".freeze,
|
2426
|
-
label:
|
2426
|
+
label: "witnessed".freeze,
|
2427
2427
|
range: "crm:E4_Period".freeze,
|
2428
2428
|
type: "rdf:Property".freeze
|
2429
2429
|
property :P80_end_is_qualified_by,
|
@@ -2431,7 +2431,7 @@ A period can take place at multiple locations.
|
|
2431
2431
|
The nature of the qualification may be certainty, precision, source etc.
|
2432
2432
|
).freeze,
|
2433
2433
|
domain: "crm:E52_Time-Span".freeze,
|
2434
|
-
label:
|
2434
|
+
label: "end is qualified by".freeze,
|
2435
2435
|
range: "rdfs:Literal".freeze,
|
2436
2436
|
subPropertyOf: "crm:P3_has_note".freeze,
|
2437
2437
|
type: "rdf:Property".freeze
|
@@ -2440,20 +2440,20 @@ The nature of the qualification may be certainty, precision, source etc.
|
|
2440
2440
|
Since Time-Spans may not have precisely known temporal extents, the CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s minimum temporal extent \(i.e. its inner boundary\) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CRM as application or system specific date intervals, and are not further analysed.
|
2441
2441
|
).freeze,
|
2442
2442
|
domain: "crm:E52_Time-Span".freeze,
|
2443
|
-
label:
|
2443
|
+
label: "ongoing throughout".freeze,
|
2444
2444
|
range: "rdfs:Literal".freeze,
|
2445
2445
|
type: "rdf:Property".freeze
|
2446
2446
|
property :P81a_end_of_the_begin,
|
2447
2447
|
comment: %(This is defined as the first boundary of the property P81).freeze,
|
2448
2448
|
domain: "crm:E52_Time-Span".freeze,
|
2449
|
-
label:
|
2449
|
+
label: "end of the begin".freeze,
|
2450
2450
|
range: "xsd:dateTime".freeze,
|
2451
2451
|
subPropertyOf: "crm:P81_ongoing_throughout".freeze,
|
2452
2452
|
type: "rdf:Property".freeze
|
2453
2453
|
property :P81b_begin_of_the_end,
|
2454
2454
|
comment: %(This is defined as the second boundary of the property P81).freeze,
|
2455
2455
|
domain: "crm:E52_Time-Span".freeze,
|
2456
|
-
label:
|
2456
|
+
label: "begin of the end".freeze,
|
2457
2457
|
range: "xsd:dateTime".freeze,
|
2458
2458
|
subPropertyOf: "crm:P81_ongoing_throughout".freeze,
|
2459
2459
|
type: "rdf:Property".freeze
|
@@ -2462,20 +2462,20 @@ Since Time-Spans may not have precisely known temporal extents, the CRM supports
|
|
2462
2462
|
Since Time-Spans may not have precisely known temporal extents, the CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows a Time-Span’s maximum temporal extent \(i.e. its outer boundary\) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CRM as application or system specific date intervals, and are not further analysed.
|
2463
2463
|
).freeze,
|
2464
2464
|
domain: "crm:E52_Time-Span".freeze,
|
2465
|
-
label:
|
2465
|
+
label: "at some time within".freeze,
|
2466
2466
|
range: "rdfs:Literal".freeze,
|
2467
2467
|
type: "rdf:Property".freeze
|
2468
2468
|
property :P82a_begin_of_the_begin,
|
2469
2469
|
comment: %(This is defined as the first boundary of the property P82).freeze,
|
2470
2470
|
domain: "crm:E52_Time-Span".freeze,
|
2471
|
-
label:
|
2471
|
+
label: "begin of the begin".freeze,
|
2472
2472
|
range: "xsd:dateTime".freeze,
|
2473
2473
|
subPropertyOf: "crm:P82_at_some_time_within".freeze,
|
2474
2474
|
type: "rdf:Property".freeze
|
2475
2475
|
property :P82b_end_of_the_end,
|
2476
2476
|
comment: %(This is defined as the second boundary of the property P82).freeze,
|
2477
2477
|
domain: "crm:E52_Time-Span".freeze,
|
2478
|
-
label:
|
2478
|
+
label: "end of the end".freeze,
|
2479
2479
|
range: "xsd:dateTime".freeze,
|
2480
2480
|
subPropertyOf: "crm:P82_at_some_time_within".freeze,
|
2481
2481
|
type: "rdf:Property".freeze
|
@@ -2484,12 +2484,12 @@ Since Time-Spans may not have precisely known temporal extents, the CRM supports
|
|
2484
2484
|
It allows an E52 Time-Span to be associated with an E54 Dimension representing it’s minimum duration \(i.e. it’s inner boundary\) independent from the actual beginning and end.
|
2485
2485
|
).freeze,
|
2486
2486
|
domain: "crm:E52_Time-Span".freeze,
|
2487
|
-
label:
|
2487
|
+
label: "had at least duration".freeze,
|
2488
2488
|
range: "crm:E54_Dimension".freeze,
|
2489
2489
|
type: "rdf:Property".freeze
|
2490
2490
|
property :P83i_was_minimum_duration_of,
|
2491
2491
|
domain: "crm:E54_Dimension".freeze,
|
2492
|
-
label:
|
2492
|
+
label: "was minimum duration of".freeze,
|
2493
2493
|
range: "crm:E52_Time-Span".freeze,
|
2494
2494
|
type: "rdf:Property".freeze
|
2495
2495
|
property :P84_had_at_most_duration,
|
@@ -2497,12 +2497,12 @@ It allows an E52 Time-Span to be associated with an E54 Dimension representing i
|
|
2497
2497
|
It allows an E52 Time-Span to be associated with an E54 Dimension representing it’s maximum duration \(i.e. it’s outer boundary\) independent from the actual beginning and end.
|
2498
2498
|
).freeze,
|
2499
2499
|
domain: "crm:E52_Time-Span".freeze,
|
2500
|
-
label:
|
2500
|
+
label: "had at most duration".freeze,
|
2501
2501
|
range: "crm:E54_Dimension".freeze,
|
2502
2502
|
type: "rdf:Property".freeze
|
2503
2503
|
property :P84i_was_maximum_duration_of,
|
2504
2504
|
domain: "crm:E54_Dimension".freeze,
|
2505
|
-
label: ["".freeze, "
|
2505
|
+
label: ["".freeze, "was maximum duration of".freeze],
|
2506
2506
|
range: "crm:E52_Time-Span".freeze,
|
2507
2507
|
type: "rdf:Property".freeze
|
2508
2508
|
property :P86_falls_within,
|
@@ -2510,12 +2510,12 @@ It allows an E52 Time-Span to be associated with an E54 Dimension representing i
|
|
2510
2510
|
This property supports the notion that a Time-Span’s temporal extent falls within the temporal extent of another Time-Span. It addresses temporal containment only, and no contextual link between the two instances of Time-Span is implied.
|
2511
2511
|
).freeze,
|
2512
2512
|
domain: "crm:E52_Time-Span".freeze,
|
2513
|
-
label:
|
2513
|
+
label: "falls within".freeze,
|
2514
2514
|
range: "crm:E52_Time-Span".freeze,
|
2515
2515
|
type: "rdf:Property".freeze
|
2516
2516
|
property :P86i_contains,
|
2517
2517
|
domain: "crm:E52_Time-Span".freeze,
|
2518
|
-
label:
|
2518
|
+
label: "contains".freeze,
|
2519
2519
|
range: "crm:E52_Time-Span".freeze,
|
2520
2520
|
type: "rdf:Property".freeze
|
2521
2521
|
property :P87_is_identified_by,
|
@@ -2523,13 +2523,13 @@ This property supports the notion that a Time-Span’s temporal extent falls wit
|
|
2523
2523
|
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
|
2524
2524
|
).freeze,
|
2525
2525
|
domain: "crm:E53_Place".freeze,
|
2526
|
-
label:
|
2526
|
+
label: "is identified by".freeze,
|
2527
2527
|
range: "crm:E44_Place_Appellation".freeze,
|
2528
2528
|
subPropertyOf: "crm:P1_is_identified_by".freeze,
|
2529
2529
|
type: "rdf:Property".freeze
|
2530
2530
|
property :P87i_identifies,
|
2531
2531
|
domain: "crm:E44_Place_Appellation".freeze,
|
2532
|
-
label:
|
2532
|
+
label: "identifies".freeze,
|
2533
2533
|
range: "crm:E53_Place".freeze,
|
2534
2534
|
subPropertyOf: "crm:P1i_identifies".freeze,
|
2535
2535
|
type: "rdf:Property".freeze
|
@@ -2538,12 +2538,12 @@ Examples of Place Appellations used to identify Places include instances of E48
|
|
2538
2538
|
It addresses spatial containment only, and does not imply any relationship between things or phenomena occupying these places.
|
2539
2539
|
).freeze,
|
2540
2540
|
domain: "crm:E53_Place".freeze,
|
2541
|
-
label:
|
2541
|
+
label: "falls within".freeze,
|
2542
2542
|
range: "crm:E53_Place".freeze,
|
2543
2543
|
type: "rdf:Property".freeze
|
2544
2544
|
property :P89i_contains,
|
2545
2545
|
domain: "crm:E53_Place".freeze,
|
2546
|
-
label:
|
2546
|
+
label: "contains".freeze,
|
2547
2547
|
range: "crm:E53_Place".freeze,
|
2548
2548
|
type: "rdf:Property".freeze
|
2549
2549
|
property :P8_took_place_on_or_within,
|
@@ -2553,42 +2553,42 @@ This property is in effect a special case of P7 took place at. It describes a pe
|
|
2553
2553
|
For example, the French and German armistice of 22 June 1940 was signed in the same railway carriage as the armistice of 11 November 1918.
|
2554
2554
|
).freeze,
|
2555
2555
|
domain: "crm:E4_Period".freeze,
|
2556
|
-
label:
|
2556
|
+
label: "took place on or within".freeze,
|
2557
2557
|
range: "crm:E18_Physical_Thing".freeze,
|
2558
2558
|
type: "rdf:Property".freeze
|
2559
2559
|
property :P8i_witnessed,
|
2560
2560
|
domain: "crm:E18_Physical_Thing".freeze,
|
2561
|
-
label:
|
2561
|
+
label: "witnessed".freeze,
|
2562
2562
|
range: "crm:E4_Period".freeze,
|
2563
2563
|
type: "rdf:Property".freeze
|
2564
2564
|
property :P90_has_value,
|
2565
2565
|
comment: %(This property allows an E54 Dimension to be approximated by an E60 Number primitive.).freeze,
|
2566
2566
|
domain: "crm:E54_Dimension".freeze,
|
2567
|
-
label:
|
2567
|
+
label: "has value".freeze,
|
2568
2568
|
range: "rdfs:Literal".freeze,
|
2569
2569
|
type: "rdf:Property".freeze
|
2570
2570
|
property :P91_has_unit,
|
2571
2571
|
comment: %(This property shows the type of unit an E54 Dimension was expressed in.).freeze,
|
2572
2572
|
domain: "crm:E54_Dimension".freeze,
|
2573
|
-
label:
|
2573
|
+
label: "has unit".freeze,
|
2574
2574
|
range: "crm:E58_Measurement_Unit".freeze,
|
2575
2575
|
type: "rdf:Property".freeze
|
2576
2576
|
property :P91i_is_unit_of,
|
2577
2577
|
domain: "crm:E58_Measurement_Unit".freeze,
|
2578
|
-
label:
|
2578
|
+
label: "is unit of".freeze,
|
2579
2579
|
range: "crm:E54_Dimension".freeze,
|
2580
2580
|
type: "rdf:Property".freeze
|
2581
2581
|
property :P92_brought_into_existence,
|
2582
2582
|
comment: %(This property allows an E63 Beginning of Existence event to be linked to the E77 Persistent Item brought into existence by it.
|
2583
2583
|
It allows a “start” to be attached to any Persistent Item being documented i.e. E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, E51 Contact Point and E55 Type).freeze,
|
2584
2584
|
domain: "crm:E63_Beginning_of_Existence".freeze,
|
2585
|
-
label:
|
2585
|
+
label: "brought into existence".freeze,
|
2586
2586
|
range: "crm:E77_Persistent_Item".freeze,
|
2587
2587
|
subPropertyOf: "crm:P12_occurred_in_the_presence_of".freeze,
|
2588
2588
|
type: "rdf:Property".freeze
|
2589
2589
|
property :P92i_was_brought_into_existence_by,
|
2590
2590
|
domain: "crm:E77_Persistent_Item".freeze,
|
2591
|
-
label:
|
2591
|
+
label: "was brought into existence by".freeze,
|
2592
2592
|
range: "crm:E63_Beginning_of_Existence".freeze,
|
2593
2593
|
subPropertyOf: "crm:P12i_was_present_at".freeze,
|
2594
2594
|
type: "rdf:Property".freeze
|
@@ -2598,13 +2598,13 @@ In the case of immaterial things, the E64 End of Existence is considered to take
|
|
2598
2598
|
This allows an “end” to be attached to any Persistent Item being documented i.e. E70 Thing, E72 Legal Object, E39 Actor, E41 Appellation, E51 Contact Point and E55 Type. For many Persistent Items we know the maximum life-span and can infer, that they must have ended to exist. We assume in that case an End of Existence, which may be as unnoticeable as forgetting the secret knowledge by the last representative of some indigenous nation.
|
2599
2599
|
).freeze,
|
2600
2600
|
domain: "crm:E64_End_of_Existence".freeze,
|
2601
|
-
label:
|
2601
|
+
label: "took out of existence".freeze,
|
2602
2602
|
range: "crm:E77_Persistent_Item".freeze,
|
2603
2603
|
subPropertyOf: "crm:P12_occurred_in_the_presence_of".freeze,
|
2604
2604
|
type: "rdf:Property".freeze
|
2605
2605
|
property :P93i_was_taken_out_of_existence_by,
|
2606
2606
|
domain: "crm:E77_Persistent_Item".freeze,
|
2607
|
-
label:
|
2607
|
+
label: "was taken out of existence by".freeze,
|
2608
2608
|
range: "crm:E64_End_of_Existence".freeze,
|
2609
2609
|
subPropertyOf: "crm:P12i_was_present_at".freeze,
|
2610
2610
|
type: "rdf:Property".freeze
|
@@ -2613,26 +2613,26 @@ This allows an “end” to be attached to any Persistent Item being documented
|
|
2613
2613
|
It represents the act of conceiving the intellectual content of the E28 Conceptual Object. It does not represent the act of creating the first physical carrier of the E28 Conceptual Object. As an example, this is the composition of a poem, not its commitment to paper.
|
2614
2614
|
).freeze,
|
2615
2615
|
domain: "crm:E65_Creation".freeze,
|
2616
|
-
label:
|
2616
|
+
label: "has created".freeze,
|
2617
2617
|
range: "crm:E28_Conceptual_Object".freeze,
|
2618
2618
|
subPropertyOf: "crm:P92_brought_into_existence".freeze,
|
2619
2619
|
type: "rdf:Property".freeze
|
2620
2620
|
property :P94i_was_created_by,
|
2621
2621
|
domain: "crm:E28_Conceptual_Object".freeze,
|
2622
|
-
label:
|
2622
|
+
label: "was created by".freeze,
|
2623
2623
|
range: "crm:E65_Creation".freeze,
|
2624
2624
|
subPropertyOf: "crm:P92i_was_brought_into_existence_by".freeze,
|
2625
2625
|
type: "rdf:Property".freeze
|
2626
2626
|
property :P95_has_formed,
|
2627
2627
|
comment: %(This property links the founding or E66 Formation for an E74 Group with the Group itself.).freeze,
|
2628
2628
|
domain: "crm:E66_Formation".freeze,
|
2629
|
-
label:
|
2629
|
+
label: "has formed".freeze,
|
2630
2630
|
range: "crm:E74_Group".freeze,
|
2631
2631
|
subPropertyOf: "crm:P92_brought_into_existence".freeze,
|
2632
2632
|
type: "rdf:Property".freeze
|
2633
2633
|
property :P95i_was_formed_by,
|
2634
2634
|
domain: "crm:E74_Group".freeze,
|
2635
|
-
label:
|
2635
|
+
label: "was formed by".freeze,
|
2636
2636
|
range: "crm:E66_Formation".freeze,
|
2637
2637
|
subPropertyOf: "crm:P92i_was_brought_into_existence_by".freeze,
|
2638
2638
|
type: "rdf:Property".freeze
|
@@ -2642,13 +2642,13 @@ It represents the act of conceiving the intellectual content of the E28 Conceptu
|
|
2642
2642
|
Note that biological fathers are not necessarily participants in the Birth \(see P97 from father \(was father for\)\). The Person being born is linked to the Birth with the property P98 brought into life \(was born\). This is not intended for use with general natural history material, only people. There is no explicit method for modelling conception and gestation except by using extensions. This is a sub-property of P11 had participant \(participated in\).
|
2643
2643
|
).freeze,
|
2644
2644
|
domain: "crm:E67_Birth".freeze,
|
2645
|
-
label:
|
2645
|
+
label: "by mother".freeze,
|
2646
2646
|
range: "crm:E21_Person".freeze,
|
2647
2647
|
subPropertyOf: "crm:P11_had_participant".freeze,
|
2648
2648
|
type: "rdf:Property".freeze
|
2649
2649
|
property :P96i_gave_birth,
|
2650
2650
|
domain: "crm:E21_Person".freeze,
|
2651
|
-
label:
|
2651
|
+
label: "gave birth".freeze,
|
2652
2652
|
range: "crm:E67_Birth".freeze,
|
2653
2653
|
subPropertyOf: "crm:P11i_participated_in".freeze,
|
2654
2654
|
type: "rdf:Property".freeze
|
@@ -2659,12 +2659,12 @@ This is not intended for use with general natural history material, only people.
|
|
2659
2659
|
A Birth event is normally \(but not always\) associated with one biological father.
|
2660
2660
|
).freeze,
|
2661
2661
|
domain: "crm:E67_Birth".freeze,
|
2662
|
-
label:
|
2662
|
+
label: "from father".freeze,
|
2663
2663
|
range: "crm:E21_Person".freeze,
|
2664
2664
|
type: "rdf:Property".freeze
|
2665
2665
|
property :P97i_was_father_for,
|
2666
2666
|
domain: "crm:E21_Person".freeze,
|
2667
|
-
label:
|
2667
|
+
label: "was father for".freeze,
|
2668
2668
|
range: "crm:E67_Birth".freeze,
|
2669
2669
|
type: "rdf:Property".freeze
|
2670
2670
|
property :P98_brought_into_life,
|
@@ -2672,26 +2672,26 @@ A Birth event is normally \(but not always\) associated with one biological fath
|
|
2672
2672
|
Twins, triplets etc. are brought into life by the same Birth event. This is not intended for use with general Natural History material, only people. There is no explicit method for modelling conception and gestation except by using extensions.
|
2673
2673
|
).freeze,
|
2674
2674
|
domain: "crm:E67_Birth".freeze,
|
2675
|
-
label:
|
2675
|
+
label: "brought into life".freeze,
|
2676
2676
|
range: "crm:E21_Person".freeze,
|
2677
2677
|
subPropertyOf: "crm:P92_brought_into_existence".freeze,
|
2678
2678
|
type: "rdf:Property".freeze
|
2679
2679
|
property :P98i_was_born,
|
2680
2680
|
domain: "crm:E21_Person".freeze,
|
2681
|
-
label:
|
2681
|
+
label: "was born".freeze,
|
2682
2682
|
range: "crm:E67_Birth".freeze,
|
2683
2683
|
subPropertyOf: "crm:P92i_was_brought_into_existence_by".freeze,
|
2684
2684
|
type: "rdf:Property".freeze
|
2685
2685
|
property :P99_dissolved,
|
2686
2686
|
comment: %(This property links the disbanding or E68 Dissolution of an E74 Group to the Group itself.).freeze,
|
2687
2687
|
domain: "crm:E68_Dissolution".freeze,
|
2688
|
-
label:
|
2688
|
+
label: "dissolved".freeze,
|
2689
2689
|
range: "crm:E74_Group".freeze,
|
2690
2690
|
subPropertyOf: ["crm:P11_had_participant".freeze, "crm:P93_took_out_of_existence".freeze],
|
2691
2691
|
type: "rdf:Property".freeze
|
2692
2692
|
property :P99i_was_dissolved_by,
|
2693
2693
|
domain: "crm:E74_Group".freeze,
|
2694
|
-
label:
|
2694
|
+
label: "was dissolved by".freeze,
|
2695
2695
|
range: "crm:E68_Dissolution".freeze,
|
2696
2696
|
subPropertyOf: ["crm:P11i_participated_in".freeze, "crm:P93i_was_taken_out_of_existence_by".freeze],
|
2697
2697
|
type: "rdf:Property".freeze
|
@@ -2699,13 +2699,13 @@ Twins, triplets etc. are brought into life by the same Birth event. This is not
|
|
2699
2699
|
comment: %(This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occupied by the former and which is defined by phenomena that form part of or are refinements of the phenomena that define the former.
|
2700
2700
|
).freeze,
|
2701
2701
|
domain: "crm:E4_Period".freeze,
|
2702
|
-
label:
|
2702
|
+
label: "consists of".freeze,
|
2703
2703
|
range: "crm:E4_Period".freeze,
|
2704
2704
|
subPropertyOf: "crm:P10i_contains".freeze,
|
2705
2705
|
type: "rdf:Property".freeze
|
2706
2706
|
property :P9i_forms_part_of,
|
2707
2707
|
domain: "crm:E4_Period".freeze,
|
2708
|
-
label:
|
2708
|
+
label: "forms part of".freeze,
|
2709
2709
|
range: "crm:E4_Period".freeze,
|
2710
2710
|
subPropertyOf: "crm:P10_falls_within".freeze,
|
2711
2711
|
type: "rdf:Property".freeze
|