Notes for Process-Spec:
- We intentionally do not define the term `process', as it means
so many things to so many people. The terms in this
Ontology should be sufficient to define whatever specific
notion of `process' is required.
- Typically, a Process-Spec will be parameterised to
enable reusability in various forms at different times.
As such, it may be viewed as a Plan schema.
Slots on class Process-Spec:
- Arity: 1
- Documentation:
a Plan that is intended to be or is capable of being
Executed more than once
- Instance-Of: Class, Relation, Set
- Subclass-Of: Plan, Activity-Or-Spec, Activity-Spec, Eo-Entity, Qua-Entity ...
Slots on instances of Process-Spec:
- Intended-Purpose:
- Minimum-Slot-Cardinality: 0
- Slot-Cardinality: 1
- Slot-Value-Type: State-Of-Affairs
- Specified-Activity-Interval:
- Minimum-Slot-Cardinality: 0
- Slot-Cardinality: 1
- Slot-Value-Type: Time-Range
- Specified-Effect:
- Minimum-Slot-Cardinality: 1
- Slot-Value-Type: Effect
- Specified-Pre-Condition:
- Minimum-Slot-Cardinality: 1
- Slot-Value-Type: Pre-Condition