Altova website: Exchanging UModel projects using XMI
UModel supports the export and import of XMI 2.4 for UML 2.0 / 2.1 / 2.1.1 and 2.1.2, 2.2, 2.3, 2.4. Do not use the Export to XMI function to archive your UModel projects, please archive the *.ump project files instead.
Select the menu item File | Export to XMI File to generate an XMI file from the UModel project, and File | Import from XMI File, to import a previously generated XMI file.
The XMI Export dialog box allows you to select the specific XMI format you want to output, XMI for UML 2.0/2.1.1. During the export process included files, even those defined as "include by reference" are also exported.
If you intend to re-import generated XMI code into UModel, please make sure that you activate the Export UModel Extensions check box.
Pretty-print XMI output
This option outputs the XMI file with XML appropriate tag indentation and carriage returns/line feeds.
XMI defines three versions of element identification: IDs, UUIDs and labels.
|•||IDs are unique within the XMI document, and are supported by most UML tools. UModel exports these type of IDs by default, i.e. none of the check boxes need activated.|
|•||UUID are Universally Unique Identifiers, and provide a mechanism to assign each element a global unique identification, GUID. These IDs are globally unique, i.e. they are not restricted to the specific XMI document. UUIDs are generated by selecting the "Export UUIDs" check box.|
|•||UUIDs are stored in the standard canonical UUID/GUID format (e.g "6B29FC40-CA47-1067-B31D-00DD010662DA", "550e8400-e29b-41d4-a716-446655440000",...)|
|•||Labels are not supported by UModel.|
|Note:||The XMI import process automatically supports both types of IDs.|
Export UModel Extensions
XMI defines an "extension mechanism" which allows each application to export its tool-specific extensions to the UML specification. Other UML tools will, however, only be able to import the standard UML data (ignoring the UModel extensions). This UModel extension data will be available when importing into UModel.
Data such as the file names of classes, or element colors, are not part of the UML specification and thus have to be deleted in XMI, or be saved in "Extensions". If they have been exported as extensions and re-imported, all file names and colors will be imported as defined. If extensions are not used for the export process, then these UModel-specific data will be lost.
When importing an XMI document, the format is automatically detected and the model generated.
Exports UModel diagrams as "Extensions" in the XMI file. The option "Export UModel Extensions" must be active to be able to save the diagrams as extensions.
© 2019 Altova GmbH