Permanent link to this class
Ontology for Maintenance Procedure Documentation - Static Procedure Ontology
loading...| Preferred Name |
Event |
| Definitions |
Event is close in meaning to BFO's 'process boundary', and to DOLCE's 'achievement'. Note that BFO's 'process boundary' is a sibling class to 'process', even though the definition annotation states it to be a "temporal part of a process". It's not obvious why the event/process boundary shouldn't have the same participants as the parent activity/process. An activity that occurs at one or more specific points in time. An 'event' doesn't need to be temporally connected. For example, several instances of switching on a heater over a week may be represented by a single 'event' individual; it will occupy a non-singular 'instant region'. The details of a singular event part may be modelled by relating the event to 'instant' individuals. |
| ID |
http://rds.posccaesar.org/ontology/lis14/rdl/Event |
| comment |
Event is close in meaning to BFO's 'process boundary', and to DOLCE's 'achievement'. Note that BFO's 'process boundary' is a sibling class to 'process', even though the definition annotation states it to be a "temporal part of a process". It's not obvious why the event/process boundary shouldn't have the same participants as the parent activity/process. An 'event' doesn't need to be temporally connected. For example, several instances of switching on a heater over a week may be represented by a single 'event' individual; it will occupy a non-singular 'instant region'. The details of a singular event part may be modelled by relating the event to 'instant' individuals. |
| definition |
Event is close in meaning to BFO's 'process boundary', and to DOLCE's 'achievement'. Note that BFO's 'process boundary' is a sibling class to 'process', even though the definition annotation states it to be a "temporal part of a process". It's not obvious why the event/process boundary shouldn't have the same participants as the parent activity/process. An activity that occurs at one or more specific points in time. An 'event' doesn't need to be temporally connected. For example, several instances of switching on a heater over a week may be represented by a single 'event' individual; it will occupy a non-singular 'instant region'. The details of a singular event part may be modelled by relating the event to 'instant' individuals. |
| example |
The beginning of a lifting operation, the end of a measurement activity, the midpoint between beginning and end of an activity. |
| is primitive |
false |
| label |
Event |
| naturalLanguageDefinition |
An activity that occurs at one or more specific points in time. |
| prefixIRI |
lis:Event |
| prefLabel |
Event |
| see also |
ISO 15926-2:2003 'event' |
| subClassOf |
| Delete | Subject | Author | Type | Created |
|---|---|---|---|---|
| No notes to display |