TerminalResourceState

Pattern

This class has been associated with the following pattern:

Pattern:Resource Pattern

Subclass Of

TerminalState

Description

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

A terminal state type has no substates (cannot be decomposed). It corresponds to a particular class of manifestations. A terminal state is achieved at some time if and only if there exists a manifestation within its defined classification, that exists at that time. The Resource pattern extends TerminalState (defined in the Activity Pattern), specialized as TerminalResourceState with the following properties: o hasQuantity: specifies the Quantity (as defined in the City Units pattern) of the resource that participates in the State, if applicable. o hasResource: specifies a Resource that participates in the state. This identifies the condition of the object that plays a resource role (i.e., is used, consumed, etc) when the state’s status is active. o hasAllocation: specifies one or more Allocations that identify a resource and what time it is allocated to the state.

Required by Use Case(s)

(why is this specialized definition needed?)

CDM References

What other classes or properties reference this term?

• ISO5087-1:ConsumeState ‎ (← links)
• ProduceState ‎ (← links)
• UseState ‎ (← links)
• ReleaseState ‎ (← links)
• Pattern:Resource 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
HasQuantity	only	i72:Quantity
HasResource	only	Resource
HasAllocation	only	5087-1:Allocation

Supplementary Figures

Figure	Caption