Concept Search

Quantification: many to many (0,n,0,n)
Scope note:

This property describes an item or items that are regarded as a reason for carrying out the E7 Activity.

For example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre.

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)

Quantification: many to many (0,n:0,n)
Scope note:

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)

Quantification: many to many (0,n:0,n)
Scope note:

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)

Quantification: many to many (0,n,0,n)
Scope note:

This property describes an item or items that are regarded as a reason for carrying out the instance of E7 Activity.

For example, the discovery of a large hoard of treasure may call for a celebration, an order from headquarters can start a military manoeuvre.

• The resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• The coronation of Elizabeth II (E7) was motivated by the death of George VI (E69). (Strong, 2005)

Quantification: many to many (0,n:0,n)
Scope note:

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)

Quantification: many to many (0,n,0,n)
Scope note:

This property describes an item or items that are regarded as a reason for carrying out the E7 Activity.

For example, the discovery of a large hoard of treasure may call for a celebration, an order from head quarters can start a military manoeuvre.

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)

Quantification: many to many (0,n:0,n)
Scope note:

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69)

Quantification: many to many (0,n:0,n)
Scope note:

• the resignation of the chief executive (E7) was motivated by the collapse of SwissAir (E68).
• the coronation of Elizabeth II (E7) was motivated by the death of George VI (E69) (Strong, 2005)

Quantification: many to one (0,1:0,n)
Scope note:

This property associates an instance of E61 Time Primitive with the instance of E52 Time-Span that constitutes the interpretation of the terms of the time primitive as an extent in absolute, real time.

The quantification allows several instances of E61 Time Primitive that are each expressed in different syntactic forms, to define the same instance of E52 Time Span.

Subproperty of: E41Appellation. P1i identifies: E1CRM Entity

• (1800/1/1 0:00:00 –1899/31/12 23:59:59) (E61) defines timeThe 19th century (E52)
• (1968/1/1 –2018/1/1) (E61) defines time“1968/1/1–2018/1/1” (E52) [an arbitrary time-span during which the Saint Titus reliquary was present in the Saint Titus Church in Heraklion, Crete]

Scope note:

This property associates an instance of E61 Time Primitive with the instance of E52 Time Span it defines. 

Quantification: many to one (0,1,0,n)
Scope note:

This property associates an instance of E61 Time Primitive with the instance of E52 Time-Span that constitutes the interpretation of the terms of the time primitive as an extent in absolute, real time.

The quantification allows several instances of E61 Time Primitive that are each expressed in different syntactic forms, to define the same instance of E52 Time Span.

• “1800/1/1 0:00:00 – 1899/31/12 23:59:59” (E61) defines time the 19th century (E52).
• “1968/1/1 – 2018/1/1” (E61) defines time 1968/1/1 – 2018/1/1 (E52). [an arbitrary time-span during which the Saint Titus reliquary was present in the Saint Titus Church in Heraklion, Crete]

Quantification: many to many (0,n:0,n)
Scope note:

This property describes the maximum spatial extent within which an instance of E53 Place falls. Since instances of E53 Places may not have precisely known spatial extents, the CIDOC CRM supports statements about maximum spatial extents of instances of E53 Place. This property allows an instance of an instance of E53 Place’s maximum spatial extent (i.e., its outer boundary) to be assigned an instance of E94 Space Primitive value.

This property is a shortcut of the fully developed path E53 Place, P89 falls within, E53 Place, P168 place is defined by, E94 Space Primitive through a declarative Place that is not explicitly documented, to a Space Primitive: declarative places are defined in CRMgeo (Doerr and Hiebel 2013).

• the spatial extent of the Acropolis of Athens (E53) is at some place within POLYGON ((37.969172 23.720787, 37.973122 23.721495 37.972741 23.728994, 37.969299 23.729735, 37.969172 23.720787)) (E94)

Scope note:

This property describes the maximum spatial extent within which an E53 Place falls. Since instances of E53 Places may not have precisely known spatial extents, the CRM supports statements about maximum spatial extents of E53 Places. This property allows an instance of an E53 Places’s maximum spatial extent (i.e. its outer boundary) to be assigned an E94 Space Primitive value.
P171 at some place within is a shortcut of the fully developed path E53 Place P89 falls within E53 Place P168 place is defined by E94 Space Primitive  through a not represented declarative Place as defined in CRMgeo (Doerr and Hiebel 2013) to a Space Primitive.

• the spatial extent of the Acropolis of Athens (E53) is at some place within POLYGON ((37.969172 23.720787, 37.973122 23.721495 37.972741 23.728994, 37.969299 23.729735, 37.969172 23.720787)) (E94)

Quantification: many to many (0,n,0,n)
Scope note:

This property describes the maximum spatial extent within which an instance of E53 Place falls. Since instances of E53 Places may not have precisely known spatial extents, the CIDOC CRM supports statements about maximum spatial extents of instances of E53 Place. This property allows an instance of E53 Place’s maximum spatial extent (i.e., its outer boundary) to be assigned an instance of E94 Space Primitive value.

This property is a shortcut of the fully developed path from E53 Place, P89 falls within, E53 Place, P168 place is defined by to E94 Space Primitive through a declarative Place that is not explicitly documented, to a Space Primitive: declarative places are defined in CRMgeo (Doerr and Hiebel 2013).

• The spatial extent of the Acropolis of Athens (E53) at some place within POLYGON ((37.969172 23.720787, 37.973122 23.721495 37.972741 23.728994, 37.969299 23.729735, 37.969172 23.720787)) (E94).

Quantification: many to many (0,n:0,n)
Scope note:

This property describes a minimum spatial extent which is contained within an E53 Place. Since instances of E53 Place may not have precisely known spatial extents, the CRM supports statements about minimum spatial extents of instances of E53 Place. This property allows an instance of E53 Places’s minimum spatial extent (i.e., its inner boundary or a point being within a Place) to be assigned an instance of E94 Space Primitive value.
This property is a shortcut of the fully developed path:  E53 Place, P89i contains, E53 Place, P168 place is defined by, E94 Space Primitive

