representing_value_limit

Template:— representing_value_limit (rep_limit)
Capability:representing_property_value_ranges

Date: 2008/03/07 06:34:59
Revision: 1.24

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

Issue raised against: representing_value_limit

GENERAL issues

Issue: RBN-1 by Rob Bodington (07-01-02) minor_technical issue
Resolution: Accept. Status: closed

The input parameters that are enumerations should have the enumeration specified.

Comment: (Rob Bodington 07-01-02)
Corrected.

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.

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

There should be a uniqueness constraint on the Numerical_representation_context

Comment: (Ann Meads 08-02-18)
Corrected.

Issue: TRO-2 by Trisha Rollo (20-11-07) minor_technical issue
Resolution: Accept. Status: closed

Seems to have possible duplication with other templates Representing_numeric_property. Only difference is that one uses date and the other uses time. Example is same.

Comment: (Ann Meads 08-02-27)
It is felt that the differences still warrant separate templates.

Issue: AMS-1 by Ann Meads (20-11-07) editorial issue
Resolution: Accept. Status: closed

Make parameter values consistent in instantiation diagrams and associated text.

Comment: (Tim Turner 08-02-27)
Fixed.

Issue: AMS-2 by Ann Meads (20-11-07) editorial issue
Resolution: Accept. Status: closed

Diagram 5 is missing and text is repeated in characterization section.

Comment: (Ann Meads 08-02-27)
No longer an issue.

Issue: GYL-1 by Leif Gyllstrom (2007-12-17) major_technical issue
Resolution: Accept. Status: closed

The ‘Numerical_ representation_context’ entity has two attributes which are not shown in the EXPRESS-G diagram (accuaracies and units). Those should be added, with a comment that they are not being instantiated by this template.

Comment: (Ann Meads 08-02-27)
Have included attributes in diagram along with supertypes for issue GYL-2. Adding a note would make it inconsistent with other templates.

Issue: GYL-2 by Leif Gyllstrom (2007-12-17) major_technical issue
Resolution: Accept. Status: closed

Entity supertypes are not shown in the EXPRESS-G diagram. The Express model is not consistent with AP239 ARM.

Comment: (Ann Meads 08-02-27)
Recreated diagram with supertypes.

Issue: GYL-3 by Leif Gyllstrom (08-01-24) minor_technical issue
Resolution: Accept. Status: closed

Declaration of input parameter value should be changed from:
< param_in name="limit" 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="limit" 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>

Comment: (Ann Meads 08-02-27)
Done.