Issue 419: Activity plans

Starting Date: 
2019-06-05
Working Group: 
3
Status: 
Open
Background: 

In the 43rd joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 36th FRBR - CIDOC CRM Harmonization meeting, the crm-sig decided to merge the discussions took place in the issues 333, 359, 369 in the CRMsoc forming a new issue.

Heraklion, March 2019

Current Proposal: 

Posted by Thanasis on 10/6/2019

Dear all,

Following discussions with Martin I am sending some homework about the
specification of events with which the activity plans are concerned, and
also a revision of the Activity Plan scope note. Also attached.

-------------------------------------------------------------

socExx Event Specification
subclass of : E89 Propositional Object

Scope note:

This class comprises specifications of events by providing necessary or
desirable constraints to their properties, be it on the level of
particular items involved or on the level of kinds of processes, items
or qualities and quantities involved. Such specifications may be used to
recognize that a past or future particular event fits the specification
or for planning future events. Characteristically, instances of this
class may be created to be associated with instances of socExx Activity
Plan, as specification of the kind of event that should trigger the
execution of an Activity Plan. For example, we expect a disaster plan
for a library to be executed when a disaster happens or as part of a
disaster readiness exercise.

Examples:

* The description of the rainy weather conditions at the location and
date of my wedding (socExx Event Specification) done in advance by my
wedding planner, which was specified to trigger the plan (socExx
Activity Plan) of using a gazeebo.
* The description of the sunny weather conditions at the location and
date of my wedding (socExx Event Specification) done in advance by my
wedding planner, which was specified to trigger the plan (socExx
Activity Plan) of taking photographs at the park.
* The description of the humidity level reached in the museum store room
(socExx Event Specification) done in advance by a preventive
conservator, which was specified to trigger the plan (socExx Activity
Plan) of turning on the dehumidifier.

Properties:

* socPxx requires event type (is required event type of): E55 Type
(e.g.1 rainy weather and wedding, e.g.2 change of humidity)
* socPxx requires actor role (is required actor role of): E55 Type
(e.g.1 mayor)
* socPxx requires type of thing (is required type of thing of): E55 Type
(e.g., a car)
* socPxx requires place (is required place of): E53 Place (e.g.1 Cardiff
city hall, e.g.2 National Museum Wales store room)
* socPxx requires time-span (is required time-span of): E4 Time-span
(e.g.1 4th of June 2019, e.g.2 winter of 2019)
* socPxx requires actor (is required actor of): E39 Actor (e.g.1 mayor
John Smith)
* socPxx requires material substantial (is required material substantial
of): S10 Material Substantial (e.g.1 wedding ring, e.g.2 air in NMW
store room)
* ?? socPxx requires condition (is required condition): E89
Propositional Object? (e.g.2 that the RH > 20%)

----------------------------------------------------------

socExx Activity Plan
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
specification of the related planned or unplanned events can be done
using instances of socExx Event Specification. The fact that an instance
of socExx Activity Plan is linked to an instance of socExx Event
Specification does not require that it will only be executed after
events conforming to that specification take place.
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.

Properties:

socP100 concerns: socExx Event Specification

socP4 is assessed by: E31 Document

In the 44th joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 37th FRBR - CIDOC CRM Harmonization meeting, the sig reviewed the HW by TV regarding the scope note definitions for socExx Event Specification and socExx Activity Plan, plus the properties linking them to other CRM classes. The reviewing process primarily involved editorial work as well as changes in the content. You may find here the editorial work.

Paris, June 2019
 

Posted by Thanasis on 20/10/2019

Dear all,

I spent a bit of time putting together some scope notes and examples for the Trigger Event Template properties (also attached as a document (in .odt)with an updated diagram). I forwarded these to Stephen only last week so he had not had a chance to review them, but maybe we can do that at the meeting next week. FOL statements and Quantification produced by OntoMe.

All the best,

Thanasis

socP24 specifies material substantial (is specified material substantial)

