representing_experience

Template:— representing_experience_type (rep_expnce_typ)
Capability:representing_person_organization_typical

Date: 2008/02/21 16:29:46
Revision: 1.4

Cover Contents Description Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues in situ

This section specifies the template representing_experience_type.

NOTE The template has been defined in the context of the capability representing_person_organization_typical which provides an overall description of the relevant parts of the ISO 10303-239 information model and a description of related templates.

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 type of experience.

Model diagrams

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

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

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_experience_type template

Input parameters

The following input parameters are defined for this template:

expnce_type_class_name (Type='CLASS')

The name of the External_class that determines the type of qualification being represented.

The following classes and their sub-classes can be used:

classifications: "Experience_type" (urn:plcs:rdl:std:Experience_type)

expnce_type_ecl_id (Default=urn:plcs:rdl:std,Type='URN')

The identification of the External_class_library storing the External_class given by the input parameter @expnce_type_class_name.

Reference parameters

The following reference parameters are defined for this template:

expnce_type(Type='ENTITY (Experience_type)')

Allow the Experience_type entity instantiated in this path to be referenced when this template is used.

Note: The Experience_type entity can be referenced in a template path by:

%^target = $representing_experience_type.expnce_type%

where target is the parameter to which the Experience_type is bound.

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Experience_type

Each instance of the entity (Experience_type) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_experience_type) namely: expnce_type_class_name, expnce_type_ecl_id.
The instance is referenced by the following template parameter: expnce_type.

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.

Experience_type

-- Mark the Experience_type entity as
-- referable when this template is used by binding it to the reference
-- parameter qual_type
%^expnce_type = Experience_type%
Experience_type.name = '/IGNORE'
Experience_type.description = '/IGNORE'

-- provide the type of person by classifying the entity Experience_type
/assigning_reference_data(
    items=^expnce_type,
    class_name=@expnce_type_class_name,
    ecl_id=@expnce_type_ecl_id)/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Experience_type.name	'/IGNORE'	—
Experience_type.description	'/IGNORE'	—

Instance diagrams

The instance diagram in Figure 3 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/representing_experience_type(expnce_type_class_name='Mechanical_design', expnce_type_ecl_id='urn:plcs:rdl:sample')/

(an illustration of the consolidated representing_experience_type template is shown in Figure 4 below.)

Figure 3 — Entities instantiated by representing_experience_type template

The instance model in STEP ASCII exchange file format (ISO 10303 Part 21 syntax) is:


          #1 = EXPERIENCE_TYPE('/IGNORE','/IGNORE',$);
          #3 = CLASSIFICATION_ASSIGNMENT(#5,(#1),'/IGNORE');
          #5 = EXTERNAL_CLASS('/NULL','Mechanical_design','/IGNORE',#6);
          #6 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample',$);

The instance model in STEP XML exchange file format (ISO 10303 Part 28 ed.2 syntax) is:

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_experience_type(expnce_type_class_name='Mechanical_design', expnce_type_ecl_id='urn:plcs:rdl:sample')/

Figure 4 — Instantiation of representing_experience_type template

Characterizations

The following section details how the representing_experience_type template can be optionally characterized by assigning other constructs to it. These are characterizations commonly applied to the template. The ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.

The following characterizations may apply:

Characterization Assigning code

NOTE this characterization is optional.

A Experience_type may also be determined by codes as described in the template assigning_code. A description of the code used to determine the experience type may then be provided as a description associated with the code, as described under the assigning_code template characterization section.

NOTE The assignment of codes is described the capability C093: assigning_codes.