Application module: Event ISO/TS 10303-1064:2018-11(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
    3.1 Terms and definitions
    3.2 Abbreviated terms

4 Information requirements
   4.1 Required AM ARMs
   4.2 ARM type definition
   4.3 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM type definitions

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
F Application module implementation and usage guide
G Change history
Bibliography
Index

Annex F
(informative)

Application module implementation and usage guide

NOTE    This clause provides guidance about the tracking of planned and actual dates of events. Although the mentioned entity data types are defined in the ARM, the recommendations also apply with the MIM entity data types.

There are two ways to use the Event entity to record the actual occurrence of a planned event:

  1. the instance of Event is edited so that the actual occurrence date is recorded in the actual_start_date attribute;
  2. a new instance of Event is created, with only the actual_start_date attribute filled in, and related back to the event it is an occurrence of through an instance of Event_relationship with relation_type = "actualization".

Interpretations of various usages of Event are given in the table below. The first column shows whether there is a planned_start_date set, the second whether there is an actual_start_date, the third shows whether there is at least an actual event which is related with an instance of Event_relationship with relation_type = "actualization". The last column provides an interpretation of the instantiation case.

NOTE    Interpretation of instances of Event_relationship whose relation_type is not 'actualization' is not considered nor impacted by the following table.

Table F.1 — Interpretation of instances of Event_relationship with relation_type 'actualization'.

planned start date

actual start date

related actual event

interpretation
no no no a description of a type of event, with nothing said about its possible or actual occurrence
no no yes may be used to describe a generic event and its actual occurrences
no yes no actual, or considered as such, event
no yes yes an actual event that has one or more actual events. Not recommended because meaningless
yes no no a planned event for which no actual occurrence has been recorded
yes no yes a planned event for which one or more actual occurrences have been recorded
yes yes no an event for which it was not considered necessary to record planned date and actual date in distinct related instances of Event
yes yes yes mixed approach to represent planned and actual events. Not recommended


© ISO 2018 — All rights reserved