Domain:

socE4 Trigger Event Template

Range:

S10 Material Substantial

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with an instance of S10 Material Substantial which the template specifies to be used or be present for the planned activity.

Examples:

The disaster plan of the Tate Archives (socE2 Activity Plan) concerns the possible event (socE4 Trigger Event Template) which specifies (socP24 specifies material substantial) the river Thames (S10 Material Substantial / S14 Fluid Body) flooding.

In First Order Logic:

    socP24(x,y) ⊃ socE4(x)

    socP24(x,y) ⊃ S10(y)

socP23 specifies actor (is specified actor of)

Domain:

socE4 Trigger Event Template

Range:

E39 Actor

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with the instance of E39 Actor who is specified by the template to be part of the planned activity.

Examples:

The template specifying my wedding (socExx Trigger Event Template), specifies (socP23 specifies actor) Rev Glyn Tidwell (E39 Actor) to be present to undertake the wedding service.

In First Order Logic:

    socP23(x,y) ⊃ socE4(x)

    socP23(x,y) ⊃ E39(y)

socP22 specifies time-span (is specified time-span of)

Domain:

socE4 Trigger Event Template

Range:

E52 Time-Span

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with the instance of E52 Time-span which is specified by the template as the time-span for the planned activity.

Examples:

The template specifying my wedding (socE4 Trigger Event Template), specifies (socPxx specifies time-span) the the wedding takes place between 14:00 and 23:00 of the 12th of August 2006 (E52 Time-span).

In First Order Logic:

    socP22(x,y) ⊃ socE4(x)

    socP22(x,y) ⊃ E52(y)

socP21 specifies place (is specified place of)

Domain:

socE4 Trigger Event Template

Range:

E53 Place

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with the instance of E53 Place which is specified by the template as the place where the planned activity should take place.

Examples:

The template specifying my wedding (socE4 Trigger Event Template), specifies (socP21 specifies place) the location of Cardiff Castle (E53 Place) for the wedding party to take place.

In First Order Logic:

    socP21(x,y) ⊃ socE4(x)

    socP21(x,y) ⊃ E53(y)

socP19 specifies actor role (is specified actor role of)

Domain:

socE4 Trigger Event Template

Range:

E55 Type

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with the E55 Type of the role of an E39 Actor which is specified by the template. This property does not require the instance of E39 Actor to be specified by socP23 specifies actor (is specified actor of).

Examples:

The template specifying my wedding (socE4 Trigger Event Template) specifies (socP19 specifies actor role) that someone acts as a disc jokey (E55 Type) to play music for the wedding guests.

In First Order Logic:

    socP19(x,y) ⊃ socE4(x)

    socP19(x,y) ⊃ E55(y)

socP18 specifies event type (is specified event type of)

Domain:

socE4 Trigger Event Template

Range:

E55 Type

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with the type (E55 Type) of the E5 Event which would trigger the planned activity. Typically the instance of E5 Event is not known when the planned activity and the trigger template are being produced, so it cannot be specified.

Examples:

The disaster plan of the Tate Archives (socE2 Activity Plan) concerns the event of the river Thames flooding (socE4 Trigger Event Template) which specifies an event of type (socPxx specifies event type) "flood" (E55 Type).

In First Order Logic:

    socP18(x,y) ⊃ socE4(x)

    socP18(x,y) ⊃ E55(y)

socP20 specifies type of thing (is specified type of thing of)

Domain:

socE4 Trigger Event Template

Range:

E55 Type

Quantification:

0,n:0,n

Scope note:

This property associates an instance of socExx Trigger Event Template with the type (E55 Type) of a thing which the template specifies to be used or be present for the planned activity. The instance of the thing can be specified using the property socP24 specifies material substantial (is specified material substantial).

Examples:

No example yet.

In First Order Logic:

    scoP20(x,y) ⊃ socE4(x)

    scoP20(x,y) ⊃ E55(y)

Reference to Issues: