http://www.cidoc-crm.org/cidoc-crm/E14_Condition_Assessment
Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year's inspection of humidity damage to the frescos in the St. George chapel in our village
In First Order Logic:
E14(x) ⊃ E13(x)
Instances of crm:E14_Condition_Assessment can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class crm:E14_Condition_Assessment | |||
| crm:P34_concerned | owl:ObjectProperty | Scope note: This property identifies the E18 Physical Thing that was assessed during an E14 Condition Assessment activity. 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. Examples: - 1997 condition assessment of the silver collection (E14) concerned silver cup 232 (E22) In First Order Logic: P34(x,y) ⊃ E14(x) P34(x,y) ⊃ E18(y) P34(x,y) ⊃ P140(x,y) | crm:E18_Physical_Thing |
| crm:P35_has_identified | owl:ObjectProperty | Scope note: This property identifies the E3 Condition State that was observed in an E14 Condition Assessment activity. Examples: - 1997 condition assessment of silver cup 232 (E14) has identified oxidation traces were present in 1997 (E3) has type oxidation traces (E55) In First Order Logic: P35(x,y) ⊃E14(x) P35(x,y) ⊃ E3(y) P35(x,y) ⊃ P141(x,y) | crm:E3_Condition_State |
| From class crm:E13_Attribute_Assignment | |||
| crm:P140_assigned_attribute_to | owl:ObjectProperty | Scope note: This property indicates the item to which an attribute or relation is assigned. Examples: - February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned attribute to Martin Doerr's silver cup (E19) - 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned attribute to silver cup 232 (E19) In First Order Logic: P140(x,y) ⊃ E13(x) P140(x,y) ⊃ E1(y) | crm:E1_CRM_Entity |
| crm:P141_assigned | owl:ObjectProperty | Scope note: 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. Examples: - February 1997 Current Ownership Assessment of Martin Doerr's silver cup (E13) assigned Martin Doerr (E21) - 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned object identifier 232 | crm:E1_CRM_Entity |
| From class crm:E7_Activity | |||
| crm:P125_used_object_of_type | owl:ObjectProperty | Scope note: 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". Examples: - at the Battle of Agincourt (E7), the English archers used object of type long bow (E55) In First Order Logic: P125(x,y) ⊃ E7(x) P125(x,y) ⊃ E55(y) | crm:E55_Type |
| crm:P134_continued | owl:ObjectProperty | Scope note: 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. Examples: - the construction of the Kölner Dom (Cologne Cathedral) (E7), abandoned in the 15th century, was continued by construction in the 19th century adapting the initial plans so as to preserve the intended appearance (E7) In First Order Logic: P134(x,y) ⊃ E7(x) P134(x,y)⊃ E7(y) P134(x,y) ⊃ P15(x,y) | crm:E7_Activity |
| crm:P134i_was_continued_by | owl:ObjectProperty | crm:E7_Activity | |
| crm:P14_carried_out_by | owl:ObjectProperty | Scope note: This property describes the active participation of an E39 Actor in an E7 Activity. 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. Examples: - the painting of the Sistine Chapel (E7) carried out by Michaelangelo Buonaroti (E21) in the role of master craftsman (E55) In First Order Logic: P14 (x,y) ⊃ E7(x) P14 (x,y)⊃ E39(y) P14 (x,y) ⊃ P11(x,y) P14(x,y,z) ⊃ [P14(x,y) ∧ E55(z)] | owl:Thing |
| crm:P15_was_influenced_by | owl:ObjectProperty | Scope note: This is a high level property, which captures the relationship between an E7 Activity and anything that may have had some bearing upon it. The property has more specific sub properties. Examples: - the designing of the Sydney Harbour Bridge (E7) was influenced by the Tyne bridge (E22) FOL: P15 (x,y) ⊃ E7(x) P15 (x,y) ⊃ E1(y) | crm:E1_CRM_Entity |
| crm:P16_used_specific_object | owl:ObjectProperty | Scope note: This property describes the use of material or immaterial things in a way essential to the performance or the outcome of an E7 Activity. This property typically applies to tools, instruments, moulds, raw materials and items embedded in a product. It implies that the presence of the object in question was a necessary condition for the action. For example, the activity of writing this text required the use of a computer. An immaterial thing can be used if at least one of its carriers is present. For example, the software tools on a computer. 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. Examples: - the writing of this scope note (E7) used specific object Nicholas Crofts' computer (E22) mode of use Typing Tool; Storage Medium (E55) - the people of Iraq calling the place identified by TGN '7017998' (E7) used specific object "Quyunjig" (E44) mode of use Current; Vernacular (E55) FOL: P16 (x,y) ⊃ E7(x) P16 (x,y) ⊃ E70(y) P16 (x,y) ⊃ P12(x,y) P16 (x,y) ⊃ P15(x,y) P16(x,y,z) ⊃ [P16(x,y) ∧ E55(z)] | crm:E70_Thing |
| crm:P17_was_motivated_by | owl:ObjectProperty | Scope note: This property describes an item or items that are regarded as a reason for carrying out the E7 Activity. 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. Examples: - the resignation of the chief executive (E7) was motivated by the collapse of Swiss Air (E68). - the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69) FOL: P17(x,y) ⊃ E7(x) P17(x,y) ⊃ E1(y) P17 (x,y) ⊃ P15(x,y) | crm:E1_CRM_Entity |
| crm:P19_was_intended_use_of | owl:ObjectProperty | Scope note: This property relates an E7 Activity with objects created specifically for use in the activity. 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)). Examples: - Lady Diana Spencer's wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55) FOL: P19(x,y) ⊃ E7(x) P19(x,y) ⊃ E71(y) P19(x,y,z) ⊃ [P19(x,y) ∧ E55(z)] Properties: P19.1 mode of use: E55 Type | crm:E71_Man-Made_Thing |
| crm:P20_had_specific_purpose | owl:ObjectProperty | Scope note: This property identifies the relationship between a preparatory activity and the event it is intended to be preparation for. This includes activities, orders and other organisational actions, taken in preparation for other activities or events. 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. Examples: - Van Eyck's pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent altar piece (E12) In First Order Logic: P21(x,y) ⊃ E7(x) P21(x,y) ⊃ E55(y) | crm:E5_Event |
| crm:P21_had_general_purpose | owl:ObjectProperty | Scope note: This property describes an intentional relationship between an E7 Activity and some general goal or purpose. 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. Examples: - Van Eyck's pigment grinding (E7) had general purpose painting (E55) - the setting of trap 2742 on May 17th 1874 (E7) had general purpose Catching Moose (E55) (Activity type In First Order Logic: P21(x,y) ⊃ E7(x) P21(x,y) ⊃ E55(y) | crm:E55_Type |
| crm:P32_used_general_technique | owl:ObjectProperty | Scope note: This property identifies the technique or method that was employed in an activity. 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. Examples: - ornamentation of silver cup 113 (E11) used general technique gold-plating (E55) (Design or Procedure Type) | crm:E55_Type |
| crm:P33_used_specific_technique | owl:ObjectProperty | Scope note: This property identifies a specific instance of E29 Design or Procedure in order to carry out an instance of E7 Activity or parts of it. The property differs from P32 used general technique (was technique of) in that P33 refers to an instance of E29 Design or Procedure, which is a concrete information object in its own right rather than simply being a term or a method known by tradition. Typical examples would include intervention plans for conservation or the construction plans of a building Examples: - Ornamentation of silver cup 232 (E11) used specific technique 'Instructions for golden chase work by A N Other' (E29) - Rebuilding of Reichstag (E11) used specific technique Architectural plans by Foster and Partners (E29) In First Order Logic: P33(x,y) ⊃ E7(x) P33(x,y) ⊃ E29(y) P33(x,y) ⊃ P16(x,y) | crm:E29_Design_or_Procedure |
| From class crm:E5_Event | |||
| crm:P11_had_participant | owl:ObjectProperty | Scope note: This property describes the active or passive participation of instances of E39 Actors in an E5 Event. It connects the life-line of the related E39 Actor with the E53 Place and E50 Date of the event. The property implies that the Actor was involved in the event but does not imply any causal relationship. The subject of a portrait can be said to have participated in the creation of the portrait. Examples: - Napoleon (E21) participated in The Battle of Waterloo (E7) - Maria (E21) participated in Photographing of Maria (E7) In First Order Logic: P11(x,y) ⊃ E5(x) P11(x,y) ⊃ E39(y) P11(x,y) ⊃ P12(x,y) | crm:E39_Actor |
| crm:P12_occurred_in_the_presence_of | owl:ObjectProperty | Scope note: This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. It connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers. Examples: - Deckchair 42 (E19) was present at The sinking of the Titanic (E5) In First Order Logic: P12(x,y) ⊃ E5(x) P12(x,y) ⊃ E77(y) | crm:E77_Persistent_Item |
| crm:P20i_was_purpose_of | owl:ObjectProperty | crm:E7_Activity | |
| From class crm:E4_Period | |||
| crm:P158_occupied | owl:ObjectProperty | Scope note: This property associates an instance of E4 Period with the real that is phenomenal, 4 dimensional point set or volume in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period. This consists of the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event. Such interactions took place in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In case of phenomena spreading out over islands or other separated areas, the trajectories necessary for participants to travel between these areas are not regarded as part of the occupied spacetime volumes. Such instances of E4 Period occupy each a limited number of contiguous spacetime volumes, however there must not be a discontinuity in the total timespan covered by these spacetime volumes. The real spacetime volumes occupied by an instance of E4 Period must not be confused with declarations of spacetime approximating the real extent. In general, instances of E4 Period have fuzzy boundaries in spacetime. Therefore it cannot be verified, if two different instances of E4 Period occupy exactly the same spacetime volume. We therefore determine that a spacetime volume may only be occupied by one instance of E4 Period. | crm:E92_Spacetime_Volume |
| crm:P7_took_place_at | owl:ObjectProperty | Scope note: This property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period "Révolution française" can be said to have taken place in "France", the "Victorian" period, may be said to have taken place in "Britain" and its colonies, as well as other parts of Europe and north America. A period can take place at multiple locations. It is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. Describe in words. Examples - the period "Révolution française" (E4) took place at France (E53) In First Order Logic: P7(x,y) ⊃ E4(x) P7(x,y) ⊃ E53(y) | crm:E53_Place |
| crm:P8_took_place_on_or_within | owl:ObjectProperty | Scope note: This property describes the location of an instance of E4 Period with respect to an E19 Physical Object. P8 took place on or within (witnessed) is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156 occupies (is occupied by) to E18 Physical Thing. It describes a period that can be located with respect to the space defined by an E19 Physical Object such as a ship or a building. The precise geographical location of the object during the period in question may be unknown or unimportant. 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. Examples: - the coronation of Queen Elisabeth II (E7) took place on or within Westminster Abbey (E19) In First Order Logic: P8(x,y) ⊃ E4(x) P8(x,y) ⊃ E18(y) | crm:E18_Physical_Thing |
| crm:P9_consists_of | owl:ObjectProperty | Scope note: This property associates an instance of E4 Period with another instance of E4 Period that is defined by a subset of the phenomena that define the former. Therefore the spacetime volume of the latter must fall within the spacetime volume of the former. Examples: - Cretan Bronze Age (E4) consists of Middle Minoan (E4) In First Order Logic: P9(x,y) ⊃ E4(x) P9(x,y) ⊃ E4(y) P9(x,y) ⊃ P10(y,x) | crm:E4_Period |
| crm:P9i_forms_part_of | owl:ObjectProperty | crm:E4_Period | |
| From class crm:E2_Temporal_Entity | |||
| crm:P114_is_equal_in_time_to | owl:ObjectProperty | Scope note: This symmetric property allows the instances of E2 Temporal Entity with the same E52 Time-Span to be equated. This property is only necessary if the time span is unknown (otherwise the equivalence can be calculated). This property is the same as the "equal" relationship of Allen’s temporal logic (Allen, 1983, pp. 832-843). Examples: - the destruction of the Villa Justinian Tempus (E6) is equal in time to the death of Maximus Venderus (E69) In First Order Logic: P114(x,y) ⊃ E2(x) P114(x,y) ⊃ E2(y) P114(x,y) ⊃ P114(y,x) | crm:E2_Temporal_Entity |
| crm:P115_finishes | owl:ObjectProperty | Scope note: This property allows the ending point for a E2 Temporal Entity to be situated by reference to the ending point of another temporal entity of longer duration. This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "finishes / finished-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). Examples: - Late Bronze Age (E4) finishes Bronze Age (E4) In First Order Logic: P115(x,y) ⊃ E2(x) P115(x,y) ⊃ E2(y) | crm:E2_Temporal_Entity |
| crm:P115i_is_finished_by | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P116_starts | owl:ObjectProperty | Scope note: This property allows the starting point for a E2 Temporal Entity to be situated by reference to the starting point of another temporal entity of longer duration. This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "starts / started-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). Examples: - Early Bronze Age (E4) starts Bronze Age (E4) In First Order Logic: P116(x,y) ⊃ E2(x) P116(x,y) ⊃ E2(y) | crm:E2_Temporal_Entity |
| crm:P116i_is_started_by | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P117_occurs_during | owl:ObjectProperty | Scope note: This property allows the entire E52 Time-Span of an E2 Temporal Entity to be situated within the Time-Span of another temporal entity that starts before and ends after the included temporal entity. This property is only necessary if the time span is unknown (otherwise the relationship can be calculated). This property is the same as the "during / includes" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). Examples: - Middle Saxon period (E4) occurs during Saxon period (E4) In First Order Logic: P117(x,y) ⊃ E2(x) P117(x,y) ⊃ E2(y) | crm:E2_Temporal_Entity |
| crm:P117i_includes | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P118_overlaps_in_time_with | owl:ObjectProperty | Scope note: This property identifies an overlap between the instances of E52 Time-Span of two instances of E2 Temporal Entity. It implies a temporal order between the two entities: if A overlaps in time B, then A must start before B, and B must end after A. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). This property is the same as the "overlaps / overlapped-by" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). Examples: - the Iron Age (E4) overlaps in time with the Roman period (E4) In First Order Logic: P118(x,y) ⊃ E2(x) P118(x,y) ⊃ E2(y) | crm:E2_Temporal_Entity |
| crm:P118i_is_overlapped_in_time_by | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P119_meets_in_time_with | owl:ObjectProperty | Scope note: This property indicates that one E2 Temporal Entity immediately follows another. It implies a particular order between the two entities: if A meets in time with B, then A must precede B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). This property is the same as the "meets / met-by" relationships of Allen's temporal logic (Allen, 1983, pp. 832-843). Examples: - Early Saxon Period (E4) meets in time with Middle Saxon Period (E4) | crm:E2_Temporal_Entity |
| crm:P119i_is_met_in_time_by | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P120_occurs_before | owl:ObjectProperty | Scope note: This property identifies the relative chronological sequence of two temporal entities. It implies that a temporal gap exists between the end of A and the start of B. This property is only necessary if the relevant time spans are unknown (otherwise the relationship can be calculated). This property is the same as the "before / after" relationships of Allen’s temporal logic (Allen, 1983, pp. 832-843). Examples: - Early Bronze Age (E4) occurs before Late Bronze age (E4) In First Order Logic: P120(x,y) ⊃ E2(x) P120(x,y) ⊃ E2(y) | crm:E2_Temporal_Entity |
| crm:P120i_occurs_after | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P4_has_time-span | owl:ObjectProperty | Scope note: This property describes the temporal confinement of an instance of an E2 Temporal Entity. 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. Examples: - the Yalta Conference (E7) has time-span Yalta Conference time-span (E52) In First Order Logic: P4(x,y) ⊃ E2(x) P4(x,y) ⊃ E52(y) | crm:E52_Time-Span |
| From class crm:E1_CRM_Entity | |||
| crm:P3_has_note | owl:DatatypeProperty | Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" (E62) has type Condition (E55) In First Order Logic: P3(x,y) ⊃ E1(x) P3(x,y) ⊃ E62(y) P3(x,y,z) ⊃ [P3(x,y) ∧ E55(z)] Properties: P3.1 has type: E55 Type | owl:Thing |
| crm:P129i_is_subject_of | owl:ObjectProperty | crm:E89_Propositional_Object | |
| crm:P136i_supported_type_creation | owl:ObjectProperty | crm:E83_Type_Creation | |
| crm:P137_exemplifies | owl:ObjectProperty | Scope note: This property allows an item to be declared as a particular example of an E55 Type or taxon The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the Type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the Type Creation (E83) itself, but selected in a later phase. Examples: - Object BM000098044 of the Clayton Herbarium (E20) exemplifies Spigelia marilandica (L.) L. (E55) in the taxonomic role lectotype In First Order Logic: P137(x,y) ⊃ E1(x) P137(x,y) ⊃ E55(y) P137(x,y,z) ⊃ [P137(x,y) ∧ E55(z)] P137(x,y) ⊃ P2(x,y) Properties: P137.1 in the taxonomic role: E55 Type | crm:E55_Type |
| crm:P138i_has_representation | owl:ObjectProperty | crm:E36_Visual_Item | |
| crm:P140i_was_attributed_by | owl:ObjectProperty | crm:E13_Attribute_Assignment | |
| crm:P141i_was_assigned_by | owl:ObjectProperty | crm:E13_Attribute_Assignment | |
| crm:P15i_influenced | owl:ObjectProperty | crm:E7_Activity | |
| crm:P17i_motivated | owl:ObjectProperty | crm:E7_Activity | |
| crm:P1_is_identified_by | owl:ObjectProperty | Scope note: This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment. Examples: - the capital of Italy (E53) is identified by "Rome" (E48) - text 25014-32 (E33) is identified by "The Decline and Fall of the Roman Empire" (E35) In First Order Logic: P1(x,y) ⊃ E1(x) P1(x,y) ⊃ E41(y) | crm:E41_Appellation |
| crm:P2_has_type | owl:ObjectProperty | Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. 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. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) In First Order Logic: P2(x,y) ⊃ E1(x) P2(x,y) ⊃ E55(y) | crm:E55_Type |
| crm:P39i_was_measured_by | owl:ObjectProperty | crm:E16_Measurement | |
| crm:P41i_was_classified_by | owl:ObjectProperty | crm:E17_Type_Assignment | |
| crm:P62i_is_depicted_by | owl:ObjectProperty | crm:E24_Physical_Man-Made_Thing | |
| crm:P67i_is_referred_to_by | owl:ObjectProperty | crm:E89_Propositional_Object | |
| crm:P70i_is_documented_in | owl:ObjectProperty | crm:E31_Document | |
| crm:P71i_is_listed_in | owl:ObjectProperty | crm:E32_Authority_Document | |
| From class crm:E92_Spacetime_Volume | |||
| crm:P10_falls_within | owl:ObjectProperty | Scope note: This property associates an instance of E4 Period with another instance of E4 Period that falls within the spacetime volumes occupied by the latter. 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 nature. Examples: - the Great Plague (E4) falls within The Gothic period (E4) | crm:E92_Spacetime_Volume |
| crm:P10i_contains | owl:ObjectProperty | crm:E92_Spacetime_Volume | |
| crm:P132_overlaps_with | owl:ObjectProperty | Scope note: This symmetric property allows instances of E4 Period that overlap both temporally and spatially to be related, i,e. they share some spatio-temporal extent. This property does not imply any ordering or sequence between the two periods, either spatial or temporal. Examples: - the "Urnfield" period (E4) overlaps with the "Hallstatt" period (E4) In First Order Logic: P132(x,y) ⊃ E92(x) P132(x,y) ⊃ E92(y) P132(x,y) ⊃ P132(y,x) | crm:E92_Spacetime_Volume |
| crm:P133_is_separated_from | owl:ObjectProperty | Scope note: This symmetric property allows instances of E4 Period that do not overlap both temporally and spatially, to be related i,e. they do not share any spatio-temporal extent. This property does not imply any ordering or sequence between the two periods either spatial or temporal. Examples: - the "Hallstatt" period (E4) is separated from the "La Tène" era (E4) In First Order Logic: P133(x,y) ⊃ E92(x) P133(x,y) ⊃ E92(y) P133(x,y) ⊃ P133(y,x) | crm:E92_Spacetime_Volume |
| crm:P160_has_temporal_projection | owl:ObjectProperty | Scope note: This property describes the temporal projection of an instance of an E92 Spacetime Volume. The property P4 has time-span is the same as P160 has temporal projection if it is used to document an instance of E4 Period or any subclass of it. Example: In First Order Logic: P160(x,y) ⊃ E92(x) P160(x,y)⊃ E52(y) | crm:E52_Time-Span |
| crm:P161_has_spatial_projection | owl:ObjectProperty | Scope note: This property associates an instance of a E92 Spacetime Volume with an instance of E53 Place that is the result of the spatial projection of the instance of a E92 Spacetime Volume on a reference space. In general there can be more than one useful reference space to describe the spatial projection of a spacetime volume, such as that of a battle ship versus that of the seafloor. Therefore the projection is not unique. This is part of the fully developed path that is shortcut by P7took place at (witnessed. The more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. Example In First Order Logic: P161(x,y) ⊃ E92(x) P161(x,y) ⊃ E53(y) | crm:E53_Place |
| crm:P166i_had_presence | owl:ObjectProperty | crm:E93_Presence | |
| From class owl:Thing | |||
| crm:P14i_performed | owl:ObjectProperty | crm:E7_Activity | |
| crm:P165i_is_incorporated_in | owl:ObjectProperty | owl:Thing | |
| crm:P22i_acquired_title_through | owl:InverseFunctionalProperty | crm:E8_Acquisition | |
| crm:P23i_surrendered_title_through | owl:ObjectProperty | crm:E8_Acquisition | |
| crm:P28i_surrendered_custody_through | owl:ObjectProperty | crm:E10_Transfer_of_Custody | |
| crm:P29i_received_custody_through | owl:ObjectProperty | crm:E10_Transfer_of_Custody | |
| crm:P48_has_preferred_identifier | owl:ObjectProperty | Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. 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. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier "OXCMS:2001.1.32" (E42) In First Order Logic: P48(x,y) ⊃ E1(x) P48(x,y) ⊃ E42(y) P48(x,y) ⊃ P1(x,y) | crm:E42_Identifier |
| crm:P50i_is_current_keeper_of | owl:ObjectProperty | crm:E18_Physical_Thing | |
| crm:P52i_is_current_owner_of | owl:ObjectProperty | crm:E18_Physical_Thing | |
@prefix crm: <http://www.cidoc-crm.org/cidoc-crm/> .
@prefix ecrm: <http://erlangen-crm.org/current/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
crm:E14_Condition_Assessment a owl:Class ;
rdfs:label "E14 Condition Assessment"@en ;
rdfs:comment """Scope note:
This class describes the act of assessing the state of preservation of an object during a particular period.
The condition assessment may be carried out by inspection, measurement or through historical research. This class is used to document circumstances of the respective assessment that may be relevant to interpret its quality at a later stage, or to continue research on related documents.
Examples:
- last year's inspection of humidity damage to the frescos in the St. George chapel in our village
In First Order Logic:
E14(x) ⊃ E13(x)"""@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:onProperty crm:P34_concerned ;
owl:someValuesFrom crm:E18_Physical_Thing ],
[ a owl:Restriction ;
owl:minCardinality "1"^^xsd:nonNegativeInteger ;
owl:onProperty crm:P35_has_identified ],
crm:E13_Attribute_Assignment ;
owl:equivalentClass ecrm:E14_Condition_Assessment ;
skos:notation "E14"^^xsd:string .