Issue 9024: "ownedType" is not a valid element (uml2-rtf) Source: Adaptive (Mr. Gene Mutschler, gene.mutschler(at)adaptive.com) Nature: Revision Severity: Significant Summary: Having implemented a UML 2 L0 addin for Rational Rose, I exported a sample model to XMI. When this XMI file was imported into another UML2 tool, the tool failed, indicating that "ownedType" is not a valid element. Examination of the Infrastructure Library reveals why this is so. In the InfrastructureLibrary's Basic package (the basis for UML2 L0), the sole means by which a Package owns items is the "ownedType" reference. However, in The Constructs package (the basis for UML 2 L1 and beyond), this reference is now indicated as derived, meaning that it will not be handled by most UML 2 tools. It has been replaced by the "ownedMember" reference, which is unknown to UML 2 L0. This is a showstopper issue with respect to UML2 XMI interoperability, since it means that a UML2 tool operating at Level 0 cannot interchange models with UML2 tools operating at any other level. Resolution: Revised Text: Actions taken: October 4, 2005: received issue Discussion: End of Annotations:===== ubject: Issue for UML 2 Date: Tue, 4 Oct 2005 13:58:02 -0700 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Issue for UML 2 Thread-Index: AcXJJk9lMwrwst3GSBW5qNa93tCxLQ== From: "Mutschler, Gene O" To: Cc: "Tolbert, Doug M" , "Malhotra, Sumeet S" X-OriginalArrivalTime: 04 Oct 2005 20:58:03.0538 (UTC) FILETIME=[4FD75720:01C5C926] Having implemented a UML 2 L0 addin for Rational Rose, I exported a sample model to XMI. When this XMI file was imported into another UML2 tool, the tool failed, indicating that "ownedType" is not a valid element. Examination of the Infrastructure Library reveals why this is so. In the InfrastructureLibrary's Basic package (the basis for UML2 L0), the sole means by which a Package owns items is the "ownedType" reference. However, in The Constructs package (the basis for UML 2 L1 and beyond), this reference is now indicated as derived, meaning that it will not be handled by most UML 2 tools. It has been replaced by the "ownedMember" reference, which is unknown to UML 2 L0. This is a showstopper issue with respect to UML2 XMI interoperability, since it means that a UML2 tool operating at Level 0 cannot interchange models with UML2 tools operating at any other level. InfrastructureLibrary::Core::Basic packages diagram: InfrastructureLibrary::Core::Constructs packages diagram: Dr. Gene Mutschler Unisys Corporation. Mission Viejo CA 949 380 6617 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. Learn it. Love it. Live it. Subject: FW: Issue 9024 -- UML 2 RTF issue (Urgent!) Date: Wed, 5 Oct 2005 11:10:30 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue 9024 -- UML 2 RTF issue (Urgent!) Thread-Index: AcXJQRgjr/tRfDKCQmqAicxCDTKglwAlCraQ From: "Tolbert, Doug M" To: Cc: "Mutschler, Gene O" X-OriginalArrivalTime: 05 Oct 2005 18:10:31.0469 (UTC) FILETIME=[12C115D0:01C5C9D8] Folks, Unless we are somehow misinterpreting the situation reported below, this looks like a potential showstopper for XMI interchange at L0. Please give it a once-over and see if you agree. The submitted figures didn.t come through (at least on my browser config), but you can find them in the Infra available spec (ptc/04-10-14) as Figure 68 on page 102 and Figure 94 on page 163, respectively. We have confirmed import failure at L0 with a tool not of Unisys. construction as well. The key point is that a UML2 capable of importing L1 and higher conformance level XMI files cannot import an L0 file. I think this is one that will need to get fixed before we wrap-up the RTF. I.ll be happy to draft the closure but would first appreciate confirmation of the problem and any suggestions for an acceptable fix that you might have. Thanks, Doug THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Tuesday, October 04, 2005 5:05 PM To: issues@omg.org; uml2-rtf@omg.org Subject: Issue 9024 -- UML 2 RTF issue Issue 9024 -- UML 2 RTF issue "ownedType" is not a valid element Subject: Issue for UML 2 Date: Tue, 4 Oct 2005 13:58:02 -0700 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Issue for UML 2 Thread-Index: AcXJJk9lMwrwst3GSBW5qNa93tCxLQ== From: "Mutschler, Gene O" To: Cc: "Tolbert, Doug M" , "Malhotra, Sumeet S" X-OriginalArrivalTime: 04 Oct 2005 20:58:03.0538 (UTC) FILETIME=[4FD75720:01C5C926] Having implemented a UML 2 L0 addin for Rational Rose, I exported a sample model to XMI. When this XMI file was imported into another UML2 tool, the tool failed, indicating that "ownedType" is not a valid element. Examination of the Infrastructure Library reveals why this is so. In the InfrastructureLibrary's Basic package (the basis for UML2 L0), the sole means by which a Package owns items is the "ownedType" reference. However, in The Constructs package (the basis for UML 2 L1 and beyond), this reference is now indicated as derived, meaning that it will not be handled by most UML 2 tools. It has been replaced by the "ownedMember" reference, which is unknown to UML 2 L0. This is a showstopper issue with respect to UML2 XMI interoperability, since it means that a UML2 tool operating at Level 0 cannot interchange models with UML2 tools operating at any other level. InfrastructureLibrary::Core::Basic packages diagram: InfrastructureLibrary::Core::Constructs packages diagram: Dr. Gene Mutschler Unisys Corporation. Mission Viejo CA 949 380 6617 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. Learn it. Love it. Live it. ================================= 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 ================================ :wq