Template:— resource_property_limit (res_prp_limit) Date: 2009/06/09 13:11:46
Revision: 1.24
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssues

Issue raised against: resource_property_limit

GENERAL issues

Closed issue Issue: RBN-1 by Johan Nielsen (2007-03-26) editorial issue
Resolution: Accept. Status: closed

The reference parameter prop_repr declaration is missing in some diagrams. It should be declared and bound to Resource_property_representation.
Comment: (Johan Nielsen 2007-03-26)
Fixed by editing the diagrams.

Closed issue 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.

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: GYL-1 by Leif Gyllstrom (07-12-09) minor_technical issue
Resolution: Accept. Status: closed

Review issue, review item 6: Master attributes are missing throughout the template.
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Added

Closed issue Issue: GYL-2 by Leif Gyllstrom (07-12-09) major_technical issue
Resolution: Accept. Status: closed

Review issue, review items 7 and 8: There are no supporting editable files available under the dvlp folder.
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Added

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

Review issue, review item 14: References within the characterization section does not comply with this rule. E.g. characterization assigning person or organization where person and organization is stated without hyperlinks to the respective entity.
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

Closed issue Issue: GYL-4 by Leif Gyllstrom (07-12-09) editorial issue
Resolution: Accept. Status: closed

Review issue, review item 24: The meaning of limit can be further explained.
Comment: ( )
Comment: (Rob Bodington 08-02-26)
Now: The qualified numerical value representing either the lower limit or the upper limit of the property.

Closed issue Issue: GYL-5 by Leif Gyllstrom (07-12-09) minor_technical issue
Resolution: Accept. Status: closed

Review issue, review item 28: There is an additional characterization using the assigning_reference_ data template
Comment: ( )
Comment: (Rob Bodington 08-02-26)

Closed issue Issue: GYL-6 by Leif Gyllstrom (07-12-09) editorial issue
Resolution: Accept. Status: closed

Review issue, review item 29: Different fonts for parameters in the diagram
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

Closed issue Issue: GYL-7 by Leif Gyllstrom (07-12-09) minor_technical issue
Resolution: Accept. Status: closed

Review issue, review item 30: No explicit relation between input attributes and constructs in the diagram (e.g. by arrows).
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

Closed issue Issue: GYL-8 by Leif Gyllstrom (07-12-09) editorial 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 ?
Comment: ( )
Comment: (Rob Bodington 08-02-26)
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-9 by Leif Gyllstrom (07-12-09) minor_technical issue
Resolution: Accept. Status: closed

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

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

Review issue, review item 52: Type = "ENUMERATION" not in the list of allowed types.
Comment: ( )
Comment: (Rob Bodington 08-02-26)
This is is an issue against the check list. ENUMERATION is acceptable

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

Review issue, review item 68: Value of "qualifier" is in bold text which is not consistent with the textual example.
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

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

Review issue, review item 68: Value of limit shall contain "any_value_number()"
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

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

Review issue, review item 82: Value of "qualifier" is in bold text which is not consistent with the textual example.
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

Closed issue Issue: GYL-14 by Leif Gyllstrom (07-12-09) editorial issue
Resolution: Accept. Status: closed

Review issue, review item 82: Value of limit shall contain "any_value_number()"
Comment: ( )
Comment: (Rob Bodington 08-02-28)
Corrected

Closed issue Issue: GYL-15 by Leif Gyllstrom (07-12-09) editorial issue
Resolution: Reject. Status: closed

Review issue, review item 90: Figures within the characterization section should use the template representation for resource_property_ limit, and not the ExpressG diagrams.
Comment: ( )
Comment: (Rob Bodington 08-02-26)
This is consistent with a number of other templates

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

Characterization should comply with Peter Bergstrom paper on property characterization defined during the DEX3 harmonization workshops. See uploaded document : 'Properties in DEXlib meeting notes 2007-08-13.doc'.
Comment: ( )
Comment: (Rob Bodington 08-02-28)
It appears to be

Closed issue Issue: GYL-17 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: (Rob Bodington 08-02-26)
Corrected

Closed issue Issue: PHX-1 by Patrick Houbaux (08-04-16) major_technical issue
Resolution: Accept. Status: closed
Registered as a ballot comment by:

Wrong type of input parameter "property". It should be RESOURCE_PROPERTY instead of ASSIGNED_PROPERTY
Comment: (Leif Gyllstrom 2009-06-08)
Fixed.

Closed issue Issue: PBM-2 by Peter Bergström (2009-03-23) editorial issue
Resolution: Accept. Status: closed

Parameter @unit is incorrectly described, it is not a class of a unit, it is a name of a unit. The description of parameter @unit_ecl_id needs also changing.
A default value for @context would also be good, suggest Numerical_representation_context.
Comment: (Peter Bergström 2009-03-23)
Fixed both issues.

Closed issue Issue: GYL-17 by Leif Gyllstrom (09-06-09) minor_technical issue
Resolution: Accept. Status: closed

Both instance diagrams shows the entity instantiation.
Comment: (Leif Gyllstrom 2009-06-09)
Changed the second instance diagram to show the instantiation of the template resource_property_limit.