Issue 17329: UPDM stereotype name conflict (updm-2-0-rtf) Source: Model Driven Solutions (Mr. Ed Seidewitz, ed-s(at)modeldriven.com) Nature: Uncategorized Issue Severity: Summary: Specification: Unified Profile for DoDAF and MODAF (UPDM), Version 2.0 (formal/2012-01-03) Subclause: 8.3.1.4.3.1.2.2 Organization The profile UPDM L1::UPDM L0::DoDAF::OperationalElements::Structure::Organizational defines a stereotype Organization that specializes ActualOrganization from UPDM L1::UPDM L0::Core::OperationalElements::Structure::Organizational::Actual. There is also a stereotype called Organization defined in UPDM L1::UPDM L0::Core::OperationalElements::Structure::Organizational::Typical. This is the only case within the UPDM profile as a whole in which there are two stereotypes with the same simple name. While this does not cause any problem from a technical UML point of view, since the stereotypes are in different UML namespaces, it does have implications for the XMI serialization of UPDM models. Since stereotype applications use the XMI namespace for a profile to disambiguate stereotype names, not UML namespaces, having this one naming conflict makes it impossible to use a single XMI namespace for the UPDM profile and all its subprofiles. The DoDAF Organization stereotype does not add any functional capabilities over the Core ActualOrganization stereotype. It would therefore simplify the serialization of UPDM models, by allowing the use of a single XMI namespace, if the Organization stereotype was simply deleted from DoDAF and the ActualOrganization stereotype from Core was used instead in DoDAF models. Resolution: Revised Text: Actions taken: April 23, 2012: received issue Discussion: End of Annotations:===== m: Ed Seidewitz To: "issues@omg.org" Date: Mon, 23 Apr 2012 11:07:33 -0400 Subject: UPDM stereotype name conflict Thread-Topic: UPDM stereotype name conflict Thread-Index: Ac0hYNn6b4kyI0YASvC/14UDNQaLjA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.226]|10.1.50.226|outbound.mailprotector.net|-0.996552|0.768924|0|white|ugly|1737|3|0|0 X-Mailprotector-Results: null_ptr clean X-Mailprotector-Score: 40 X-Mailprotector-IP-Analysis: 0, 10.1.50.226, Ugly c=0.768924 p=-0.996552 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-9008-c X-Mailprotector-ID: 593332d9-e1de-4eeb-98c8-e389b1bc8384 Specification: Unified Profile for DoDAF and MODAF (UPDM), Version 2.0 (formal/2012-01-03) Subclause: 8.3.1.4.3.1.2.2 Organization The profile UPDM L1::UPDM L0::DoDAF::OperationalElements::Structure::Organizational defines a stereotype Organization that specializes ActualOrganization from UPDM L1::UPDM L0::Core::OperationalElements::Structure::Organizational::Actual. There is also a stereotype called Organization defined in UPDM L1::UPDM L0::Core::OperationalElements::Structure::Organizational::Typical. This is the only case within the UPDM profile as a whole in which there are two stereotypes with the same simple name. While this does not cause any problem from a technical UML point of view, since the stereotypes are in different UML namespaces, it does have implications for the XMI serialization of UPDM models. Since stereotype applications use the XMI namespace for a profile to disambiguate stereotype names, not UML namespaces, having this one naming conflict makes it impossible to use a single XMI namespace for the UPDM profile and all its subprofiles. The DoDAF Organization stereotype does not add any functional capabilities over the Core ActualOrganization stereotype. It would therefore simplify the serialization of UPDM models, by allowing the use of a single XMI namespace, if the Organization stereotype was simply deleted from DoDAF and the ActualOrganization stereotype from Core was used instead in DoDAF models. Subject: RE: UPDM stereotype name conflict Date: Mon, 23 Apr 2012 11:16:16 -0400 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: UPDM stereotype name conflict Thread-Index: Ac0hYNn6b4kyI0YASvC/14UDNQaLjAAAfx7AAAAaXlA= From: "Levine, Leonard F CIV DISA EE" To: "Ed Seidewitz" , , Cc: , , X-OriginalArrivalTime: 23 Apr 2012 15:16:17.0204 (UTC) FILETIME=[07A0D740:01CD2164] Concur. The DoD, having consulted with the DoDAF Metadata Working Group Chair (Dave McDaniel) concurs that UPDM can use ActualOrganization in place of the DoDAF specific Organization since both DoDAF Organization and ActualOrganization are meant to represent an actual, real organization instance rather than an abstract Organization. Len Levine, for DoD -----Original Message----- From: Ed Seidewitz [mailto:ed-s@modeldriven.com] Sent: Monday, April 23, 2012 11:10 AM To: model-interchange@omg.org; updm-rtf@omg.org Subject: FW: UPDM stereotype name conflict Per the discussion during today's MIWG telecom, I have submitted the following UPDM issue. From: Ed Seidewitz Sent: Monday, April 23, 2012 11:08 AM To: issues@omg.org Subject: UPDM stereotype name conflict Specification: Unified Profile for DoDAF and MODAF (UPDM), Version 2.0 (formal/2012-01-03) Subclause: 8.3.1.4.3.1.2.2 Organization The profile UPDM L1::UPDM L0::DoDAF::OperationalElements::Structure::Organizational defines a stereotype Organization that specializes ActualOrganization from UPDM L1::UPDM L0::Core::OperationalElements::Structure::Organizational::Actual. There is also a stereotype called Organization defined in UPDM L1::UPDM L0::Core::OperationalElements::Structure::Organizational::Typical. This is the only case within the UPDM profile as a whole in which there are two stereotypes with the same simple name. While this does not cause any problem from a technical UML point of view, since the stereotypes are in different UML namespaces, it does have implications for the XMI serialization of UPDM models. Since stereotype applications use the XMI namespace for a profile to disambiguate stereotype names, not UML namespaces, having this one naming conflict makes it impossible to use a single XMI namespace for the UPDM profile and all its subprofiles. The DoDAF Organization stereotype does not add any functional capabilities over the Core ActualOrganization stereotype. It would therefore simplify the serialization of UPDM models, by allowing the use of a single XMI namespace, if the Organization stereotype was simply deleted from DoDAF and the ActualOrganization stereotype from Core was used instead in DoDAF models. smime.p7s