Issue 7750: Rule (26) p. 21 (mof2idl-ftf) Source: Vanderbilt University (Mr. Jeff Parsons, j.parsons@vanderbilt.edu) Nature: Uncategorized Issue Severity: Summary: Although I see the member types for the *Link struct specified, I don't see anything about the member names. Are they specified somewhere else? How are they to be derived? Resolution: Revised Text: Resolution: The members of the link struct should be of type of the abstract interfaces derived for the associated classes. This issue is resolved together with the resolution of issue 7677. Actions taken: August 27, 2004: received issue August 1, 2005: closed issue Discussion: End of Annotations:===== ubject: More mapping questions Date: Fri, 27 Aug 2004 12:16:52 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: More mapping questions Thread-Index: AcSMWaVVVV305u3vRcOFApCKD+E50A== From: "Jeff Parsons" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i7RHUf1U030048 Hi, As I continue to work with the MOF2IDL mapping, I've come up with some more questions about it. Rule (26) p. 21 Although I see the member types for the *Link struct specified, I don't see anything about the member names. Are they specified somewhere else? How are they to be derived? From: "Michael Soden" To: "'Jeff Parsons'" Cc: Subject: RE: More mapping questions Date: Tue, 31 Aug 2004 11:56:38 +0200 Organization: Fraunhofer FOKUS X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcSMWaVVVV305u3vRcOFApCKD+E50AC2horQ Hi Jeff, here are a few answers to your questions. You should also raise them formally at the OMG's issue list. > Rule (26) p. 21 > > Although I see the member types for the *Link struct > specified, I don't see anything about the member names. > Are they specified somewhere else? How are they to be > derived? At this point, we referred to the MOF1.4, by saying "As in MOF1.4 [...]" (a bit too short and in the wrong sentence I guess). For that reason, the IDL