OntoME

Subclass of:

• E29 Design or Procedure

Scope note:

This class comprises plans foreseeing specific predefined activities or kinds of activities taking place. They consist of descriptions of specific constraints, patterns or types of activities that could be realized. They may also foresee that the planned activities are realized at times explicitly foreseen by the actor intending the application of the plan, for instance, to organize a conference, in which case we may talk about “active plans”. Alternatively, times of realization may be foreseen in reaction to external events of a kind foreseen by the plan, for instance the rescue activity after an earthquake following a rescue plan, or a penal action in the case of criminal activity according to a penal code, in which case we may talk about “reactive plans”. The existence of an instance of Activity Plan does not necessarily imply the intention of any Actor to apply it. It may be created together, before or without the will to apply it. For instance, laws are created before they are passed by parliament. Any Activity Plan may require specific conditions for it to be applicable. For example, a plan to excavate a river bank may require that the river is flooded, or my plan to lime plaster my stone wall requires that it is winter (i.e. wet and cold).

Examples:

The disaster plan of Tate Archives in case of the Thames flooding.

The proposal for conservation work for MS Greek 418 at the Saint Catherine library.

Provisions of Law 3730/2008 of the Greek Government against smoking in work places.

In First Order Logic:

• socE2(x) ⊃ E29(x)

Ongoing properties:

• socP requires event of type (delete - included in Event specification now) → E55 Type
• socP17 concerns (is concerned with) → socE4 Trigger Event Template

Incoming properties:

• E7 Activity → socP15 realised (was realised by)
• E7 Activity → socP3 realized (duplicate, delete)
• E31 Document → socP2 assesses (is assessed by)
• socE3 Intention to Apply → socP16 intended to apply (was intended by)