XMI model (c4i/13-09-06) contains invalid type identifiers
Source: Real-Time Innovations ( Andrea Sorbini)
The XMI model (file c4i/13-09-06) makes use of incorrect type identifiers, which point to "anonymous types" defined by Enterprise Architect.
An example of this is can be found at line 14:
<ownedParameter xmi:id="EAID_9B162F37_72E7_4fd2_9E2B_B1DEA8914167" name="obj" type="EAnone_ObservableObject" isUnique="false"/>
These errors were caused by misuse of the modelling tool, which produced anonymous types whenever the name of a type was input directly into the definition of an attribute or function parameter, instead of selecting it from a list of all the types currently defined by the model.
The offending type identifiers must be replaced with correct references, which use the machine-readable ID assigned to each type.
Reported: APP-INST 1.0b1 — Wed, 28 Oct 2015 00:09 GMT
Disposition: Resolved — APP-INST 1.0
Fix invalid type identifiers in XMI model
The invalid type identifiers described by issue
APPINST-2have been replaced by valid references to the expected types in the normative XMI model.
In order to achieve this, the UML model, created in Enterprise Architect, was modified and an XMI model was re-generated from it.
Offending elements were identified by inspecting document c4i/13-09-06 in search of XML elements which presented a value for their type attribute that matched the regular expression:
The corresponding elements of the Enterprise Architect UML model, typically a function parameter, were then modified in the modelling tool to reference the correct type and avoid generation of "anonymous types".
Changes in the UML model resulted in valid type references to be inserted in the XMI model generated by Enterprise Architect.
The regeneration of the XML from the updated UML model replaces the references to undefined types with names such as "EAnone_XXX" with the proper GUIDs "EAID_XXX" to existing types in the model.
Changes required to fix issue
APPINST-2have been consolidated with those required to resolve issues APPINST-1, APPINST-5, and APPINST-9. For this reason, no updated document is attached to this resolution.
Document omg_appinst_pim.xmi, attached to resolution
APPINST-8(which resolves APPINST-5), is the updated normative XMI document which should be used to verify the changes proposed by this resolution.
Updated: Tue, 29 Mar 2016 15:05 GMT