Template:— representing_value_w_tolerances (rep_val_tol) Date: 2008/03/10 09:26:28
Revision: 1.25
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssues

Issue raised against: representing_value_w_tolerances

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: 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-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: (Tim Turner 2008-03-06)
Fixed. By product is the requirement to make it a reference parameter.

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: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 14: Characterization section does not fully compy with this. E.g. references to Person, Organization etc.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 24: Description includes an empty example.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 26: 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: (Tim Turner 2008-03-06)
EXPRESS G Updated

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

Review issue. Review items 26, 41: Entity supertypes are not shown in the EXPRESS-G diagram. The Express model is not consistent with AP239 ARM.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review items 48, 58: Reference parameter ‘item’ is missing.
Comment: (Tim Turner 2008-03-06)
Item is not a reference parameter of this template - therefore removed.

Closed issue Issue: GYL-7 by Leif Gyllstrom (2007-12-10) minor_technical issue
Resolution: Reject. Status: closed

Review issue. Review item 51: Input parameter si_unit. Do we need to bring in explanations on Part 21 and Part 28 representations in every template that just passes on the values to another template.
Comment: (Rob Bodington 08-02-27)
There is now a note explaining the Part 21 and Part 28 representation issue. This is included as agreed "Notes from issue resolution teleocn 2007-17-12"

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

Review issue. Review item 53: Input parameter context. Should we be able to reuse representation contexts that are being defined as subclasses of the class "Representation_context" ?
Comment: (Rob Bodington 08-02-27)
Changed to Representation_context as per "Notes from issue resolution teleocn 2007-17-12"

Closed issue Issue: GYL-9 by Leif Gyllstrom (2007-12-10) minor_technical issue
Resolution: Reject. Status: closed

Review issue. Review item 62: An Entity is assigned to the input parameter "items" of the template assigning_reference_data. Entity is not in the list of allowed assignments.
Comment: (Tim Turner 2008-03-06)
As a subtype of Representation_context, the classification_item may be assigned to a Numerical_representation_context.

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

Review issue. Review item 67: Kilogram is si unit, i.e si_unit shall be set to true.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 70: Shaded are is missing for the graphical template instantiation.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 72: The entity instantiation diagram is not consistent with the textual example. ‘lower_limit’ is set to -4 and not 4.0. ‘unit’ is set to Hour and not Kilogram. If Kilogram is used then shall ‘si_unit’ be set to true.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 82: The following input parameters in the instantiated template needs to be revised: ‘lower_limit’, ‘upper_limit’, ‘si_unit’ and ‘context_ecl_id’. If Kilogram is used then shall si_unit be set to true.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 88: See open issue RBN-2.
Comment: (Tim Turner 2008-03-06)
See response to RBN-2

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

Review issue. Review item 90: The EXPRESS-G diagram does not comply with AP239 ARM. It does not show superclasses and inheritance, but is an EXPRESS-G version of an instance diagram.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 91: Characterizations should comply with Peter Bergstom’s notes in “Properties in DEXlib meeting notes 2007-08-13.doc”
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 91: Provide examples for each defined characterization.
Comment: (Tim Turner 2008-03-06)
Fixed.

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

Review issue. Review item 30: No expicit relation between input parameters and template attributes (e.g. arrows).
Comment: (Tim Turner 2008-03-06)
Fixed.

Closed issue Issue: GYL-19 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="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>
Comment: (Rob Bodington 08-02-27)
rrecetd

Closed issue Issue: AMS-1 by Ann Meads (08-02-01) minor_technical issue
Resolution: Accept. Status: closed

The lower_limit input parameter should be negative to be consistent with product_property_w_tolerances. Add a comment such as: The lower tolerance limit of the property value. This value should always be negative as upper_limit and lower_limit represent offsets from value, specifying a range of values defined as [value+lower_limit, value+upper_limit]. Change the example instantiation to a negative number for lower_limit.
Comment: (Tim Turner 2008-03-06)
Fixed.

Closed issue Issue: JNN-1 by Johan Nielsen (2008-02-25) editorial issue
Resolution: Accept. Status: closed

In the Instance diagrams section the lower_limit is set to 4.0 in the textual representation, but shown as -4.0 in Figure 3 and 0 in Figure 4.
Comment: (Tim Turner 2008-03-06)
Fixed.

Closed issue Issue: JNN-1 by Johan Nielsen (2008-02-25) editorial issue
Resolution: Accept. Status: closed

In the Instance diagrams section the upper_limit is set to 0.5 in the textual representation, but shown as 0 Figure 4.
Comment: (Tim Turner 2008-03-06)
Fixed.

Closed issue Issue: RBN-3 by Rob Bodington (08-03-10) minor_technical issue
Resolution: Accept. Status: closed

The characterization sections in the templates make incorrect references to Property_value_representation (reference parameter ^representation in template representing_value_range). and Property_value_representation (reference parameter ^representation in template representing_value_with_unit). It should be the reference parameter on this template
Comment: (Rob Bodington 08-03-10)
Corrected