• the spatial extent of the Acropolis of Athens (E53) contains POINT (37.971431 23.725947) (E94)

Scope note:

This property describes a minimum spatial extent which is contained within an E53 Place. Since instances of E53 Place may not have precisely known spatial extents, the CRM supports statements about minimum spatial extents of instances of E53 Place. This property allows an instance of E53 Places’s minimum spatial extent (i.e. its inner boundary or a point being within a Place) to be assigned an E94 Space Primitive value.
This property is a shortcut of the fully developed path:  E53 Place, P89i contains, E53 Place, P168 place is defined by, E94 Space Primitive

• the spatial extent of the Acropolis of Athens (E53) contains POINT (37.971431 23.725947) (E94)

Quantification: many to many (0,n,0,n)
Scope note:

This property describes a minimum spatial extent which is contained within an instance of E53 Place. Since instances of E53 Place may not have precisely known spatial extents, the CIDOC CRM supports statements about minimum spatial extents of instances of E53 Place. This property allows an instance of E53 Places’s minimum spatial extent (i.e., its inner boundary or a point being within a Place) to be assigned an instance of E94 Space Primitive value.

This property is a shortcut of the fully developed path from E53 Place, P89i contains, E53 Place, P168 place is defined by to E94 Space Primitive

• The spatial extent of the Acropolis of Athens (E53) contains POINT (37.971431 23.725947) (E94).

Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bend is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to the disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during,  overlapped by}

Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B

Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B

• The legendary run from Marathon to Athens 490BC (E7) starts before or with the end ofThe Battle of Marathon 490BC (E7)

Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bend is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to the disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during,  overlapped by}

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^start ≤ B^end is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to the disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, met-by, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by}.

Figure 8: Temporal entity A starts before or with the end of temporal entity B. Here A is longer than B

Figure 9: Temporal entity A starts before or with the end of temporal entity B. Here A is shorter than B

• The legendary run from Marathon to Athens 490BC (E7) starts before or with the end of The Battle of Marathon 490BC (E7).

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. 
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart < Bend is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983] :{before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during,  overlapped by}

Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities This property is not transitive. 

Figure 3: Temporal entityA starts before the end of temporal entity B. Here A is longer than B

Figure 4: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B

• The settling activity of the city of Assur (Ashur)(E7) starts before the end ofThe Tenth Dynasty of Egypt. (E4) [There are some 200 -300 years differences in the chronology of the First Intermediate Period, and Assur is dated to "about 2500 BC”](Pedersen, 1986)

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity. 
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart < Bend is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983] :{before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during,  overlapped by}

Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities

Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^start < B^end is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finishes, finished-by, equals, during, overlapped by}

Typically, this property is a consequence of a known influence of some event on another event or activity, such as a novel written by someone being continued by someone else, or the knowledge of a defeat on a distant battlefield causing people to end their ongoing activities. This property is not transitive.

Figure 10: Temporal entity A starts before the end of temporal entity B. Here A is longer than B

Figure 11: Temporal entity A starts before the end of temporal entity B. Here A is shorter than B

• The settling activity of the city of Assur (Ashur) (E7) starts before the end of The Tenth Dynasty of Egypt (E4). [There are some 200 - 300 years differences in the chronology of the First Intermediate Period, and Assur is dated to about 2500 BC”.] (Pedersén, 1986)

|P174(x,y) ⇒ E2(x), P174(x,y) ⇒ E2(y), P174(x,y) ⇒ P173(x,y)|many to many (0,n,0,n)|

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^start ≤ B^start is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, started-by, contains, finished-by, equals}

In a model with fuzzy borders, this property will not be transitive.

Figure 12: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B

Figure 13: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B

• The production of the scarab seal found in Poros in a context of LMIIIB (E12) starts after or with the start of Tutankhamun period (1332-1323 B.C) (E4). [The scarab stamp seal found in Poros was associated with finds dated to the LMIIIB period. The seal is dated to the Tutankhamun period or later because it belongs to the scarabs of type “nh.s n Jmn”: During Akhenaten period, the production of this type of scarab seal stopped (the name of Amun is not referred to during his reign). Therefore, the scarab cannot have been produced before the Tutankhamun period and is probably a later production] (Karetsou, 2000)
• The production of the cylindrical seal of the first Dynasty of Babylon found in Tholos B in Platanos (E12) starts after or with the start of the Hammurabi period of the kingdom (E4). [Of the cylindrical seal of the first Dynasty of Babylon found in tholos B in Platanos believed to connect king Hammurabi with the MM I period. Specifically, although the finding is believed to have been found in a MM I layer, it contained material from the MM III/YM I period. Therefore, the seal may be from the Hammurabi period or, it may be from a later period.] (Walberg, 1992.)

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, starts, started-by, contains, finished-by, equals}

In a model with fuzzy borders, this property will not be transitive.

Figure 5: Temporal entity A starts before or with the start of temporal entity B. Here A is longer than B

Figure 6: Temporal entity A starts before or with the start of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart ≤ Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, starts, started-by, contains, finished-by, equals}

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^start < B^start is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, contains, finished-by}. This property is transitive.

Figure 14: Temporal entity A starts before the start of temporal entity B. Here A is longer than B

Figure 15: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart < Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, contains, finished-by}

This property is transitive.

Figure 7: Temporal entity A starts before the start of temporal entity B. Here A is longer than B

Figure 8: Temporal entity A starts before the start of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity starts definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Astart < Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, contains, finished-by}

Quantification: many to many,necessary (1,n,0,n)
Scope note:

This property associates an instance of E13 Attribute Assignment with the type of property or relation that this assignment maintains to hold between the item to which it assigns an attribute and the attribute itself. Note that the properties defined by the CIDOC CRM also constitute instances of E55 Type themselves. The direction of the assigned property type is understood to be from the attributed item (the range of property P140 assigned attribute to) to the attribute item (the range of the property P141 assigned). More than one property type may be assigned to hold between two items.

