Difference between revisions of "ISO5087-1:ConjunctiveState"
(Created page with "{{Class Definition |Description=A conjunctive state is a type of NonTerminalState that is defined by the conjunction of its child states. |Definition Status=Pending Approval }...") |
|||
| Line 1: | Line 1: | ||
{{Class Definition | {{Class Definition | ||
|Description=A conjunctive state is a type of NonTerminalState that is defined by the conjunction of its child states. | |Description=A conjunctive state is a type of NonTerminalState that is defined by the conjunction of its child states. | ||
| + | |Class Diagram Description=An activity cluster provides a basic structure for representing activity specifications. Illustrated in Figure 1, it consists of an activity connected to an enabling and caused state, each of which may be a state tree that defines complex states via decomposition into conjunctions and disjunctions of states. | ||
| + | |||
| + | Figure 2 illustrates the use of the Activity Ontology to describe a class of objects that should be identified as “Drive to Work” activities, where the effect of such an activity is a Conjunctive state. The conjunctive state is decomposed into two terminal states, meaning that it should be interpreted as a state where both sub-states (DriverAtWork and CarAtWork) are true. | ||
|Definition Status=Pending Approval | |Definition Status=Pending Approval | ||
}} | }} | ||
| Line 10: | Line 13: | ||
}} | }} | ||
}} | }} | ||
| − | {{Supplementary Figures}} | + | {{Supplementary Figures |
| + | |Figure Row={{Figure Row | ||
| + | |Figure=Act-1.png, | ||
| + | |Caption=Figure 1: A generic activity cluster. | ||
| + | }}{{Figure Row | ||
| + | |Figure=Act-2.png, | ||
| + | |Caption=Figure 2: Example use of the Activity Ontology. | ||
| + | }} | ||
| + | }} | ||
Revision as of 21:03, 3 July 2021
Pattern
This class has been associated with the following pattern:
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
A conjunctive state is a type of NonTerminalState that is defined by the conjunction of its child states.
Class Diagram Description
An activity cluster provides a basic structure for representing activity specifications. Illustrated in Figure 1, it consists of an activity connected to an enabling and caused state, each of which may be a state tree that defines complex states via decomposition into conjunctions and disjunctions of states.
Figure 2 illustrates the use of the Activity Ontology to describe a class of objects that should be identified as “Drive to Work” activities, where the effect of such an activity is a Conjunctive state. The conjunctive state is decomposed into two terminal states, meaning that it should be interpreted as a state where both sub-states (DriverAtWork and CarAtWork) are true.
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
- ISO5087-1:DisjunctiveState (← links)
- Pattern:Activity Pattern (← links)
- ConjunctiveState (redirect page) (← links)
- 5087-1:ConjunctiveState (redirect page) (← links)
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)
Annotations
| Annotation | Value |
|---|
Manchester Syntax Specification
| Property | Restriction | Value |
|---|---|---|
| disjointWith | DisjunctiveState |
Supplementary Figures
| Figure | Caption |
|---|---|
| Figure 1: A generic activity cluster. | |
| Figure 2: Example use of the Activity Ontology. |
