| Template Slots | |||||
| Slot name | Documentation | Type | Allowed Values/Classes | Cardinality | Default | 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 | start time | The first time when an event is happening (holds). This might be an integer or a class. | Any | Temporal_measure | 0:1 | contains | Events contained within, but not essential to, a larger event. | Instance | Process | 0:* | simultaneous | Two intervals that share start and end points (?). This should be a symmetric relation. | Instance | Process | 0:* | part_of | This "part_of" relation usually implies temporal inclusion. | Instance | Process | 0:1 | follows | When one interval starts after another ends. | Instance | Process | 0:* | precedes | When a temporal interval ends before another starts. | Instance | Process | 0:1 | object | The "direct" object slot for an action. If a turtle uses a flipper to move stand, the flipper is the instrument, which moves the object - sand. Note: cases of moving a body part may be best treated by assigning the part moved to the object slot, with something more proximal serving as the instrument - move_head ought to be modelled as object:head; instrument:neck. | Instance | Body | 0:* | caused_by | This slot is a causal link back from an event to another event. Members of Event_by_action ought to specify the action that got them added to this class. | Instance | Action | 1:1 | synchronous | The idea is two complex or cyclic complex events that maintain phase as they proceed. | Instance | Process | 0:* |