http://www.cidoc-crm.org/cidoc-crm/E52_Time-Span
Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- from 12-17-1993 to 12-8-1996
- 14h30 - 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
In First Order Logic:
E52(x) ⊃ E1(x)
Instances of crm:E52_Time-Span can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class crm:E52_Time-Span | |||
| crm:P79_beginning_is_qualified_by | owl:DatatypeProperty | Scope note: This property qualifies the beginning of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) beginning is qualified by approximately (E62) In First Order Logic: P79 (x,y) ⊃ E52 (x) P79 (x,y) ⊃ E62(y) P79(x,y) ⊃ P3(x,y) | owl:Thing |
| crm:P80_end_is_qualified_by | owl:DatatypeProperty | Scope note: This property qualifies the end of an E52 Time-Span in some way. The nature of the qualification may be certainty, precision, source etc. Examples: - the time-span of the Holocene (E52) end is qualified by approximately (E62) In First Order Logic: P80(x,y) ⊃ E52(x) P80(x,y) ⊃ E62(y) P80(x,y) ⊃ P3(x,y) | owl:Thing |
| crm:P81_ongoing_throughout | owl:DatatypeProperty | Scope note: This property describes the minimum period of time covered by an E52 Time-Span. 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. Examples: - the time-span of the development of the CIDOC CRM (E52) ongoing throughout 1996-2002 (E61) In First Order Logic: P81 (x,y) ⊃ E52(x) P81 (x,y) ⊃ E61(y) | owl:Thing |
| crm:P82_at_some_time_within | owl:DatatypeProperty | Scope note: This property describes the maximum period of time within which an E52 Time-Span falls. 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. Examples: - the time-span of the development of the CIDOC CRM (E52) at some time within 1992-infinity (E61) In First Order Logic: P82 (x,y) ⊃ E52(x) P82 (x,y) ⊃ E61(y) | owl:Thing |
| crm:P164i_was_time-span_of | owl:ObjectProperty | crm:E93_Presence | |
| crm:P4i_is_time-span_of | owl:ObjectProperty | crm:E2_Temporal_Entity | |
| crm:P78_is_identified_by | owl:ObjectProperty | Scope note: This property identifies an E52 Time-Span using an E49Time Appellation. Examples: - the time span 1926 to 1988 (E52) is identified by "Showa" (Japanese time appellation) (E49) In First Order Logic: P78(x,y) ⊃ E52(x) P78(x,y) ⊃ E49(y) P78(x,y) ⊃ P1(x,y) | crm:E49_Time_Appellation |
| crm:P83_had_at_least_duration | owl:ObjectProperty | Scope note: This property describes the minimum length of time covered by an E52 Time-Span. 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. Examples: - the time span of the Battle of Issos 333 B.C.E. (E52) had at least duration Battle of Issos minimum duration (E54) has unit (P91) day (E58) has value (P90) 1 (E60) In First Order Logic: P83(x,y) ⊃ E52(x) P83(x,y) ⊃ E54(y) | crm:E54_Dimension |
| crm:P84_had_at_most_duration | owl:ObjectProperty | Scope note: This property describes the maximum length of time covered by an E52 Time-Span. 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. Examples: - the time span of the Battle of Issos 333 B.C.E. (E52) had at most duration Battle of Issos maximum duration (E54) has unit (P91) day (E58) has value (P90) 2 (E60) In First Order Logic: P84(x,y) ⊃ E52(x) P84(x,y) ⊃ E54(y) | crm:E54_Dimension |
| crm:P86_falls_within | owl:ObjectProperty | Scope note: This property describes the inclusion relationship between two instances of E52 Time-Span. 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. Examples: - the time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52) In First Order Logic: P86(x,y) ⊃ E52(x) P86(x,y) ⊃ E52(y) | crm:E52_Time-Span |
| crm:P86i_contains | owl:ObjectProperty | 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:E52_Time-Span a owl:Class ;
rdfs:label "E52 Time-Span"@en ;
rdfs:comment """Scope note:
This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration.
Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation.
Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known.
Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive.
Examples:
- 1961
- from 12-17-1993 to 12-8-1996
- 14h30 - 16h22 4th July 1945
- 9.30 am 1.1.1999 to 2.00 pm 1.1.1999
- duration of the Ming Dynasty
In First Order Logic:
E52(x) ⊃ E1(x)"""@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:maxCardinality "1"^^xsd:nonNegativeInteger ;
owl:onProperty crm:P83_had_at_least_duration ],
[ a owl:Restriction ;
owl:maxCardinality "1"^^xsd:nonNegativeInteger ;
owl:onProperty crm:P84_had_at_most_duration ],
[ a owl:Restriction ;
owl:onProperty crm:P4i_is_time-span_of ;
owl:someValuesFrom crm:E2_Temporal_Entity ],
crm:E1_CRM_Entity ;
owl:equivalentClass ecrm:E52_Time-Span ;
skos:notation "E52"^^xsd:string .