http://www.cidoc-crm.org/cidoc-crm/E3_Condition_State
Scope note:
This class comprises the states of objects characterised by a certain condition over a time-span.
An instance of this class describes the prevailing physical condition of any material object or
feature during a specific E52 Time Span. In general, the time-span for which a certain
condition can be asserted may be shorter than the real time-span, for which this condition held.
The nature of that condition can be described using P2 has type. For example, the E3
Condition State "condition of the SS Great Britain between 22 September 1846 and 27 August
1847" can be characterized as E55 Type "wrecked".
Examples:
- the "Amber Room" in Tsarskoje Selo being completely reconstructed from summer 2003 until now
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946
- the state of my turkey in the oven at 14:30 on 25 December, 2002 (P2 has type: E55 Type "still not cooked")
In First Order Logic:
E3(x) ⊃ E2(x)
Instances of crm:E3_Condition_State can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class crm:E3_Condition_State | |||
| crm:P35i_was_identified_by | owl:ObjectProperty | crm:E14_Condition_Assessment | |
| crm:P44i_is_condition_of | owl:ObjectProperty | crm:E18_Physical_Thing | |
| crm:P5_consists_of | owl:ObjectProperty | Scope note: This property describes the decomposition of an E3 Condition State into discrete, subsidiary states. 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. Examples: - The Condition State of the ruined Parthenon (E3) consists of the bombarded state after the explosion of a Venetian shell in 1687 (E3) In First Order Logic: P5(x,y) ⊃ E3(x) P5(x,y) ⊃ E3(y) | crm:E3_Condition_State |
| crm:P5i_forms_part_of | owl:ObjectProperty | crm:E3_Condition_State | |
| 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 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:E3_Condition_State a owl:Class ;
rdfs:label "E3 Condition State"@en ;
rdfs:comment """Scope note:
This class comprises the states of objects characterised by a certain condition over a time-span.
An instance of this class describes the prevailing physical condition of any material object or
feature during a specific E52 Time Span. In general, the time-span for which a certain
condition can be asserted may be shorter than the real time-span, for which this condition held.
The nature of that condition can be described using P2 has type. For example, the E3
Condition State "condition of the SS Great Britain between 22 September 1846 and 27 August
1847" can be characterized as E55 Type "wrecked".
Examples:
- the "Amber Room" in Tsarskoje Selo being completely reconstructed from summer 2003 until now
- the Peterhof Palace near Saint Petersburg being in ruins from 1944 – 1946
- the state of my turkey in the oven at 14:30 on 25 December, 2002 (P2 has type: E55 Type "still not cooked")
In First Order Logic:
E3(x) ⊃ E2(x)"""@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:onProperty crm:P44i_is_condition_of ;
owl:someValuesFrom crm:E18_Physical_Thing ],
crm:E2_Temporal_Entity ;
owl:equivalentClass ecrm:E3_Condition_State ;
skos:notation "E3"^^xsd:string .