Issue 7678: Rule (27) (mof2idl-ftf) Source: Vanderbilt University (Mr. Jeff Parsons, j.parsons@vanderbilt.edu) Nature: Uncategorized Issue Severity: Summary: I assume that the identifiers for the members of the <association_name>State valuetype will be the type name in format_2, but it should probably be stated explicitly Resolution: Revised Text: Resolution: A valuetype that is derived for an association contains only a single (private) member of type of the associations's link struct as IDL sequence. This sequence is derived in rule 26 and reflects the state of the whole association's link set. However the missing statement in rule 27 is about the format of this member and therefore the issue is justified. Revised Text: Change IDL generation Rule (27) on page 21 to make the member specification clearer as follows. Note that this resolution addresses also issue 7751 (which is actually no bug in the specification). Rule(27) Additionally, a CORBA valuetype is derived with identifier concatenate ( format_1 ( <association name> ), "State" ), inheriting from MOFState (truncatable) and supporting the abstract interface derived for the association according to Rule (25). This valuetype contains one private member of type of the link-set's collection type (cp. Rule (26)), i.e. the sequence of derived link structs <association_name>LinkSet. The name for this member is concatenate( format_2 (<association_name> ), "_links" ). Actions taken: September 6, 2004: received issue August 1, 2005: closed issue Discussion: End of Annotations:===== ubject: MOF2IDL mapping Date: Mon, 6 Sep 2004 10:18:25 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MOF2IDL mapping Thread-Index: AcSUJMCvyFVMTpUfRce8WYy7DYYfcQ== From: "Jeff Parsons" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i86FXO1U010173 Rule (27) I assume that the identifiers for the members of the State valuetype will be the type name in format_2, but it should probably be stated explicitly. thanks, Jeff Parsons