Template:— representing_value_with_unit (rep_val_unit)
Capability:representing_value_with_unit		 Date: 2009/04/09 15:05:20
Revision: 1.23
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssuesin situ

Issue raised against: representing_value_with_unit

GENERAL issues

Open issue Issue: GYL-2 by Leif Gyllstrom (2007-12-10) editorial issue
Resolution: Accept. Status: open

Review issue. Review item 24: The example is not obvious. For me it was even confusing.

Open issue Issue: GYL-3 by Leif Gyllstrom (2007-12-10) editorial issue
Resolution: Accept. Status: open

Review issue. Review item 24: Elaborate on the difference between this template and the template representing_numerical_item.

Open issue Issue: GYL-4 by Leif Gyllstrom (2007-12-10) minor_technical issue
Resolution: Accept. Status: open

Review issue. Review item 38: There is no attribute name associated with the assignment of the template "assigning_ reference_data"

Open issue Issue: GYL-5 by Leif Gyllstrom (2007-12-10) minor_technical issue
Resolution: Accept. Status: open

Review issue. Review item 62: An Entity is assigned to the input parameter "items" of the template assigning_reference_data. Entity is not within the list of allowed assignments.

Open issue Issue: GYL-6 by Leif Gyllstrom (2007-12-10) editorial issue
Resolution: Accept. Status: open

Review issue. Review item 70: Shaded are is missing for the graphical template instantiation.

Open issue Issue: GYL-7 by Leif Gyllstrom (2007-12-10) minor_technical issue
Resolution: Accept. Status: open

Review issue. Review item 88: See issue RBN-1.

Open issue Issue: GYL-8 by Leif Gyllstrom (08-01-24) minor_technical issue
Resolution: Accept. Status: open

Declaration of input parameter value should be changed from:
< param_in name="value" type="SELECT" select_type="measure_value">
<description>
The value of the property.
The datatype must also be indicated in this parameter, e.g.
"ANY_NUMBER_VALUE(5)".
</description>
</param_in>
to something like:
<param_in name="value" type="TYPE" defined_type="any_number_value">
<description>
The value of the property. The datatype is always 'any_number_value'
and should not be registered together with the value, i.e. enter the
value as a number, without datatype.
</description>
</param_in>

GENERAL issues

Closed issue Issue: PBM-1 by Peter Bergström (2007-02-16) minor_technical issue
Resolution: Accept. Status: closed

The necessity of chosing a datatype for the input parameter 'value' is not made clear in the parameter definition. It appears that value can be "5" or similar, when in fact the datatype must be given as well, e.g. "ANY_NUMBER_VALUE(5)".
Comment: (Peter Bergström 2007-02-16)
Fixed by editing the parameter description. I also harmonized the description of parameter si_unit with other templates.

Closed issue Issue: DNV-41 by Sylvia Schwab on behalf of DNV (07-03-07) minor_technical issue
Resolution: Accept. Status: closed

Does the template like representing_value_with_unit use sub types of the entity Unit or only sub types of the class "Unit"?

Comment: (Peter Bergström 2007-04-12)
The capability representing_value_with_unit discuss the deprecated use of subtypes of Unit. This template only provides the entity Unit, none of its subtypes. It does provide the means to specify subtypes using external reference data, though.

Closed issue Issue: DNV-42 by Sylvia Schwab on behalf of DNV (07-03-07) minor_technical issue
Resolution: Accept. Status: closed

Unit can be represented as a code value with description/encoding system. The template for representing_value_with_unit and representing_numerical_item should include this.

Proposal: Add optional representing_code (new template proposed as part of assigning_identifier (C001)) to unit in representing_value_with_unit and representing_numerical_item.

Comment: (Rob Bodington 07-04-13)
The unit is provided by reference data. It is possible to assign reference data by either assigning_code or assigning_reference data. Hence, this is an issues against assigning_code or assigning_reference data.

Closed issue Issue: TRO-1 by Trisha Rollo (2007-06-25) minor_technical issue
Resolution: Accept. Status: closed

short name does not conform to template checklist of valid values
Comment: (Trisha Rollo 2007-06-25)
amended

Closed issue Issue: RBN-1 by Rob Bodington (07-08-09) minor_technical issue
Resolution: Accept. Status: closed

There should be a uniqueness constraint against Unit
Comment: (Rob Bodington 08-03-10)
Added

Closed issue Issue: GYL-1 by Leif Gyllstrom (2007-12-10) editorial issue
Resolution: Accept. Status: closed

Review issue. Review item 13: Figures under the section Instance diagrams are hard to read. Enlarge
Comment: (Rob Bodington 08-03-10)
Enlarged