Issue 1676:  OBV TypeCode parameters wrong (obv-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: Section 5.9.7 of orbos/98-01-18 says that the TypeCode parameters for both
 tk_value and tk_value_box start with a string which is the type"s
 repository ID. Why? For everything except tk_interface, the repository ID
 is not visible as a parameter. I believe these parameter lists should not
 include repository IDs to make them consistent with the others.
 
 I assume that the {member_name, TypeCode} pairs in the tk_value parameter
 list should appear in the order of declaration of the members in the
 valuetype. This is not stated anywhere.
 
 The visibility of each member should be added to the tk_value parameter
 list. Each entry in the list should contain {member_name, TypeCode, short}
 where the short refers to the Visibility of the member.
 
 The parameter list for tk_value should probably have an additional
 parameter which is the TypeCode of the concrete valuetype base, if any.
 
 

Resolution: 
Revised Text: 
Actions taken:
July 14, 1998: received issue
July 30, 1998: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <vinoski@iona.com>
X-Sender: vinoski@mail.boston.iona.ie
Date: Tue, 14 Jul 1998 01:48:06 -0400
To: obv-rtf@omg.org, issues@omg.org
From: Steve Vinoski <vinoski@iona.com>
Subject: OBV TypeCode parameters wrong

Section 5.9.7 of orbos/98-01-18 says that the TypeCode parameters for
both
tk_value and tk_value_box start with a string which is the type's
repository ID. Why? For everything except tk_interface, the repository
ID
is not visible as a parameter. I believe these parameter lists should
not
include repository IDs to make them consistent with the others.

I assume that the {member_name, TypeCode} pairs in the tk_value
parameter
list should appear in the order of declaration of the members in the
valuetype. This is not stated anywhere.

The visibility of each member should be added to the tk_value
parameter
list. Each entry in the list should contain {member_name, TypeCode,
short}
where the short refers to the Visibility of the member.

The parameter list for tk_value should probably have an additional
parameter which is the TypeCode of the concrete valuetype base, if
any.

--steve