representing_person

The use of template,representing_person_typical, has been deprecated since 2008-01-25 Until further notice.

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.

Note:

This template is subject for change, and therefore being deprecated until further notice. The current content of this template has been copied to the template referencing_person_typical.

This template describes how to represent a type of person without its definition.

NOTE The Type_of_person_definition has been omitted from this template. The definition(s) for a type of person should be defined within the class (reference data) being used to determine the type of person.

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

The following input parameters are defined for this template:

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

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

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

The following reference parameters are defined for this template:

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

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

%^target = $representing_person_typical.type_of_pers%

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

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Type of person

Each instance of the entity (Type_of_person) within the data set shall be uniquely identified by a combination of the following parameters on this template (representing_person_typical) namely: type_of_pers_class_name, type_of_pers_ecl_id.
The instance is referenced by the following template parameter: type_of_pers.

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.

Type_of_person

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

-- provide the type of person by classifying the entity Type_of_person
/assigning_reference_data(
    items=^type_of_pers,
    class_name=@type_of_pers_class_name,
    ecl_id=@type_of_pers_ecl_id)/

The following entities are instantiated with attributes as specified:

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

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

/representing_person_typical(type_of_pers_class_name='Welder', type_of_pers_ecl_id='urn:plcs:rdl:sample')/

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

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


          #1 = TYPE_OF_PERSON('/IGNORE','/IGNORE',());
          #3 = CLASSIFICATION_ASSIGNMENT(#4,(#1),'/IGNORE');
          #5 = EXTERNAL_CLASS('/NULL','Welder','/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_person_typical(type_of_pers_class_name='Welder', type_of_pers_ecl_id='urn:plcs:rdl:sample')/

The following section details how the representing_person_typical 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 descriptor

NOTE this characterization is optional.

Additional descriptions, notes etc for the defined Type_of_person may be assigned using the assigning_descriptor template.