Issue 6694: diagrams mostly use unspecified «combine» (mu2i-ftf) Source: XTG, LLC (Mr. Joaquin Miller, jm-omg@sbcglobal.net) Nature: Revision Severity: Critical Summary: The diagrams mostly use «combine», but what that means is not specified. The defined package merge types are define and extend. Resolution: Revised Text: Actions taken: December 11, 2003: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 11 Dec 2003 13:47:35 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Joaquin Miller Company: X-Change Technologies mailFrom: jm-omg@sbcglobal.net Notification: Yes Specification: MOF 2 Section: 14.2 FormalNumber: ptc/03-10-04 Version: 2 RevisionDate: 1/1/1899 Page: various Nature: Revision Severity: Critical HTTP User Agent: Mozilla/5.0 (Windows NT 5.0; U) Opera 7.22 [en] Description The diagrams mostly use «combine», but what that means is not specified. The defined package merge types are define and extend. To: Juergen Boldt Cc: issues@omg.org, mu2i-ftf@omg.org Subject: Re: issue 6694 -- MOF 2.0 Core/UML 2.0 Infrastructure FTF issue X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Jim Amsden Date: Tue, 16 Dec 2003 14:00:07 -0500 X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 12/16/2003 12:00:27, Serialize complete at 12/16/2003 12:00:27 X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id hBGIvoNA024851 The PackageMergeKind enumeration literals are define and extend, but the corresponding stereotypes are <> and <>. This is documentd in the spec. Juergen Boldt 12/16/2003 01:53 PM To: issues@omg.org, mu2i-ftf@omg.org cc: Subject: issue 6694 -- MOF 2.0 Core/UML 2.0 Infrastructure FTF issue >From: webmaster@omg.org >Date: 11 Dec 2003 13:47:35 -0500 >To: >Subject: Issue/Bug Report > > >---------- > * Name: Joaquin Miller > * Company: X-Change Technologies > * mailFrom: jm-omg@sbcglobal.net > * Notification: Yes > * Specification: MOF 2 > * Section: 14.2 > * FormalNumber: ptc/03-10-04 > * Version: 2 > * RevisionDate: 1/1/1899 > * Page: various > * Nature: Revision > * Severity: Critical > * HTTP User Agent: Mozilla/5.0 (Windows NT 5.0; U) Opera 7.22 [en] > > > >Description > > > >The diagrams mostly use «combine», but what that means is not specified. >The defined package merge types are define and extend. ================================= Jürgen Boldt Director, Member Services Object Management Group 250 First Avenue, Suite 100 Needham, MA 02494 Tel. +1 781 444 0404 ext. 132 Fax: +1 781 444 0320 email: juergen@omg.org www www.omg.org Date: Tue, 18 May 2004 11:51:20 +0200 From: Didier Vojtisek User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en, fr To: issues@omg.org Cc: mu2i-ftf@omg.org, Jim Steel Subject: issue 6694 --diagrams mostly use unspecified <> X-Virus-Scanned: by amavisd-new at irisa.fr Hello About issue 6694, I've effectively found some details about the behavior of the <> but there are still some unprecise points. For example, what happen to combined package dependencies. Are the dependencies of the resulting package copied implicitly or explicitly ? In MOF::EMOF combines Infrastructure::Core::Basic. Basic depends on Infrastructure::Core::PrimitiveTypes and Infrastructure::Core::Abstraction. Does the resulting EMOF implicitly depends on Infrastructure::Core::PrimitiveTypes and Infrastructure::Core::Abstraction ? Or PrimitiveTypes and Abstraction are copied somewhere in MOF ? In that case with which mechanism ? Proposed resolutions: If dependencies are copied implicitly. We should explain this behavior of the <> in MOF §14.2 If dependencies aren't implicitly copied, we should update MOF figure 1- MOF imports from the UML Core to explicitly show these dependencies. Else ??? Regards Didier -- IRISA-INRIA, Campus de Beaulieu, 35042 Rennes cedex, France Tél: +33 (0) 2 99 84 75 07, Fax: +33 (0) 2 99 84 71 71