z[Deprecated] Unitary Event – C98
This class does not yet have the minimum number of validated parts required for publication.
C98 z[Deprecated] Unitary Event
Scope note:
This class comprises events that take place in a unity of time, place and action. This definition, that should allow a clear identification of instances of this class, is inspired by the three unities of Greek tragedy: a unitary event should have one principal action (unity of action) specified by a type, it should occur over a limited period of time (no more than 24 hours according to the unity of time in tragedy, but could be shorter or longer in real life), and should happen in a single physical location (unity of place). The most important unity defining the event is the unity of action and the action is generally restricted to one single place and a limited duration in time.
The unitary event is defined in contrast to the sdh:C4 Phase class which includes more complex temporalities composed of several events, activities or sub-phases, taking place over a longer period of time, and being projected on a space which can be quite vast. Often, but not always, a unitary event is related to the notion of achievement or fulfillment while a phase is related to the notion of process or development. Note that this difference does not mean that a unitary event is atomic: it could be composed of several sub-events (as instances of the same class) provided that the three unities of action, time and place are ensured.
Examples:
The assassination of Henry IV of France on 14 May 1610
The 1886 eruption of Mount Tarawera
Scope notes
Show | Scope note | Language | Namespace | View details | Comments | Validation |
---|---|---|---|---|---|---|
This class comprises events that take place in a unity of time, place and action. This definition, that should allow a clear identification of instances of this class, is inspired by the three unities of Greek tragedy: a unitary event should have one principal action (unity of action) specified by a type, it should occur over a limited period of time (no more than 24 hours according to the unity of time in tragedy, but could be shorter or longer in real life), and should happen in a single physical location (unity of place). The most important unity defining the event is the unity of action and the action is generally restricted to one single place and a limited duration in time. The unitary event is defined in contrast to the sdh:C4 Phase class which includes more complex temporalities composed of several events, activities or sub-phases, taking place over a longer period of time, and being projected on a space which can be quite vast. Often, but not always, a unitary event is related to the notion of achievement or fulfillment while a phase is related to the notion of process or development. Note that this difference does not mean that a unitary event is atomic: it could be composed of several sub-events (as instances of the same class) provided that the three unities of action, time and place are ensured. | en | SDHSS Semantic Data for Humanities and Social Sciences CIDOC CRM Extension ongoing | 0 | Candidate |
Examples
Show | Example | Language | Namespace | View details | Comments | Validation |
---|---|---|---|---|---|---|
The assassination of Henry IV of France on 14 May 1610 The 1886 eruption of Mount Tarawera | en | SDHSS Semantic Data for Humanities and Social Sciences CIDOC CRM Extension ongoing | 0 | Candidate |
Additional notes
Show | Notes | Type | Language | Namespace | View details | Comments | Validation |
---|
Identifier: C98
Official URI: https://ontome.net/ns/sdhss/C98
OntoME URI: https://ontome.net/ontology/c837
Labels
Label | Language | Last updated | View details | Comments | Validation |
---|---|---|---|---|---|
z[Deprecated] Unitary Event * | en | 2022-02-05 | 0 | Denied (see comment) |
* : Standard label for this language
Namespace
Namespace | Last updated |
---|---|
SDHSS Semantic Data for Humanities and Social Sciences CIDOC CRM Extension ongoing | 2021-04-21 |
Parent classes
Class | Class namespace | Relation defined in | Justification | View details | Edit | Delete | Comments | Validation |
---|
Ancestor classes
Class | Depth | Class namespace | Via |
---|
Child and descendant classes
Class | Depth | Class namespace | Via |
---|
Related classes
Relation | Class | Class namespace | Justification | Relation defined in | View details | Edit | Delete | Comments | Validation |
---|
Outgoing properties (this class is domain)
Domain | Property identifier | Range | Namespace |
---|
Outgoing properties (inherited from ancestors)
Domain | Property identifier | Range | Namespace |
---|
Incoming properties (this class is range)
Domain | Property identifier | Range | Namespace |
---|
Incoming properties (inherited from ancestors)
Domain | Property identifier | Range | Namespace |
---|
Profiles using this class
Label | Version | Status | Last updated |
---|
Linked classes graph
Use mouse wheel to zoom in/out.
Comments
Vincent Alamercery
When looking at subclasses of crm:E5, how to distinguish between phases and unitary events? Could we interpret all crm:E7 as phases, even if some are close from having a unity of time, place and action; and all crm:E63 and crm:E64 as unitary events, even if some are a little further from having a unity of time, place and action?
on September 22, 2021 17:22