All lowered templates shall have the annotation property
Lowered templates may have the annotation property
This publication shows how this information can be mapped to object properties in templates.
Two use cases shall be distinguished:
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:
In use case #2 the situation becomes a bit more complex, but still doable. The following cases have to be covered:
For each such combination a template is available to map that metadata to lifted templates:
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 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).
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: