State

Pattern

This class has been associated with the following pattern:

Pattern:Activity Pattern

Subclass Of

Geo:Feature

Description

An English description of the definition (what distinguishes this sense of the term?).

A state specifies some snapshot of objects in the domain as they exist at some point in time. States have the following core set of properties: o hasStatus: identifies the StateStatus at some point or interval in time. For example, the state may be “unsatisfied, “satisfied” or “completed”. o achievedAt: identifies the time Interval or Instant during which the state was satisfied. o scheduledFor: identifies a time Interval during which the state is scheduled to be realized. o effectOf: identifies an Activity that the state was realized by. o preconditionOf: identifies an Activity requires the state to be realized in order to occur. A State may also be described with the following, supplemental properties: o enables: identifies an Activity that in some (indirect) way was enabled by the state. The enables property is the inverse of the enabledBy property and is a generalization (super-property) of the preconditionOf property. o causedBy: identifies an Activity that in some (indirect) way caused the state to be realized. The causedBy property is the inverse of the causes property and is a generalization (super-property) of the effectOf property.

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:Activity ‎ (← links)
• TerminalState ‎ (← links)
• NonTerminalState ‎ (← links)
• RecurringEvent ‎ (← links)
• ISO5087-1:Allocation ‎ (← links)
• Goal ‎ (← links)
• Pattern:Activity Pattern ‎ (← 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

Annotations

Annotation	Value

Manchester Syntax Specification

Property	Restriction	Value
PreconditionOf	only	ISO5087-1:Activity
Enables	only	ISO5087-1:Activity
EffectOf	only	ISO5087-1:Activity
CausedBy	only	ISO5087-1:Activity
ScheduledFor	max 1	TemporalEntity
HasStatus	exactly 1	StateStatus

Supplementary Figures

Figure	Caption
	Figure 1: A generic activity cluster.
	Figure 2: Example use of the Activity Ontology.