Mapping provenance data

latest update: 2014-10-15    

Introduction

All lowered templates shall have the annotation property

  • meta:hasLifecycleActivity, to indicate as a result of which activity the information content of that template was created.
  • meta:valEffectiveDate, to indicate the dateTime that the information content of that template became effective (valid);

Lowered templates may have the annotation property

  • meta:hasStatus, to indicate the status of the information content of that template;
  • meta:valDeprecationDate, to indicate the dateTime that the information content of that template became invalid;

This publication shows how this information can be mapped to object properties in templates.

Use cases

Two use cases shall be distinguished:

  1. the case where exclusively lowered templates are being used

  2. the case where information is being mapped to lifted templates

In use case #1 the metadata apply to the template instances as such. Templates are ClassOfInformationRepresentation AND MultidimensionalObject. In the capacity of ClassOfInformationRepresentation we can use the following templates to detail the metadata applicable to the information content of any template instance:

AnnotationProperty meta:

all lowered templates

hasLifecycleActivity

applicable template below

valEffectiveDate

ActivityCausesEffectiveClass

hasStatus

ActivityCausesStatusedClass

valDeprecationDate

ActivityCausesDeprecatedClass

In use case #2 the situation becomes a bit more complex, but still doable. The following cases have to be covered:

  1. the template is about a class-of-temporal-part of one instance of ClassOfIndividual;
  2. the template is about classes-of-temporal-part of two related instances of ClassOfIndividual (in most cases "templates for structure", e.g. for assembly);
  3. the template is about a temporal part of one instance of PossibleIndividual;
  4. the template is about temporal parts of two related instances of PossibleIndividual.

For each such combination a template is available to map that metadata to lifted templates:

AnnotationProperty

one ClassOfIndividual

two related ClassOfIndividual's

 one Individual (temporal part)

two related PossibleIndividual's

hasLifecycleActivity

in applicable template below in applicable template below in applicable template below in applicable template below

valEffectiveDate

ActivityCausesEffectiveClass

ActivityCausesTwoRelatedEffectiveClasses

ActivityCausesBegunIndividual

ActivityCausesTwoRelatedBegunIndividuals

hasStatus

ActivityCausesStatusedClass

ActivityCausesTwoRelatedStatusedClasses

ActivityCausesStatusedIndividual

ActivityCausesTwoRelatedStatusedIndividuals

valDeprecationDate

ActivityCausesDeprecatedClass

ActivityCausesTwoRelatedDeprecatedClasses

ActivityCausesEndedIndividual

ActivityCausesTwoRelatedEndedIndividuals

An example for mapping to a lifted template will be given below.

Example for Lowered Templates for Class

Below is shown how this mapping can be done.

 

Assumed is that the lower template already existed, and that the upper template is created, thereby using the metadata of the lower template. The dateTime is used for the RepresentationOfGregorianDateAndUtcTime only when subsequently mapping this to lifted template format.

Project Controls (Provenance)

Since the lifecycle activity is now made explicit, it can be used in activity-based templates to formally model the provenance information such as:

  • the author of the information;
  • the computer system used;
  • the labor costs involved;
  • etc

The ClassOfActivity that is the "LifecycleActivity" can be any activity class in any WBS (Work Breakdown Structure).

Example of mapping to Lifted Templates for Class

The example below shows the same template as above, but now as lifted templates.

It is suggested to identify all internal objects in the lifted template as follows: ID-of-lowered-template_serial number in template, as shown in the above graph.

NOTE - This lifting of templates is different from what may evolve from the work on ISO 15926 Part 12.

Example for Lowered Templates for Individual

 

Example for Lifted Templates for Individual

 

Two related Classes or Individuals

In templates where two instances of ClassOfIndividual or of PossibleIndividual are related to each other, these become effective/begun, statused, or deprecated/ended simultaneously. The templates ActivityCausesTwoRelatedEffectiveClasses / ActivityCausesTwoRelatedBegunIndividuals , etc are to be (see table above).

dateTime-only required

In cases where, for lifted templates, the lifecycle activity is not required, but only the dateTime of effectiveness, then these extra templates are not required for templates about PossibleIndividual, since these have the time already incorporated: