| Template Slots | |||||
| Slot name | Documentation | Type | Allowed Values/Classes | Cardinality | Default | start time | The first time when an event is happening (holds). This might be an integer or a class. | Any | Temporal_measure | 0:1 | follows | When one interval starts after another ends. | Instance | Process | 0:* | precedes | When one interval ends before another starts. | Instance | Process | 0:1 | interruption | An event that results in the script not reaching the goal state. | Instance | Event | 0:1 | normal_termination | A state that holds when the script is "successfully completed." This might serve as the basis for reasoning about goals. | Instance | State | 0:1 | synchronous | The idea is two complex or cyclic complex events that maintain phase as they proceed. | Instance | Process | 0:* | end time | Like start_time, but the other end of the interval. Likewise start_time, not ready to commit to integer vs. class for the value here. | Any | Temporal_measure | 0:1 | parts | The inverse of part_of. This should be a list of all of the things that claim to be part_of this object. | Instance | Process | 0:* | contained_in | This slot should definitely behave differently for different classes - for example physical objects and information. | Instance | Process | 0:1 | simultaneous | Two intervals that share start and end points (?). This should be a symmetric relation. | Instance | Process | 0:* | contains | Events contained within, but not essential to, a larger event. | Instance | Process | 0:* | part_of | This "part_of" relation usually implies temporal inclusion. | Instance | Process | 0:1 | start | Designates a starting point for a cyclic process. This avoids the requirement to represent cyclic processes with a cyclic graph. Not impossible to deal with, but adds unnecessary complexity. | Instance | Action | 0:* |