Template:— representing_value_range (rep_range) Date: 2008/03/07 03:50:25
Revision: 1.26

This section specifies the template representing_value_range.

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 property value range (with units) for any property.

EXAMPLE    The weight of an item may range in weight from 5.05 down to 4.95 kilgrames.

The range (in terms of upper and lower values) of a property value defined in specific units (e.g. time, length etc..) that may be associated with an item.

NOTE    The specification and definition of the property and the item to which it is associated, are outside the scope of this template. This template, however, defines the representation andvalues (range of) that may be associated with such a property.

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


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

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

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 representing_value_range template, related to a resource property

Figure 2 —   The graphical representation of representing_value_range template, related to a resource property

Input parameters
The following input parameters are defined for this template:
upper_limit (Type= 'TYPE (any_number_value)' )
The upper limit value of the property. The datatype must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".
lower_limit (Type= 'TYPE (any_number_value)' )
The lower limit value of the property. The datatype must also be indicated in this parameter, e.g. "ANY_NUMBER_VALUE(5)".
unit (Type='CLASS')
The class name of the unit in which the value is expressed.
The following classes and their sub-classes can be used:
classifications: "Unit" (urn:plcs:rdl:std:Unit)
unit_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 @unit.
si_unit (Default=false,Type='BOOLEAN')
Value should be set to true if the unit is a SI base unit defined by ISO, i.e. kilogram (kg) for Mass, second (s) for Time, metre (m) for Displacement, ampere (A) for Electrical current, kelvin (K) for Temperature, mole (mol) for Amount of substance, and candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 and Part 21 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false".
context (Type='CLASS')
The name of the class being used to classify the representation context (Numerical_representation_context) of the property.
The following classes and their sub-classes can be used:
classifications: "Representation_context" (urn:plcs:rdl:std:Representation_context)
context_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 @context.
Reference parameters
The following reference parameters are defined for this template:
representation(Type='ENTITY (Property_value_representation)')
Allow the Property_value_representation entity instantiated in this path to be referenced when this template is used.
Note: The Property_value_representation entity can be referenced in a template path by:
%^target = $representing_value_range.representation%
where target is the parameter to which the Property_value_representation is bound.
num_rep_cntxt(Type='ENTITY (Numerical_representation_context)')
Allow the Numerical_representation_context entity instantiated in this path to be referenced when this template is used.
Note: The Numerical_representation_context entity can be referenced in a template path by:
%^target = $representing_value_range.num_rep_cntxt%
where target is the parameter to which the Numerical_representation_context is bound.
Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:
Unique constraint: Unique numerical representation context
There shall be at most one instance of the entity (Numerical_representation_context) within the data set uniquely identified by a combination of the following parameters on this template (representing_value_range) namely: context, context_ecl_id.
The instance is referenced by the following template parameter: num_rep_cntxt.
There will be one numerical context for the representation of a value.
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 Reading Capability Templates help section.
-- Instantiate Property_value_representation entity
Property_value_representation

-- Set the Property_value_representation attributes id, name and description to be ignored
Property_value_representation.id = '/IGNORE'
Property_value_representation.name = '/IGNORE'
Property_value_representation.description = '/IGNORE'

-- Bind the Property_value_representation to the parameter ^representation.
-- The parameter is a reference parameter so the Property_value_representation
-- entity can be referred to when this template is used.
%^representation = Property_value_representation%

-- Instantiate Numerical_representation_context and assign
%^num_rep_cntxt = Numerical_representation_context%

-- Set the Numerical_representation_context attributes id and kind to be ignored
Numerical_representation_context.id = '/IGNORE'
Numerical_representation_context.kind = '/IGNORE'

-- Property_value_representation at it
^representation.context_of_items -> ^num_rep_cntxt

-- Assign reference data for kind of Numerical_representation_context
/assigning_reference_data(
    items=^num_rep_cntxt,
    class_name=@context,
    ecl_id=@context_ecl_id)/

-- Instantiate Value_range and assign
-- Property_value_representation to it
^representation.items -> Value_range

-- Set the Value_range attribute name to be ignored
Value_range.name = '/IGNORE'

