Activity models

latest update: 21 Febr. 2015


Introduction

There are four different types of involvement in an activity:

Participation

Part 2 defines Participation as follows:

A Participation is a CompositionOfIndividual that indicates that a PossibleIndividual is a participant in an Activity.

NOTE The PossibleIndividual that is the part in the Participation is may be a temporal part of a WholeLifeIndividual that is classified by the ParticipatingRoleAndDomain that indicates the role it plays in the Activity.

EXAMPLE The relationship between the temporal part of P1234 that performs the discharge of the Motor Vessel Murex on 2nd December 2002, and the activity that is that discharge of that vessel is a Participation.

EXPRESS specification:

ENTITY participation  

    SUBTYPE OF (composition_of_individual);  

    SELF\composition_of_individual.whole   :   activity;  

END_ENTITY;  

Attribute definitions:

    whole   :   The Activity that is the whole in the Participation.  

Exegesis

Normally there are more than one possible individuals participating in an activity, and together they cause some state change in the one that is subjected to that activity. The relationship between an activity and the participants is deemed to be of the composition type. The reason for this is that an activity is in fact the interaction between the behaviours of the participating objects. So when you put them together (composition) the activity occurs.

Template

The template diagrams are shown below.

Template for ClassOfParticipation

  

Template for Participation


InvolementByReference

Part 2 defines InvolvementByReference as follows:

An InvolvementByReference is a Relationship that indicates that a Thing is referred to in an Activity.

NOTE This entity type is for involvements that are not direct Participation of a PossibleIndividual, such as involvement of a class, or of a historical or future temporal part of a PossibleIndividual.

EXAMPLE A conversation that refers to the Roman Empire is an Activity that relates to the Roman Empire by an InvolvementByReference.

EXPRESS specification:

ENTITY involvement_by_reference  

    SUBTYPE OF (relationship);  

    involved   :   thing;  

    involver   :   activity;  

END_ENTITY;  

Attribute definitions:

    involved   :   The Thing that is involved in the referenced Activity.  

    involver   :   The Activity in which the referenced Thing is involved.  

Exegesis

Neither an instance of Class (or its many subtypes), nor instances of PossibleIndividual that existed in the past or will (probably) exist in the future, can physically participate in an activity that takes place at present. We can only refer to it. A typical example is the reference that is made to standards (ClassOfInformationRepresentation).

NOTE - In cases that the activity took place in the same period in time as the possible individual existed, that may have been a matter of participation. However, in cases that a possible individual, that exists in the same period in time as the activity, it is also possible that only reference is been made to that individual. For example when two people talk about the third.

Template

The template diagrams are shown below.

Template for ClassOfInvolvementByReference

Template for InvolvementByReference of a Class

Template for InvolvementByReference of a PossibleIndividual


Recognition

Part 2 defines Recognition as follows:

A Recognition is a Relationship that indicates that a Thing is recognized through an Activity.

EXAMPLE Measurement activity #358 recognized that the room was a member of the 20 Celsius Property.

EXPRESS specification:

ENTITY recognition  

    SUBTYPE OF (relationship);  

    recognized    :   thing;  

    recognizing   :   activity;  

END_ENTITY;  

Attribute definitions:

    recognized    :   The Thing that is recognized by the Activity.  

    recognizing   :   The Activity that results in the recognition.

Exegesis

Recognizing is defined as "to perceive a thing to be the same as, or belong to the same class as, something previously seen or known.".

In case something is recognized about an object it means that it is the classification with that 'something' is what is recognized. If you want to recognize the temparature of a temporal part of a stream (see below) the 'recognized' attribute refers to an instance of Classification between that stream and the instance of Property that is quantified as 75.9 C.

But we can also recognize that a particular car is a (is classified as) Mercedes 300 SEL. And also that that car has passed the annual check (this is modeled with the classification of that car with that instance of Status).

Part 2 of ISO 15926 was written before the Part 7 templates were designed. For practical reasons it is better to refer to a template instance that represents the recognized fact. Recognition of something being the same as something else is to be modeled with the owl:sameAs property.

Template

The template diagrams are shown below.

Template for ClassOfRecognition

Template for Recognition of Information


Cause of Event

Part 2 defines CauseOfEvent as follows:

A CauseOfEvent is a Relationship that indicates that the caused Event is caused by the causer Activity.

EXAMPLE The relation that indicates that the tanker loading Activity caused the Event described as 'tank liquid level full' can be represented by an instance of CauseOfEvent.

EXPRESS specification:

ENTITY cause_of_event

    SUBTYPE OF (relationship);

    caused  :  event;

    causer   :  activity;

END_ENTITY;

Attribute definitions:

    caused  :  The Event that is caused in the CauseOfEvent.

    causer  :  The Activity that is the causer in the CauseOfEvent.

and for all clarity:

An Event is a PossibleIndividual with zero extent in time. An Event is the temporal boundary of one or more PossibleIndividuals, although there may be no knowledge of these PossibleIndividuals.

EXAMPLE The connection of power to a pump motor is an Event that marks the beginning of a temporal part of that pump motor that is in operation.

EXPRESS specification:

ENTITY event  

    SUBTYPE OF (possible_individual);  

END_ENTITY;  

Exegesis

Here we deal with the question what activity caused the event to happen. In the example below we manufacture a pump, causing the pump to begin its existence. We typically deal with instances of WholeLifeIndividual here.

Template

The derived template diagrams are shown below.

Template for ClassOfCauseOfBeginningOfClassOfIndividual

Template for ActivityCausesBegunIndividual