Concept Search
Showing 2710 results:
P78 is identified by
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.2.2
P78 is identified by
Quantification: many to many (0,n,0,n)
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)
Type: Property
Belongs to version: Version 5.0.2
P78 is identified by
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.2
P78 is identified by
Quantification: many to many (0,n,0,n)
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)
Type: Property
Belongs to version: Version 4.1
P78 is identified by
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.0
P78 is identified by
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.2.1
P78 is identified by
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 5.1.2
P79 beginning is qualified by
Quantification: many to one (0,1,0,n)
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)
Type: Property
Belongs to version: Version 5.0.1
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.1
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
Scope note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the certainty, precision, sources etc. of its beginning. Such notesmay also be used to elaborate arguments about constraints or to give explanations of alternatives.
Examples:
- the time-span of the Holocene (E52) beginning is qualified by by “The formal definition and dating of the GSSP (GlobalStratotype Section andPoint) for the base of the Holocene using the Greenland NGRIP ice core, and selected auxiliary records” (E62) (Walker et al 2009)
Type: Property
Belongs to version: version 7.1
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.2
P79 beginning is qualified by
Quantification: many to one (0,1,0,n)
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)
Type: Property
Belongs to version: Version 5.0.2
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2
P79 beginning is qualified by
Quantification: many to one (0,1,0,n)
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)
Type: Property
Belongs to version: Version 4.1
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.0
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.1
P79 beginning is qualified by
Quantification: many to one (0,1,0,n)
Scope note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the certainty, precision, sources etc. of its beginning. Such notes may also be used to elaborate arguments about constraints or to give explanations of alternatives.
Examples:
- The time-span of the Holocene (E52) beginning is qualified by “The formal definition and dating of the GSSP (GlobalStratotype Section and Point) for the base of the Holocene using the Greenland NGRIP ice core, and selected auxiliary records” (E62). (Walker et al., 2009)
Type: Property
Belongs to version: version 7.1.1
P79 beginning is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 5.1.2
P8 took place on or within
Quantification: many to many (0,n:0,n)
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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 6.2.2
P8 took place on or within
Quantification: many to many (0,n,0,n)
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 short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition.
This property is in effect a special case of P7 took place at. 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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 5.0.2
P8 took place on or within
Quantification: many to many (0,n:0,n)
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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 6.2
P8 took place on or within
Quantification: many to many (0,n,0,n)
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 short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition.
This property is in effect a special case of P7 took place at. 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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 4.1
P8 took place on or within
Quantification: many to many (0,n:0,n)
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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 6.2.1
P8 took place on or within
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the location of an instance of E4 Period with respect to an instance of E19 Physical Object.
This property is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156i is occupied by 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 Elizabeth II (E7) took place on or within Westminster Abbey (E18). (Strong, 2005)
Type: Property
Belongs to version: version 7.1.1
P8 took place on or within
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the location of an instance of E4 Period with respect to an E18 Physical Thing. P8 took place on or within (witnessed) is a short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition. This property is in effect a special case of P7 took place at. It describes a period that can be located with respect to the space defined by an E18 Physical Thing 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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 6.0
P8 took place on or within
Quantification: many to many (0,n,0,n)
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 short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition.
This property is in effect a special case of P7 took place at. 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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 5.0.1
P8 took place on or within
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the location of an instance of E4 Period with respect to an E18 Physical Thing. P8 took place on or within (witnessed) is a short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition. This property is in effect a special case of P7 took place at. It describes a period that can be located with respect to the space defined by an E18 Physical Thing 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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 6.1
P8 took place on or within
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the location of an instance of E4 Period with respect to an instance of E19 Physical Object.
This property is a shortcut of the more fully developed path from E4 Period through P7 took place at, E53 Place, P156i 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.E
Examples:
- the coronation of Queen Elizabeth II (E7) took place on or within Westminster Abbey (E19) (Strong, 2005)
Type: Property
Belongs to version: version 7.1
P8 took place on or within
Quantification: many to many (0,n:0,n)
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 short-cut of a path defining a E53 Place with respect to the geometry of an object. cf. E46 Section Definition.
This property is in effect a special case of P7 took place at. 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 Elizabeth II (E7) took place on or within Westminster Abbey (E19)
Type: Property
Belongs to version: Version 5.1.2
P80 end is qualified by
Quantification: many to one (0,1,0,n)
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)
Type: Property
Belongs to version: Version 5.0.1
P80 end is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.1
P80 end is qualified by
Quantification: many to one (0,1:0,n)
Scope note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the end of this time-span concerning certainty, precision, sources etc. This property may also be used to describe arguments constraining possible dates and to distinguish reasons for alternative dates.
Examples:
- the time-span of the Holocene (E52) end is qualified by approximately (E62) (Walker et al, 2009)
Type: Property
Belongs to version: version 7.1
P80 end is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.2
P80 end is qualified by
Quantification: many to one (0,1,0,n)
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)
Type: Property
Belongs to version: Version 5.0.2
P80 end is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2
P80 end is qualified by
Quantification: many to one (0,1,0,n)
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)
Type: Property
Belongs to version: Version 4.1
P80 end is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.0
P80 end is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.1
P80 end is qualified by
Quantification: many to one (0,1,0,n)
Scope note:
This property associates an instance of E52 Time-Span with a note detailing the scholarly or scientific opinions and justifications about the end of this time-span concerning certainty, precision, sources etc. This property may also be used to describe arguments constraining possible dates and to distinguish reasons for alternative dates.
Examples:
- The time-span of the Holocene (E52) end is qualified by “still ongoing” (E62). (Walker et al., 2009)
Type: Property
Belongs to version: version 7.1.1
P80 end is qualified by
Quantification: many to one (0,1:0,n)
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)
Type: Property
Belongs to version: Version 5.1.2
P81 ongoing throughout
Quantification: many to one,necessary (1,1,0,n)
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. it’s 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)
Type: Property
Belongs to version: Version 5.0.1
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.1
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
Scope note:
This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC 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 CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including all these extents will be the best estimate. This should be taken into account for information integration.
Examples:
- the time-span of the development of the CIDOC CRM (E52) ongoing throughout 1996-2020 (E61)
- The Time-Span of the Thirty Years War (E52) ongoing throughout May 23, 1618AD until October 24, 1648AD (E61) (Bonney, 2014)
- The time-span of the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) (E52) ongoing throughout 2181BC - 2160BC (E61) (Reid, 1993)
[This is the minimal common agreement of two conflicting dates: James Henry Breasted dates the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) from 2475BC to 2160BC in his _Ancient Records (first published in 1906), volume 1, sections 58–75. Ian Shaw dates it from 2181BC to 2125BC in his _Oxford History of Ancient Egypt (published in 2000), pp. 479–483]
Type: Property
Belongs to version: version 7.1
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.2
P81 ongoing throughout
Quantification: many to one,necessary (1,1,0,n)
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)
Type: Property
Belongs to version: Version 5.0.2
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2
P81 ongoing throughout
Quantification: many to one,necessary (1,1,0,n)
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. it’s 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)
Type: Property
Belongs to version: Version 4.1
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.0
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.1
P81 ongoing throughout
Quantification: many to one,necessary (1,n,0,n)
Scope note:
This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC 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 CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including all these extents will be the best estimate. This should be taken into account for information integration.
Examples:
- The time-span of the development of the CIDOC CRM (E52) ongoing throughout “1996-2003” (E61). (Doerr, 2003)
- The Time-Span of the Thirty Years War (E52) ongoing throughout “23rd May 1618 AD until 24th October 1648 AD” (E61). (Bonney, 2014)
- The time-span of the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) (E52) ongoing throughout “2181 BC – 2160 BC” (E61). (Reid, 1993)
[This is the minimal common agreement of two conflicting dates: James Henry Breasted dates the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) from 2475BC to 2160BC in his Ancient Records (first published in 1906), volume 1, sections 58–75 (Breasted, 1906). Ian Shaw dates it from 2181BC to 2125BC in his Oxford History of Ancient Egypt (published in 2000), pp. 479–483 (Shaw, 2000).]
Type: Property
Belongs to version: version 7.1.1
P81 ongoing throughout
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 5.1.2
P82 at some time within
Quantification: many to one,necessary (1,1,0,n)
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. it’s 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)
Type: Property
Belongs to version: Version 5.0.1
P82 at some time within
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.1
P82 at some time within
Quantification: many to many, necessary (1,n:0,n)
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 CIDOC 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 CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of all these extents will be the best estimate. This should be taken into account for information integration.
Examples:
- the time-span of the development of the CIDOC CRM (E52)at some time within 1992-infinity (E61) ICOM/CIDOC Documentation Standards Group, 2000)
- The Time-Span of the Battle in the Teutoburg Forest (E52) at some time withinSeptember 9CE (E61) (Andrews, 1977)
- The time-Span of the death of Tut Ankh Amun (E52) at some time withinDecember 1324 BC to February 1323 BC (E61) (Murdoch, 2003)
- The time-span of the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) (E52) at some time within2475BC -2125BC (E61) (Reid, 1993)
Type: Property
Belongs to version: version 7.1
P82 at some time within
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.2
P82 at some time within
Quantification: many to one,necessary (1,1,0,n)
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)
Type: Property
Belongs to version: Version 5.0.2
P82 at some time within
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2
P82 at some time within
Quantification: many to one,necessary (1,1,0,n)
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. it’s 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)
Type: Property
Belongs to version: Version 4.1
P82 at some time within
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.0
P82 at some time within
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 6.2.1
P82 at some time within
Quantification: many to many,necessary (1,n,0,n)
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 CIDOC 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 CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of all these extents will be the best estimate. This should be taken into account for information integration.
Examples:
- The time-span of the development of the CIDOC CRM (E52) at some time within “1992-infinity” (E61). (Doerr, 2003)
- The Time-Span of the Battle in the Teutoburg Forest (E52) at some time within “September 9 CE” (E61). (Andrews & Kesteven, 1977)
- The time-Span of the death of Tut Ankh Amun (E52) at some time within “December 1324 BC to February 1323 BC” (E61). (Murdoch, 2003)
- The time-span of the First Intermediate Period of Ancient Egypt (7th to 10th dynasty) (E52) at some time within “2475BC - 2125BC” (E61). (Reid, 1993)
Type: Property
Belongs to version: version 7.1.1
P82 at some time within
Quantification: many to one, necessary (1,1:0,n)
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)
Type: Property
Belongs to version: Version 5.1.2
P83 had at least duration
Quantification: one to one (1,1,1,1)
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 day (E58) has value 1 (E60)
Type: Property
Belongs to version: Version 5.0.1
P83 had at least duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.1
P83 had at least duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.2.2
P83 had at least duration
Quantification: one to one (1,1,1,1)
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)
Type: Property
Belongs to version: Version 5.0.2
P83 had at least duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.2
P83 had at least duration
Quantification: one to one (1,1,1,1)
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 day (E58) has value 1 (E60)
Type: Property
Belongs to version: Version 4.1
P83 had at least duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.0
P83 had at least duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.2.1
P83 had at least duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 5.1.2
P84 had at most duration
Quantification: one to one (1,1,1,1)
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 day (E58) has value 2 (E60)
Type: Property
Belongs to version: Version 5.0.1
P84 had at most duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.1
P84 had at most duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.2.2
P84 had at most duration
Quantification: one to one (1,1,1,1)
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)
Type: Property
Belongs to version: Version 5.0.2
P84 had at most duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.2
P84 had at most duration
Quantification: one to one (1,1,1,1)
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 day (E58) has value 2 (E60)
Type: Property
Belongs to version: Version 4.1
P84 had at most duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.0
P84 had at most duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 6.2.1
P84 had at most duration
Quantification: one to one (1,1:1,1)
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)
Type: Property
Belongs to version: Version 5.1.2
P86 falls within
Quantification: many to many (0,n,0,n)
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)
Type: Property
Belongs to version: Version 5.0.1
P86 falls within
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.1
P86 falls within
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the inclusion relationship between two instances of E52 Time-Span.
This property supports the notion that the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 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) (Riley, 2009), (Robinson, 2000)
Type: Property
Belongs to version: version 7.1
P86 falls within
Quantification: many to many (0,n:0,n)
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.
This property is transitive.
This property is transitive.
Examples:
- the time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52)
Type: Property
Belongs to version: Version 6.2.2
P86 falls within
Quantification: many to many (0,n,0,n)
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)
Type: Property
Belongs to version: Version 5.0.2
P86 falls within
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.2
P86 falls within
Quantification: many to many (0,n,0,n)
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)
Type: Property
Belongs to version: Version 4.1
P86 falls within
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 6.0
P86 falls within
Quantification: many to many (0,n:0,n)
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.
This property is transitive.
This property is transitive.
Examples:
- the time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52)
Type: Property
Belongs to version: Version 6.2.1
P86 falls within
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the inclusion relationship between two instances of E52 Time-Span.
This property supports the notion that the temporal extent of an instance of E52 Time-Span falls within the temporal extent of another instance of E52 Time-Span. It addresses temporal containment only, and no contextual link between the two instances of E52 Time-Span is implied. This property is transitive.
Examples:
- The time-span of the Apollo 11 moon mission (E52) falls within the time-span of the reign of Queen Elizabeth II (E52). (Riley, 2009) (Robinson, 2000)
Type: Property
Belongs to version: version 7.1.1
P86 falls within
Quantification: many to many (0,n:0,n)
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)
Type: Property
Belongs to version: Version 5.1.2
P87 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples:
- of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
- Examples:
- the location of the Duke of Wellington’s House (E53) is identified by No 1 London (E45)
Type: Property
Belongs to version: Version 5.0.1
P87 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 6.1
P87 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 6.2.2
P87 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples:
- of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
- Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 5.0.2
P87 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 6.2
P87 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples:
- of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
- Examples:
- the location of the Duke of Wellington’s House (E53) is identified by No 1 London (E45)
Type: Property
Belongs to version: Version 4.1
P87 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 6.0
P87 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 6.2.1
P87 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E53 Place using an E44 Place Appellation.
Examples of Place Appellations used to identify Places include instances of E48 Place Name, addresses, E47 Spatial Coordinates etc.
Examples:
- the location of the Duke of Wellington’s House (E53) is identified by “No 1 London” (E45)
Type: Property
Belongs to version: Version 5.1.2