A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.

• Examples
• The Current Ownership Assessment of Martin Doerr’s silver cup February 1997 (E13) assigned property type P52 has former or current owner (is former or current keeper of) (E55). (fictitious)
• 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property type P48 has preferred identifier (is preferred identifier of) (E55). (fictitious)
• The examination of MS Sinai Greek 418 (E13) assigned property type binding structure type (E55). [‘binding structure type’ refers to a property, external to the CIDOC CRM, which connects a book (E22) to the type of its binding structure (E55)] (Honey & Pickwoad, 2010)
• The condition assessment of the endband cores of MS Sinai Greek 418 (E14) assigned property type damage (E55.) [‘damage’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like an endband core (E22) to the type of damage (E55) it shows] (Honey & Pickwoad, 2010)
• The condition assessment of the cover of MS Sinai Greek 418 (E14) assigned property type quality (E55). [‘quality’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like a book cover (E22) to its quality (E55)] (Honey and Pickwoad, 2010)

Quantification: many to many, necessary (1,n:0,n)
Scope note:

This property associates an instance of E13 Attribute Assignment with the type of property or relation that this assignment maintains to hold between the item to which it assigns an attribute and the attribute itself. Note that the properties defined by the CIDOC CRM also constitute instances of E55 Type themselves. The direction of the assigned property type is understood to be from the attributed item (the range of property P140 assigned attribute to) to the attribute item (the range of the property P141 assigned). More than one property type may be assigned to hold between two items.

A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.
 

•  February 1997 Current Ownership Assessment of Martin Doerr’s silver cup (E13) assigned property type P52 has former or current owner (is former or current keeper of) (E55)
• 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property type P48 has preferred identifier (is preferred identifier of) (E55)
• the examination of MS Sinai Greek 418 (E13) assigned property type binding structure type (E55) [‘binding structure type’ refers to a property, external to the CIDOC CRM, which connects a book (E22) to the type of its binding structure (E55)] (Honey and Pickwoad, 2010)
• the condition assessment of the endband cores of MS Sinai Greek 418 (E14) assigned property type damage (E55) [‘damage’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like an endband core (E22) to the type of damage (E55) it shows] (Honey and Pickwoad, 2010)
• the condition assessment of the cover of MS Sinai Greek 418 (E14) assigned property type quality (E55) [‘quality’ refers to a property, external to the CIDOC CRM, which connects an instance of a physical thing like a book cover (E22) to its quality (E55)] (Honey and Pickwoad, 2010)
   

Quantification: many to many, necessary (1,n:0,n)
Scope note:

This property associates an instance of E13 Attribute Assignment with the type of property or relation that this assignment maintains to hold between the item to which it assigns an attribute and the attribute itself. Note that the properties defined by the CIDOC CRM also constitute instances of E55 Type themselves. The direction of the assigned property type is understood to be from the attributed item (the range of property P140 assigned attribute to) to the attribute item (the range of the property P141 assigned). More than one property type may be assigned to hold between two items. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.

• February 1997 Current Ownership Assessment of Martin Doerr’s silver cup (E13) assigned property type P52 has former or current owner (is former or current keeper of) (E55)
• 01 June 1997 Identifier Assignment of the silver cup donated by Martin Doerr (E15) assigned property type P48 has preferred identifier (is preferred identifier of) (E55)

Scope note:

This property allows the ending time point of an E7 Activity to be situated during the time extent of another Activity.
ends within (Aend < Bend  & Aend > Bstart)

This property can be expressed using a set of possible Allen operators such as: {meets, overlaps, starts, during, finishes, finished-by, equals}. The temporal primitive is implied when the ending point of the domain activity is after (or at) the starting point of the range and before (or at) the end of the range. Time inequality is considered to be a non-overlap over the fuzzy boundary zones, and serves the representation of time imprecision. [There must not be an overlap between the fuzzy boundary zones.]

Scope note:

This property allows the ending time point of an E7 Activity to be situated after the ending time point of another Activity.This is part of a set of temporal primitives.
This property can be expressed using a set of possible Allen operators such as: {meets, overlaps, starts, finishes, finished-by, equals}. This property is implied when the ending point of the domain activity is after (or at) the end of the range. Time equality is considered as an overlap over fuzzy boundary zones, and serves the interpretation of time imprecision.

Quantification: many to many (1,n,0,n)
Scope note:

This property establishes the relationship between an instance of E96 Purchase and the instance of E97 Monetary Amount that forms the compensation for the transaction. The monetary amount agreed upon may change in the course of the purchase activity.

• The sale of Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” 30^th March 1987 (E96) had sales price Christies’ hammer price for “Still Life: Vase with Fifteen Sunflowers” (E97).
• The purchase of 10 okka of nails by the captain A. Syrmas on 18^th September 1895 (E96) had sales price 20 piastre (grosi) (E97). (Syrmas, 1896)

Quantification: many to many (0,n:0,n)
Scope note:

This property establishes the relationship between an instance of E96 Purchase and the instance of E97 Monetary Amount that forms the compensation for the transaction. The monetary amount agreed upon may change in the course of the purchase activity.

• the sale of Vincent van Gogh’s “Vase with Fifteen Sunflowers” on 1987/03/30 (E96)had sales priceChristies’ hammer price for “Vase with Fifteen Sunflowers” (E97).
• the purchase of 10 okka of nails by the captain A. Syrmas on 18/9/1895(E96)had sales price 20 piastre (grosi) (E97)

Quantification: many to many (0,n:0,n)
Scope note:

This property establishes the relationship between an instance of E96 Purchase and the instance of E97 Monetary Amount that forms the compensation for the transaction.

• The sale of Vincent van Gogh’s “Vase with Fifteen Sunflowers” on 1987/03/30 (E96) had sales price Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97)

Quantification: many to one,necessary (1,1,0,n)
Scope note:

This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in.

• Christie’s hammer price for Vincent van Gogh’s “Still Life: Vase with Fifteen Sunflowers” in London on 30^th March 1987 (E97) has currency British Pounds (E98).

Quantification: many to one, necessary (1,1:0,n)
Scope note:

This property establishes the relationship between an instance of E97 Monetary Amount and the instance of E98 Currency that it is measured in.

• Christie' s hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98).

Scope note:

 This property establishes the relationship between an instance of E97 Monetary Amount and the currency that it is measured in.

• Christies’ hammer price for “Vase with Fifteen Sunflowers” (E97) has currency British Pounds (E98)

Scope note:

This property establishes the relationship between an instance of E97 Monetary Amount and the amount of currency that it consists of.

• Christies hammer price for “Vase with Fifteen Sunflowers” (E97) has amount 24,750,000 (E60)

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^end ≤ B^start is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets}.

Figure 16: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B

Figure 17: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets}

Figure 9: Temporal entity A ends before or with the start of temporal entity B. Here A is longer than B

Figure 10: Temporal entity A ends before or with the start of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bstart is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets}

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^end < B^start is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to the following Allen temporal relation (Allen, 1983) : {before}.

This property is transitive.

Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B

Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B

• Gisle taking office as Bishop of Linköping 1139 AD (E7) ends before the start of The Guta saga composition (E65). (Peel, 1999)
• Troy VII (E4) ends before the start of Troy VIII (E4). [uninhabited for some 200 years]

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend < Bstart  is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before}

This property is transitive.

Figure 18: Temporal entity A ends before the start of temporal entity B. Here A is longer than B

Figure 19: Temporal entity A ends before the start of temporal entity B. Here A is shorter than B

• Gisle taking office as Bishop of Linköping 1139 AD (E7) ends before the start of The Guta saga composition (E65) (Peel, 1999)
• Troy VII(E4) ends before the start of Troy VIII (E4) [uninhabited for some 200 years]

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the start of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend < Bstart  is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before}

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^end ≤ B^end is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, finished by, start, equals, during, finishes}.

Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B

Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bend   is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations Allen, 1983]: {before, meets, overlaps, finished by, start, equals, during, finishes}

Figure 20: Temporal entity A ends before or with the end of temporal entity B. Here A is longer than B

Figure 21: Temporal entity A ends before or with the end of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends before or simultaneously with the end of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend ≤ Bend   is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, finished by, start, equals, during, finishes}

Quantification: many to many (0,n,0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity.

In other words, if A = [A^start, A^end] and B = [B^start, B^end], we mean A^end < B^end is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations (Allen, 1983): {before, meets, overlaps, starts, during}.

This property is transitive.

Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B

Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend < Bend   is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, starts, during}

This property is transitive.

Figure 22: Temporal entity A ends before the end of temporal entity B. Here A is longer than B

Figure 23: Temporal entity A ends before the end of temporal entity B. Here A is shorter than B

Quantification: many to many (0,n:0,n)
Scope note:

This property specifies that the temporal extent of the domain instance A of E2 Temporal Entity ends definitely before the end of the temporal extent of the range instance B of E2 Temporal Entity.
In other words, if A = [Astart, Aend] and B = [Bstart, Bend], we mean Aend < Bend   is true.

This property is part of the set of temporal primitives P173 – P176, P182 – P185.

This property corresponds to a disjunction (logical OR) of the following Allen temporal relations [Allen, 1983]: {before, meets, overlaps, starts, during}

Quantification: many to many (0,n,0,n)
Scope note:

This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces.

• The production activity of the Volkswagen factory related to the “Standard limousine Type II” during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99). (Rieger, 2013)

Quantification: many to many (0,n:0,n)
Scope note:

This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces.

• The production activity of the Volkswagen factory during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99) (Rieger, 2013)

Quantification: many to many (0,n:0,n)
Scope note:

This property associates an instance of E12 Production with the instance of E99 Production Type, that is, the type of the things it produces.

• The production activity of the Volkswagen factory during 1949-1953 (E12) produced thing of product type Volkswagen Type 11 (Beetle) (E99). 

Quantification: one to many (1,n,1,1)
Scope note:

This property associates an instance of E99 Product Type with an instance of E29 Design or Procedure that completely determines the production of instances of E18 Physical Thing. The resulting instances of E18 Physical Thing are considered exemplars of this instance of E99 Product Type when the process specified is correctly executed. Note that the respective instance of E29 Design or Procedure may not necessarily be fixed in a written/graphical form, and may require the use of tools or models unique to the product type. The same instance of E99 Product Type may be associated with several variant plans.

• Volkswagen Type 11 (Beetle) (E99) has production plan the production plans for Volkswagen Type 11 (Beetle) (E29). (Rieger, 2013)

Quantification: one to many (0,n:0,1)
Scope note:

This property associates an instance of E99 Product Type with an instance of E29 Design or Procedure that completely determines the production of instances of E18 Physical Thing. The resulting instances of E18 Physical Thing are considered exemplars of this instance of E99 Product Type when the process specified is correctly executed. Note that the respective instance of E29 Design or Procedure may not necessarily be fixed in a written/graphical form, and may require the use of tools or models unique to the product type. The same instance of E99 Product Type may be associated with several variant plans.

• the production plans (E29) for Volkswagen Type 11 (Beetle) (E99) (Rieger, 2013)

Quantification: one to many (0,n:0,1)
Scope note:

This property associates an instance of E99 Product Type with an instance of E29 Design or Procedure that completely determines the production of instances of E18 Physical Thing. The resulting instances of E18 Physical Thing are considered exemplars of this instance of E99 Product Type when the process specified is correctly executed. Note that the respective instance of E29 Design or Procedure may not necessarily be fixed in a written/graphical form, and may require the use of tools or models unique to the product type. The same E99 Product Type may be associated with several variant plans.

• the production plans (E29) for Volkswagen Type 11 (Beetle) (E99)

Quantification: one to many (1,n,1,1)
Scope note:

This property associates an instance of E99 Product Type with an instance of E19 Physical Object that is needed for the production of an instance of E18 Physical Thing. When the process of production is correctly executed in accordance with the plan and using the specified instance of E19 Physical Object, the resulting instance of E18 Physical Thing is considered an exemplar of this instance of E99 Product Type. The instance of E19 Physical Object may bear distinct features that are transformed into characteristic features of the resulting instance of E18 Physical Thing. Examples include models and moulds.

• Volkswagen Type 11 (Beetle) (E99) requires production tool the luggage compartment lid mould for the Volkswagen Type 11 (Beetle) (E22). [See thumbnail image of the luggage compartment lid: https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Type_1_(Auto_classique_St._Lazare_%2710).jpg/220px-Volkswagen_Type_1_(Auto_classique_St._Lazare_%2710).jpg)] (Rieger, 2013)

Quantification: one to many (0,n:0,1)
Scope note:

This property associates an instance of E99 Product Type with an instance of E19 Physical Object that is needed for the production of an instance of E18 Physical Thing. When the process of production is correctly executed in accordance with the plan and using the specified instance of E19 Physical Object, the resulting instance of E18 Physical Thing is considered an exemplar of this instance of E99 Product Type. The instance of E19 Physical Object may bear distinct features that are transformed into characteristic features of the resulting instance of E18 Physical Thing. Examples include models and moulds.

• the luggage compartment lid mould (E19) for the Volkswagen Type 11 (Beetle) (E99)|(https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Ty…) (Rieger, 2013)

Quantification: one to many (0,n:0,1)
Scope note:

This property associates an instance of E99 Product Type with an instance of E19 Physical Object that is needed for the production of an instance of E18 Physical Thing. When the process of production is correctly executed in accordance with the plan and using the specified instance of E19 Physical Object, the resulting instance of E18 Physical Thing is considered an exemplar of this instance of E99 Product Type. The instance of E19 Physical Object may bear distinct features that are transformed into characteristic features of the resulting instance of E18 Physical Thing. Examples include models and moulds.