-- Instantiate template representing_numerical_item
-- for upper limit
/representing_numerical_item(
    value= @upper_limit,
    unit= @unit,
    unit_ecl_id= @unit_ecl_id,
    si_unit= @si_unit)/

-- Bind ref param ^item in just instantiated template
-- representing_numerical_item to ref param ^item in this template,
-- and point attribute Value_range.upper_limit to it
%^upper_item = $representing_numerical_item.item%

-- Instantiate template representing_numerical_item
-- for lower limit
/representing_numerical_item(
    value= @lower_limit,
    unit= @unit,
    unit_ecl_id= @unit_ecl_id,
    si_unit= @si_unit)/

-- Bind ref param ^item in just instantiated template
-- representing_numerical_item to ref param ^item in this template,
-- and point attribute Value_range.lower_limit to it
%^lower_item = $representing_numerical_item.item%
Value_range.lower_limit -> ^lower_item
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Property_value_representation.id '/IGNORE' Representation.id
Property_value_representation.name '/IGNORE' Representation.name
Property_value_representation.description '/IGNORE' Representation.description
Numerical_representation_context.id '/IGNORE' Representation_context.id
Numerical_representation_context.kind '/IGNORE' Representation_context.kind
Value_range.name '/IGNORE' Representation_item.name
Instance diagrams
The instance diagram in Figure  3 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/representing_value_range(upper_limit='ANY_NUMBER_VALUE(5.05)', lower_limit='ANY_NUMBER_VALUE(4.95)', unit='kilogram', unit_ecl_id='urn:plcs:rdl:std', si_unit='.T.', context='Representation_context', context_ecl_id='urn:plcs:rdl:std')/
(an illustration of the consolidated representing_value_range template is shown in Figure 4 below.)


Figure 3 —  Entities instantiated by representing_value_range template

Figure 3 —  Entities instantiated by representing_value_range 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_value_range(upper_limit='ANY_NUMBER_VALUE(5.05)', lower_limit='ANY_NUMBER_VALUE(4.95)', unit='kilogram', unit_ecl_id='urn:plcs:rdl:std', si_unit='.T.', context='Representation_context', context_ecl_id='urn:plcs:rdl:std')/


Figure 4 —  Instantiation of representing_value_range template

Figure 4 —  Instantiation of representing_value_range template

Characterizations
The following section details how the representing_value_range 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 EXPRESS-G diagram in Figure 5 shows the possible characterizations of the template "representing_value_range".


Figure 5 —  Characterizations for representing_value_range template

Figure 5 —  Characterizations for representing_value_range template

The following characterizations may apply:
Characterization Assigning time (and Dates)

NOTE   this characterization is optional.

Time (and dates) can be associated with the assignment of a property value representation as shown in Figure 5, by using the templates assigning_time. An example of this is provided below.



Figure 6 —  Characterization by date of representing_value_range template

Figure 6 —  Characterization by date of representing_value_range template

The date of creation of the property value representation is represented by using the template assigning_time to assign a date and time to Property_value_representation (reference parameter ^representation in template representing_value_range). The date and time assignment is classified as: "Date_actual_creation" (urn:plcs:rdl:std:Date_actual_creation) to indicate that it is the date (and time) when the property value representation was actually created. This is illustrated in Figure 6.

Other dates may be assigned instead.

Characterization Assigning organization or person

NOTE   this characterization is optional.

An Organization (or a Person_in_organization) can be associated with the property value representation (see the ^representation reference parameter), as in Figure 5. The creating organization is represented by using the template assigning_organization or assigning_person_in_organization assigned to Property_value_representation (reference parameter ^representation in template representing_value_range). The assignment of the organization (Organization_or_person_in_organization_assignment) is classified as: "Creator_of" (urn:plcs:rdl:std:Creator_of) to indicate that this organization created the property value representation. This is illustrated in Figure 7.



Figure 7 —  Characterization by organization or person of representing_value_range template

Figure 7 —  Characterization by organization or person of representing_value_range template

Other roles of an organization with regard to a property value representation may be assigned instead.

© OASIS 2008 — All rights reserved