Template:— representing_task_version_relationship (rep_task_ver_rel) Date: 2009/03/10 07:33:45
Revision: 1.4

This section specifies the template representing_task_version_relationship.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes how to represent a relationship between two Task_method_versions.

Model diagrams
The EXPRESS-G diagram in Figure 1 shows the templates and EXPRESS entities that are required to represent the template "representing_task_version_relationship". The text highlighted in blue shows the template parameters.


Figure 1 —  An EXPRESS-G representation of the Information model for representing_task_version_relationship

Figure 1 —  An EXPRESS-G representation of the Information model for representing_task_version_relationship

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure  2 below.


Figure 2 —  The graphical representation of the representing_task_version_relationship template

Figure 2 —  The graphical representation of the representing_task_version_relationship template

Input parameters
The following input parameters are defined for this template:
relating_task_ver (Type= 'ENTITY (Task_method_version)' )
The Task_method_version which relates to another Task_method_version.
related_task_ver (Type= 'ENTITY (Task_method_version)' )
The Task_method_version that is being related.
rel_class_name (Type='CLASS')
Subclass of "Task method version relationship" (urn:plcs:rdl:std:Task method version relationship)
The following classes and their sub-classes can be used:
classifications: "Task_method_version_relationship" (urn:plcs:rdl:std:Task_method_version_relationship)
rel_ecl_id (Default=urn:plcs:rdl:std,Type='URN')
The identifier of the External_class_library storing the definition of the class referenced by the parameter @rel_class_name.
Reference parameters
The following reference parameters are defined for this template:
task_ver_rel(Type='ENTITY (Task_method_version_relationship)')
Allow the Task_method_version_relationship entity instantiated in this path to be referenced when this template is used.
Note: The Task_method_version_relationship entity can be referenced in a template path by:
%^target = $representing_task_version_relationship.task_ver_rel%
where target is the parameter to which the Task_method_version_relationship is bound.
Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:
Unique constraint: Task version relationship
Each instance of the entity (Task_method_version_relationship) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_task_version_relationship) namely: relating_task_ver, related_task_ver, rel_class_name, rel_ecl_id.
The instance is referenced by the following template parameter: task_ver_rel.
Instantiation path
The instantiation path shown below specifies the entities that are to be instantiated by the template.
A description of templates and the syntax for the instantiation path is provided in the Templates Help/Information section.
Task_method_version_relationship

-- Mark the Task_method_version_relationship entity as
-- referable when this template is used by binding it to the reference
-- parameter task_ver_rel
%^task_ver_rel = Task_method_version_relationship%
Task_method_version_relationship.name = '/IGNORE'
Task_method_version_relationship.description = '/IGNORE'
Task_method_version_relationship.relating_method -> @relating_task_ver
Task_method_version_relationship.related_method -> @related_task_ver

-- provide the role of the realization by classifying the Task_method_version_relationship
/assigning_reference_data(
    items=^task_ver_rel,
    class_name=@rel_class_name,
    ecl_id=@rel_ecl_id)/
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Task_method_version_relationship.name '/IGNORE' Activity_method_relationship.name
Task_method_version_relationship.description '/IGNORE' Activity_method_relationship.description
Instance diagrams
The instance diagram in Figure  3 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/representing_task_version_relationship(relating_task_ver='#1', related_task_ver='#2', rel_class_name='Supersedes', rel_ecl_id='urn:plcs:rdl:sample')/
(an illustration of the consolidated representing_task_version_relationship template is shown in Figure 4 below.)


Figure 3 —  Entities instantiated by representing_task_version_relationship template

Figure 3 —  Entities instantiated by representing_task_version_relationship template

The instance diagram in Figure 4 shows the graphic symbol for the template that is to be used in other instance diagrams. The example template is:
/representing_task_version_relationship(relating_task_ver='#1', related_task_ver='#2', rel_class_name='Supersedes', rel_ecl_id='urn:plcs:rdl:sample')/


Figure 4 —  Instantiation of representing_task_version_relationship template

Figure 4 —  Instantiation of representing_task_version_relationship template

Characterizations
No common characterizations of the template representing_task_version_relationship have been identified. However, the ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.

© OASIS 2010 — All rights reserved