• the luggage compartment lid mould (E19) for the Volkswagen Type 11 (Beetle) (E99)|(https://upload.wikimedia.org/wikipedia/commons/thumb/b/b5/Volkswagen_Ty…)

Quantification: many to many (0,n,0,n)
Scope note:

This property associates an instance of E53 Place with another instance of E53 Place, which is defined in the same reference space, and which is used to approximate the former. The property does not necessarily state the quality or accuracy of this approximation, but rather indicates the use of the first instance of place to approximate the second.

In common documentation practice, find or encounter spots e.g., in archaeology, botany or zoology are often related to the closest village, river or other named place without detailing the relation, e.g., if it is located within the village or in a certain distance of the specified place. In this case the stated “phenomenal” place found in the documentation can be seen as approximation of the actual encounter spot without more specific knowledge.

In more recent documentation often point coordinate information is provided that originates from GPS measurements or georeferencing from a map. This point coordinate information does not state the actual place of the encounter spot but tries to approximate it with a “declarative” place. The accuracy depends on the methodology used when creating the coordinates. It may be dependent on technical limitations like GPS accuracy but also on the method where the GPS location is taken in relation to the measured feature. If the methodology is known a maximum deviation from the measured point can be calculated and the encounter spot or feature may be related to the resulting circle using an instance of P171 at some place within.

This property is not transitive.

• [40°31'17.9N 21°15'48.3E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://sws.geonames.org/735927]
• [40°31'00.1N 21°16'00.1E] (E53) approximates Kastoria, Greece, TGN ID: 7010880 (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from http://vocab.getty.edu/page/tgn/7010880]
• [40°04'60.0N 22°21'00.0E] (E53) approximates Mount Olympus National Park, Greece (E53). [The approximating declarative place with point shape is defined in terms of coordinates taken from https://www.geonames.org/6941814]

Quantification: many to many, necessary (1,n:0,n)
Scope note:

This property associates an instance of E53 Place with another instance of E53 Place, which is defined in the same reference space, and which is used to approximate the former. The property does not necessarily state the quality or accuracy of this approximation, but rather indicates the use of the first instance of place to approximate the second.

In common documentation practice, find or encounter spots e.g., in archaeology, botany or zoology are often related to the closest village, river or other named place without detailing the relation, e.g., if it is located within the village or in a certain distance of the specified place. In this case the stated “phenomenal” place found in the documentation can be seen as approximation of the actual encounter spot without more specific knowledge.

In more recent documentationoften point coordinate information is provided that originates from GPS measurements or georeferencing from a map. This point coordinate information does not state the actual place of the encounter spot but tries to approximate it with a “declarative” place. The accuracy depends on the methodology used when creating the coordinates. It may be dependent on technical limitations like GPS accuracy but also on the method where the GPS location is taken in relation to the measured feature. If the methodology isknown a maximum deviation from the measured point can be calculated and the encounter spot or feature may be related to the resulting circle using an instance of P171 at some place within.This property is not transitive.

• [40°31'17.9"N 21°15'48.3"E] approximatesKastoria, Greece, TGN ID: 7010880. (coordinates from https://sws.geonames.org/735927)

• [40°31'00.1"N 21°16'00.1"E] approximatesKastoria, Greece, TGN ID: 7010880. (coordinates from http://vocab.getty.edu/page/tgn/7010880)

• [40°04'60.0"N 22°21'00.0"E] approximatesMount Olympus National Park, Greece (coordinates from https://www.geonames.org/6941814)

Quantification: many to many, necessary (1,n:0,n)
Scope note:

• This property associates an instance of EXX Intention to Apply an activity plan with the actors intending it.

• “A Parliament regarding a law as being decided”

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n,0,n)
Scope note:

This property relates an E7 Activity with objects created specifically for use in the activity.

This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n,0,n)
Scope note:

This property relates an E7 Activity with objects created specifically for use in the activity.

This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n,0,n)
Scope note:

This property relates an instance of E7 Activity with instances of E71 Human-Made Thing, created specifically for use in the activity.

This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55). (Daly, 1981)

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n,0,n)
Scope note:

This property relates an E7 Activity with objects created specifically for use in the activity.

This is distinct from the intended use of an item in some general type of activity such as the book of common prayer which was intended for use in Church of England services (see P101 had as general use (was use of)).

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55)

Quantification: many to many (0,n:0,n)
Scope note:

• Lady Diana Spencer’s wedding dress (E71) was made for Wedding of Prince Charles and Lady Diana Spencer (E7) mode of use To Be Worn (E55) (Daly, 1981)

Quantification: many to many (0,n,0,n)
Scope note:

This property associates an instance of E90 Symbolic Object with a complete, identifying representation of its content in the form of an instance of E62 String.

This property only applies to instances of E90 Symbolic Object that can be represented completely in this form. The representation may be more specific than the symbolic level defining the identity condition of the represented. This depends on the type of the symbolic object represented. For instance, if a name has type Modern Greek character sequence, it may be represented in a loss-free Latin transcription, meaning however the sequence of Greek letters.

As another example, if the represented object has type English words sequence, American English or British English spelling variants may be chosen to represent the English word colour without defining a different symbolic object. If a name has type European traditional name, no particular string may define its content.

• The materials description of the painting (E33) has symbolic content “Oil, French Watercolors on Paper, Graphite and Ink on Canvas, with an Oak frame.” (E62).
• The title of Einstein’s 1915 text (E35) has symbolic content “Relativity, the Special and the General Theory” (E62). (Einstein, 2001)
• The story of Little Red Riding Hood (E33) has symbolic content “Once upon a time there lived in a certain village.” (E62). (Lang, 1965)
• The inscription on Rijksmuseum object SK-A-1601 (E34) has symbolic content “B” (E62). [reference: https://www.rijksmuseum.nl/en/collection/SK-A-1601/catalogue-entry (accessed 10^th April 2021)]

Quantification: many to many (0,n:0,n)
Scope note:

This property associates an instance of E90 Symbolic Object with a complete, identifying representation of its content in the form of an instance of E62 String.

This property only applies to instances of E90 Symbolic Object that can be represented completely in this form. The representation may be more specific than the symbolic level defining the identity condition of the represented. This depends on the type of the symbolic object represented. For instance, if a name has type "Modern Greek character sequence", it may be represented in a loss-free Latin transcription, meaning however the sequence of Greek letters.

As another example, if the represented object has type "English words sequence", American English or British English spelling variants may be chosen to represent the English word "colour" without defining a different symbolic object. If a name has type "European traditional name", no particular string may define its content.

• The materials description (E33) of the painting has symbolic content“Oil, French Watercolors on Paper, Graphite and Ink on Canvas, with an Oak frame.”
• The title (E35) of Einstein’s 1915 text has symbolic content“Relativity, the Special and the General Theory” (Einstein, 2001)
• The story of Little Red Riding Hood (E33) has symbolic content“Once upon a time there lived in a certain village.” (Lang, 1965)
• The inscription (E34) on Rijksmuseum object SK-A-1601 has symbolic content“B” (Cohen 1997)

Scope note:

This property associates an Intention to Apply with the externalisation of this intention (Expression) in a document.

• The Tate Archives disaster planning document (E31 Document) expresses the intention of undertaking certain actions (E?? Intention to Apply) to save the collection in case of the Thames flooding.

Quantification: one to one (1,1,1,1)
Scope note:

This property describes the length of time covered by an instance of E52 Time-Span. It allows an instance of E52 Time-Span to be associated with an instance of E54 Dimension representing duration independent from the actual beginning and end. Indeterminacy of the duration value can be expressed by assigning a numerical interval to the property P90 has value of E54 Dimension.

• The time span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of Issos duration (E54). (Howard, 2012)

Quantification: one to one (1,1:1,1)
Scope note:

This property describes the length of time covered by an instance of E52 Time-Span. It allows an instance of E52 Time-Span to be associated with an instance of E54 Dimension representing duration independent from the actual beginning and end. Indeterminacyof the duration value can be expressed by assigning a numerical interval to the property P90 has valueof E54 Dimension.

• the time span of the Battle of Issos 333 B.C.E. (E52) had durationBattle of Issos duration (E54) (Howard, 2012)

Quantification: many to many (0,n:0,n)
Scope note:

This property associates an instance of EXX Intention to Apply with the time constraint foreseen by the intending party for the actual application of the planned activities. The intending party may vary the time constraint over time. In case a newly set time constraint narrows down a previously set time constraint, one may regard both constraints as being simultaneously true and consistent. In case the newly set time constraint exceeds the previous one (typically delaying the foreseen time of application), we may talk about a modification of the overall intention to apply.  This modification should be regarded as an intention in its own right, but being part of an overall instance of EXX Intention to Apply, which continues to be maintained. 

“Law XXX to be in force from 1.1.2018”
To add to scope note: the nature of the time use as declarative

Quantification: many to one (0,1:0,n)
Scope note:

This property associates the beginning of an instance of EXX Intention to Apply with an explicit activity initiating it. Often, the initiation of intention to apply is implicit in the creation of the activity plan.

“Parliament XX deciding law YY”

Quantification: many to one (0,1:0,n)
Scope note:

This property associates the end of an instance of EXX Intention to Apply with an explicit activity or event terminating it. Often, the termination of intention to apply is implicit in the realization of the activity plan. In other cases, it is silently forgotten.

Suggestion: add to scope note how an event or an activity could bring about an end to the intention. For instance earthquake or volcanic eruption makes possibility fo realization impossible.
Potentially add example form architecture and city planning Anais

Storing MS Greek 418 into its new phase box (E7 Activity) ends the intention to conserve it (E?? Intention to Apply)

Quantification: many to many (0,n:0,n)
Scope note:

This property associates a particular instance of E7 Activity which realized an Activity Plan in a way regarded as valid by the actors intending it. (Should we require that a realization falls within the period of intending it?)

• “Getting a fine following paragraph XXX.” “I have built my house according to the agreed design (not me alone…)”
• The conservation of MS Greek 418 (E7 Activity) realised the proposals for its conservation (Activity Plan)

Quantification: many to one,necessary (1,1,0,n)
Scope note:

This property associates an instance of E93 Presence with the instance of E18 Physical Thing of which it represents a temporal restriction (i.e.: a time-slice) of the thing’s trajectory through spacetime. In other words, it describes where the instance of E18 Physical Thing was or moved around within a given time-span. Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence.

This property is a strong shortcut of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P166 was a presence of (had presence) to E93 Presence.

• Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998)
• Johann Joachim Winckelmann’s whereabouts from 19^th November 19 1755 until 9^th April 1768 (E93) was a presence of Johann Joachim Winckelmann (E21). (Wiencke, 1998)

Quantification: many to one, necessary (1,1:0,n)
Scope note:

This property associates an instance of E93 Presence with the instance of E18 Physical Thing of which it represents a temporal restriction (i.e.: a time-slice) of the thing’s trajectory through spacetime. In other words, it describes where the instance of E18 Physical Thing was or moved around within a given time-span. Instantiating this property constitutes a necessary part of the identity of the respective instance of E93 Presence.

This property is a strong shortcut of the fully developed path from E18 Physical Thing through P196 defines, E92 Spacetime Volume, P166 was a presence of (had presence), E93 Presence.    
 

• Johann Joachim Winckelmann’s whereabouts in December 1755 (E93) was a presence of Johann Joachim Winckelmann (E21) (Wiencke, 2020)
• Johann Joachim Winckelmann’s whereabouts from November 19 1755 until April 9 1768 (E93) was a presence of Johann Joachim Winckelmann (E21) (Wiencke, 2020)

Quantification: one to one,necessary (1,1,0,1)
Scope note:

This property associates an instance of E18 Physical Thing with the instance of E92 Spacetime Volume that constitutes the complete trajectory of its geometric extent through spacetime for the whole time of the existence of the instance of E18 Physical Thing.

An instance of E18 Physical Thing not only occupies a particular geometric space at each instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime, i.e., the instance of E92 Spacetime Volume this property associates it with. This real spatiotemporal extent of the instance of E18 Physical Thing is regarded as being unique, in all its details and fuzziness; the identity and existence of the E92 Spacetime Volume depends uniquely on the identity of the instance of E18 Physical Thing, whose existence defines it. It constitutes a phenomenal spacetime volume as defined in CRMgeo (Doerr & Hiebel, 2013).

Included in this spacetime volume are both the spaces filled by the matter of the physical thing and any inner space that may exist, for instance the interior of a box. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a finite number of individually contiguous subsets of this spacetime volume equal to the number of objects that constitute the set and that are never connected during its existence.

• H.M.S. Temeraire (E22) defines the spacetime volume of H.M.S. Temeraire (E92). [it was built, during 1798, in Chatham and destroyed, during 1838, in Rotherhithe] (Willis, 2010)
• The Saint Titus reliquary (E22) defines the Spacetime Volume of the Saint Titus reliquary (E92). [the reliquary has been produced by the workshop of the Vogiatzis brothers located at Monastiraki, Athens, in 1966 as container for the skull of Saint Titus, which was placed into it at that time and has since then continued to fall within the container's spacetime volume. The reliquary with the skull has been kept in the Saint Titus Church in Heraklion, Crete since 1966] (Fisher & Garvey, 2010) (Panotis, 2016)

Scope note:

This property associates an instance of E18 Physical Thing with the instance of E92 Spacetime Volume that constitutes the complete trajectory of its geometric extent through spacetime for the whole time of the existence of the instance of E18 Physical Thing.

An instance of E18 Physical Thing not only occupies a particular geometric space at each instant of its existence, but in the course of its existence it also forms a trajectory through spacetime, which occupies a real, that is phenomenal, volume in spacetime, i.e., the instance of E92 Spacetime Volume this property associates it with. This real spatiotemporal extent of the instance of E18 Physical Thing is regarded as being unique, in all its details and fuzziness; the identity and existence of the E92 Spacetime Volume depends uniquely on the identity of the instance of E18 Physical Thing, whose existence defines it. It constitutes a phenomenal spacetime volume as defined in CRMgeo (Doerr and Hiebel 2013).

Included in this spacetime volume are both the spaces filled by the matter of the physical thing and any inner space that may exist, for instance the interior of a box. Physical things consisting of aggregations of physically unconnected objects, such as a set of chessmen, occupy a finite number of individually contiguous subsets of this spacetime volume equal to the number of objects that constitute the set and that are never connected during its existence.
 

• H.M.S. Temeraire (E22) defines the spacetime volume of H.M.S. Temeraire [it was built, during 1798, in Chatham and destroyed, during 1838, in Rotherhithe] (Willis 2010)
• The Saint Titus reliquary (E22) defines the Spacetime Volume of the Saint Titus reliquary (E92) [the reliquary has been produced by the workshop of the Vogiatzis brothers located at Monastiraki, Athens, in 1966 as container for the skull of Saint Titus, which was placed into it at that time and has since then continued to fall within the container's spacetime volume. The reliquary with the skull has been kept in the Saint Titus Church in Heraklion, Crete since 1966] (Fisher&Garvey 2010) (Panotis, 2016)

Quantification: many to many (0,n,0,n)
Scope note:

This property associates an instance of E93 Presence with an instance of E53 Place that geometrically overlaps with the spatial projection of the respective instance of E93 Presence. A use case of this property is to state through which places an object or an instance of E21 Person has or was moved within a given time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighbouring region during a known time-span.

This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P121 overlaps with, to E53 Place.

• Johann Joachim Winckelmann’s whereabouts from 19^th November 19 1755 until 9^th April 1768 (E93) covered parts of Paestum, Italy (E53). (Wiencke, 1998)
• The Byzantine Empire 1013 AD (E93) covered parts of The Italian Peninsula (E53). (Browning, 1980)

Quantification: many to many (0,n:0,n)
Scope note:

This property associates an instance of E93 Presence with an instance of E53 Place that geometrically overlaps with the spatial projection of the respective instance of E93 Presence. A use case of this property is to state through which places an object or an instance of E21 Person has or was moved within a given time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighboring region during a known time-span. It may also be used to describe a partial or complete, temporary or permanent extension of the spatial extent of some realm into a neighboring region during a known time-span. 

This property is a shortcut of the more fully developed path from E93 Presence through P161 has spatial projection, E53 Place, P121 overlaps with to E53 Place.
 

•  Johann Joachim Winckelmann’s whereabouts from November 19 1755 until April 9 1768 (E93) covered parts of Paestum, Italy (E53) (Wiencke, 2020)
• The Byzantine Empire 1013 AD (E93) covered parts of The Italian Peninsula (E53) (Browning, 1980)

Quantification: one to many (0,n,0,n)
Scope note:

This property relates one instance of E18 Physical Thing which acts as a container or support to a supported or contained instance of E18 Physical Thing. Typical examples of E18 Physical Things which are intended to function as a container or support include shelves, folders or boxes. These containers or supports provide a stable surface which is intended for other physical objects to be placed upon for storage, display, transport or other similar functions.

This property is a shortcut of the more fully developed path from E18 Physical Thing through P59 has section, E53 Place, P53i is former or current location of, to E18 Physical Thing. It is not a sub-property of P46 is composed of, as the held or supported object is not a component of the container or support.

This property can be used to avoid explicitly instantiating the E53 Place which is defined by an instance of E18 Physical Thing, especially when the only intended use of that instance of E18 Physical Thing is to act as a container or surface for the storage of other instances of E18 Physical Thing. The place’s existence is defined by the existence of the container or surface, and will go out of existence at the same time as the destruction of the container or surface.

This property is transitive.

• Archival folder “6” (E22) holds or supports the piece of paper carrying the text of a letter from Lawrence Alloway to Sylvia Sleigh (E22).
  [http://archives2.getty.edu:8082/xtf/view?docId=ead/2003.M.46/2003.M.46.xml;chunk.id=aspace_ref12_kf7;brand=default]
• Archival folder 17 (E22) holds or supports the daguerreotype that shows the image of Henry Ward Beecher as a young man (E22).
  [https://archives.yale.edu/repositories/12/archival_objects/1402266]
• Box 88 (E22) holds or supports folder 17 (E22). [https://archives.yale.edu/repositories/12/archival_objects/1402266]
• Bookshelf “GRI-708.1” (E22) holds or supports the book entitled “Catalog of Paintings in the J. Paul Getty Museum” (E22). (Potts, 2015)

Quantification: one to many (0,n:0,1)
Scope note:

This property relates one instance of E18 Physical Thing which acts as a container or support to a supported or contained instance of E18 Physical Thing. Typical examples of E18 Physical Things which are intended to function as a container or support include shelves, folders or boxes. These containers or supports provide a stable surface which is intended for other physical objects to be placed upon for storage, display, transport or other similar functions.

This property is  a shortcut of the more fully developed path from the domain E18 Physical Thing through P59 has section, E53 Place, P53i is former or current location of, to the range E18 Physical Thing.  It is not a sub-property of P46 is composed of, as the held or supported object is not a component of the container or support.

This property can be used to avoid explicitly instantiating the E53 Place which is defined by an instance of E18 Physical Thing, especially when the only intended use of that instance of E18 Physical Thing is to act as a container or surface for the storage of other instances of E18 Physical Thing. The place’s existence is defined by the existence of the container or surface, and will go out of existence at the same time as the Destruction of the container or surface. This property is transitive.
 

• Archival folder “6” (E22) holds or supports the piece of paper (E22) carrying the text of a letter from Lawrence Alloway to Sylvia Sleigh 
  [reference:http://archives2.getty.edu:8082/xtf/view?docId=ead/2003.M.46/2003.M.46…
• Archival folder "17" (E22) holds or supports the daguerreotype (E22) that shows the image of Henry Ward Beecher as a young man 
  [reference:https://archives.yale.edu/repositories/12/archival_objects/1402266
• Box "88" (E22) holds or supports folder "17" (E22) [reference:https://archives.yale.edu/repositories/12/archival_objects/1402266 [3] ] 
• Bookshelf “GRI-708.1” (E22) holds or supports the book entitled “Catalog of Paintings in the J. Paul Getty Museum” (E22) (Potts, 2015)

Quantification: many to many (0,n,0,n)
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.

• “www.cidoc.icom.org” (E51) has type URL (E55)

Quantification: many to many (0,n:0,n)
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.

• “enquiries@cidoc-crm.org” (E51) has type e-mail address (E55)

Quantification: many to many (0,n,0,n)
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.

• www.cidoc.icom.org (E51) has type URL (E55)

Quantification: many to many (0,n:0,n)
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.

• “enquiries@cidoc-crm.org” (E51) has type e-mail address (E55)

Quantification: many to many (0,n:0,n)
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.

• “enquiries@cidoc-crm.org” (E51) has type e-mail address (E55)

Quantification: many to many (0,n,0,n)
Scope note:

This property allows sub typing of CIDOC CRM entities –a form of specialisation – through the use of a terminological hierarchy, or thesaurus.

The CIDOC 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 CIDOC CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E41 Appellation, for example, may be specialised into “e-mail address”, “telephone number”, “post office box”, “URL” etc. none of which figures explicitly in the CIDOC CRM hierarchy. A comprehensive explanation about refining CIDOC CRM concepts by E55 Type is given in the section “About Types” in the section on “Specific Modelling Constructs” of this document.

This property is a shortcut for the path from E1 CRM Entity through P41i was classified by, E17 Type Assignment, P42 assigned to E55 Type.

• “enquiries@cidoc-crm.org” (E41) has type e-mail address (E55). (fictitious)

Quantification: many to many (0,n:0,n)
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.

• “enquiries@cidoc-crm.org” (E51) has type e-mail address (E55)