Concept Search
Showing 2710 results:
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 4.1
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 6.1
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 5.0.2
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 6.2.2
E60 Number
Scope note:
This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision.
Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension
Examples:
- 5
- 3+2i
- 1.5e-04
- (0.5, - 0.7,88)
Type: Entity
Belongs to version: Version 5.1.2
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 6.0
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and references to temporal coordinate systems to express time in some context relevant to cultural and scientific documentation.
Instantiating different instances of E61 Time Primitive relative to the same instance of E52 Time Span allows for the expression of multiple opinions/approximations of the same phenomenon. When representing different opinions/approximations of the E52 Time Span of some E2 Temporal Entity, multiple instances of E61 Time Primitive should be instantiated relative to one E52 Time Span. Only one E52 Time Span should be instantiated since there is only one real phenomenal time extent of any given temporal entity.
The instances of E61 Time Primitive are not considered as elements of the universe of discourse that the CIDOC CRM aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: version 7.1
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 6.2
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 5.0.1
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 6.2.1
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and references to temporal coordinate systems to express time in some context relevant to cultural and scientific documentation.
Instantiating different instances of E61 Time Primitive relative to the same instance of E52 Time Span allows for the expression of multiple opinions/approximations of the same phenomenon. When representing different opinions/approximations of the E52 Time Span of some E2 Temporal Entity, multiple instances of E61 Time Primitive should be instantiated relative to one E52 Time Span. Only one E52 Time Span should be instantiated since there is only one real phenomenal time extent of any given temporal entity.
The instances of E61 Time Primitive are not considered as elements of the universe of discourse that the CIDOC CRM aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
Therefore, they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class.
Examples:
- “1994 – 1997”
- “13th May 1768”
- “2000/01/01 00:00:59.7”
- “85th century BCE”
Type: Entity
Belongs to version: version 7.1.1
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 4.1
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 6.1
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 5.0.2
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and references to temporal coordinate systems to express time in some context relevant to cultural and scientific documentation.
Instantiating different instances of E61 Time Primitive relative to the same instance of E52 Time Span allows for the expression of multiple opinions/approximations of the same phenomenon. When representing different opinions/approximations of the E52 Time Span of some E2 Temporal Entity, multiple instances of E61 Time Primitive should be instantiated relative to one E52 Time Span. Only one E52 Time Span should be instantiated since there is only one real phenomenal time extent of any given temporal entity.
The instances of E61 Time Primitive are not considered as elements of the universe of discourse that the CRM aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class.
Instantiating different instances of E61 Time Primitive relative to the same instance of E52 Time Span allows for the expression of multiple opinions/approximations of the same phenomenon. When representing different opinions/approximations of the E52 Time Span of some E2 Temporal Entity, multiple instances of E61 Time Primitive should be instantiated relative to one E52 Time Span. Only one E52 Time Span should be instantiated since there is only one real phenomenal time extent of any given temporal entity.
The instances of E61 Time Primitive are not considered as elements of the universe of discourse that the CRM aims at defining and analysing. Rather, they play the role of a symbolic interface between the scope of this model and the world of mathematical and computational manipulations and the symbolic objects they define and handle.
Therefore they must not be represented in an implementation by a universal identifier associated with a content model of different identity. In a concrete application, it is recommended that the primitive value system from a chosen implementation platform and/or data definition language be used to substitute for this class.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 6.2.2
E61 Time Primitive
Scope note:
This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation.
E61 Time Primitive is not further elaborated upon within the model.
Examples:
- 1994 – 1997
- 13 May 1768
- 2000/01/01 00:00:59.7
- 85th century BC
Type: Entity
Belongs to version: Version 5.1.2
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 6.0
E62 String
Scope note:
This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. They may or may not contain a language code.
In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces other than that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date but consist of different strings.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: version 7.1
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 6.2
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 5.0.1
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 6.2.1
E62 String
Scope note:
This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. They may or may not contain a language code.
In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces other than that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date but consist of different strings.
Examples:
- “the Quick Brown Fox Jumps Over the Lazy Dog”
- “6F 6E 54 79 70 31 0D 9E”
Type: Entity
Belongs to version: version 7.1.1
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 4.1
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 6.1
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 5.0.2
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 6.2.2
E62 String
Scope note:
This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
E62 String is not further elaborated upon within the model.
Examples:
- the Quick Brown Fox Jumps Over the Lazy Dog
- 6F 6E 54 79 70 31 0D 9E
Type: Entity
Belongs to version: Version 5.1.2
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 6.0
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any ΙΝΣΤΑΝΨΕ ΟΦ E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a "terminus post quem” or “terminus ante quem".
Examples:
- the birth of my child (E67) (fictitious)
- the birth of Snoopy, my dog (fictitious)
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower (Tissandier, 1889)
Type: Entity
Belongs to version: version 7.1
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 6.2
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus postquem and antequem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 5.0.1
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 6.2.1
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any instance of E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”.
Examples:
- the birth of my child (E67) (fictitious)
- the birth of Snoopy, my dog (fictitious)
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower (E12) (Tissandier, 1889)
Type: Entity
Belongs to version: version 7.1.1
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus postquem and antequem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 4.1
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 6.1
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 5.1.2
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 5.0.2
E63 Beginning of Existence
Scope note:
This class comprises events that bring into existence any E77 Persistent Item.
It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem.
Examples:
- the birth of my child
- the birth of Snoopy, my dog
- the calving of the iceberg that sank the Titanic
- the construction of the Eiffel Tower
Type: Entity
Belongs to version: Version 6.2.2
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 6.0
E64 End of Existence
Scope note:
This class comprises events that end the existence of any instance of E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”. In cases where substance from an instance of E64 Persistent Item continues to exist in a new form, the process would be documented as instances of E81 Transformation.E
Examples:
- the death of Snoopy, my dog (fictitious)
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC (Trell, 1945)
Type: Entity
Belongs to version: version 7.1
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 6.2
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 5.0.1
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 6.2.1
E64 End of Existence
Scope note:
This class comprises events that end the existence of any instance of E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a “terminus post quem” or “terminus ante quem”. In cases where substance from an instance of E64 Persistent Item continues to exist in a new form, the process would be documented as instances of E81 Transformation.
Examples:
- the death of Snoopy, my dog (fictitious)
- the melting of the snowman (E6)
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC (E7,E6) (Trell, 1945)
Type: Entity
Belongs to version: version 7.1.1
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 4.1
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 6.1
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 5.1.2
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 5.0.2
E64 End of Existence
Scope note:
This class comprises events that end the existence of any E77 Persistent Item.
It may be used for temporal reasoning about things (physical items, groups of people, living beings) ceasing to exist; it serves as a hook for determination of a terminus postquem and antequem. In cases where substance from a Persistent Item continues to exist in a new form, the process would be documented by E81 Transformation.
Examples:
- the death of Snoopy, my dog
- the melting of the snowman
- the burning of the Temple of Artemis in Ephesos by Herostratos in 356BC
Type: Entity
Belongs to version: Version 6.2.2
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 6.0
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution (Farrand, 1913)
- the drafting of U.N. resolution 1441 (United Nations Security Council, 2002)
Type: Entity
Belongs to version: version 7.1
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 6.2
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 5.0.1
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 6.2.1
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution (Farrand, 1913)
- the drafting of U.N. resolution 1441 (United Nations Security Council, 2002)
Type: Entity
Belongs to version: version 7.1.1
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 6.1
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 5.1.2
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 5.0.2
E65 Creation
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 6.2.2
E65 Creation Event
Scope note:
This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc.
Examples:
- the framing of the U.S. Constitution
- the drafting of U.N. resolution 1441
Type: Entity
Belongs to version: Version 4.1
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 6.0
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group in 2000
- the formation of the Soviet Union (Pipes, 1964)
- the conspiring of the murderers of Caesar (Irwin, 1935)
Type: Entity
Belongs to version: version 7.1
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 6.2
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 5.0.1
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 6.2.1
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group in 2000
- the formation of the Soviet Union (Pipes, 1964)
- the conspiring of the murderers of Caesar (Irwin, 1935)
Type: Entity
Belongs to version: version 7.1.1
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 6.1
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 5.1.2
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 5.0.2
E66 Formation
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation does not include the arbitrary aggregation of people who do not act as a collective.
The formation of an instance of E74 Group does not require that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 6.2.2
E66 Formation Event
Scope note:
This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation.
E66 Formation Event does not include the arbitrary aggregation of people who do not act as a collective.
Examples:
- the formation of the CIDOC CRM Special Interest Group
- the formation of the Soviet Union
- the conspiring of the murderers of Caesar
Type: Entity
Belongs to version: Version 4.1
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 6.0
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living being).
Twins, triplets etc. are typically brought into life by the same instance of E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the birth.
Examples:
- the birth of Alexander the Great (Stoneman, 2004)
Type: Entity
Belongs to version: version 7.1
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 6.2
E67 Birth
Scope note:
This class comprises the birth of a human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 5.0.1
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 6.2.1
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living being).
Twins, triplets etc. are typically brought into life by the same instance of E67 Birth. The introduction of E67 Birth as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the birth.
Examples:
- the birth of Alexander the Great (Stoneman, 2004)
Type: Entity
Belongs to version: version 7.1.1
E67 Birth
Scope note:
This class comprises the birth of a human beings.
E67 Birth is a biological event focussing on the context of people coming into life.
(E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 4.1
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 6.1
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 5.1.2
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 5.0.2
E67 Birth
Scope note:
This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings).
Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event.
Examples:
- the birth of Alexander the Great
Type: Entity
Belongs to version: Version 6.2.2
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 6.0
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an instance of E74 Group.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an instance of E7 Activity.
Examples:
- the fall of the Roman Empire (Whittington, 1964)
- the liquidation of Enron Corporation (Atlas, 2001)
Type: Entity
Belongs to version: version 7.1
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 6.2
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 5.0.1
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 6.2.1
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an instance of E74 Group.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an instance of E7 Activity.
Examples:
- the fall of the Roman Empire (Whittington, 1964)
- the liquidation of Enron Corporation (Atlas, 2001)
Type: Entity
Belongs to version: version 7.1.1
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 4.1
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 6.1
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 5.1.2
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 5.0.2
E68 Dissolution
Scope note:
This class comprises the events that result in the formal or informal termination of an E74 Group of people.
If the dissolution was deliberate, the Dissolution event should also be instantiated as an E7 Activity.
Examples:
- the fall of the Roman Empire
- the liquidation of Enron Corporation
Type: Entity
Belongs to version: Version 6.2.2
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
Type: Entity
Belongs to version: Version 6.0
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, the death should be documented as an instance of both E69 Death and E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence
Examples:
- the murder of Julius Caesar (E69, E7) (Irwin, 1935)
- the death of Senator Paul Wellstone (Monast, 2003)
Type: Entity
Belongs to version: version 7.1
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
Type: Entity
Belongs to version: Version 6.2
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
Type: Entity
Belongs to version: Version 5.0.1
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
Type: Entity
Belongs to version: Version 6.2.1
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, the death should be documented as an instance of both E69 Death and E7 Activity. The death or perishing of other living beings should be documented as instances of E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69, E7) (Irwin, 1935)
- the death of Senator Paul Wellstone (Monast and Tao, 2002)
Type: Entity
Belongs to version: version 7.1.1
E69 Death
Scope note:
This class comprises the deaths of human beings.
If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence.
Examples:
- the murder of Julius Caesar (E69,E7)
- the death of Senator Paul Wellstone
Type: Entity
Belongs to version: Version 4.1