CTS2 XML file appears to contain EA proprietary elements
Legacy Issue Number: 16347
Source: Model Driven Solutions ( Steve Cook)
Looking at 11-06-20.xml, I see elements such as <thecustomprofile:interface base_Class="EAID_F37A3B0D_CFE6_448a_A95F_26FDC113F2A2"/>, which are EA-specific representations. This needs to be fixed to be properly XMI compliant.
Reported: CTS2 1.0b1 — Thu, 23 Jun 2011 04:00 GMT
Disposition: Resolved — CTS2 1.0
The UML 2.x Specification insists that Stereotypes be bound to a
But in EA, users can freely type-in any name in the "Stereotype" field (
in the "Properties" dialog of a construct ).
Such freely typed-in stereotypes do not belong to any profile.
When exporting to XMI 2.x, we cannot export a stereotype unless we
specify its profile.
So, we create a dummy profile called "thecustomprofile" in the namespace
http://www.sparxsystems.com/profiles/thecustomprofile/1.0 and bind all
the freely typed-in stereotypes to this profile.
For example, refer to the attached Snapshot.png - Class1's stereotype is
"opt" ( I typed-in this in the "Stereotype" field in the "Properties"
dialog of the class ) & Activity1 is a BPMN 2.0 activity.
When exported to XMI 2.x, the stereotype "opt" is linked to
"thecustomprofile" as underlined in green.
XML Namespace is just a method to avoid name conflicts & using the
doesn't means that our XMI is OMG in-compliant.
If you want, you can manually change the namespace of the
"thecustomprofile" ( or any other profile used in the XMI file ) from
http://www.sparxsystems.com/profiles/thecustomprofile/1.0 to the desired
namespace ( at the location boxed in brown ).
N\A - No Change Necessary
Disposition: Closed No Change
Updated: Fri, 6 Mar 2015 20:58 GMT