Note: that any import/export bridge annotated with (via ***) is not a native bridge for that tool, but just a bridge alias for a third party file format or API that may work on that tool. Thus, any bridge annotated as "via UML" or "via CWM XMI" files is often very limited for many reasons including (a) the many versions of the OMG metamodels and XMI encoding, (b) the many vendor proprietary extensions of the OMG standard, (c) the limited scope of the vendor support (e.g. the DI/ETL support for CWM is often limited to data store definitions, but not the full lineage). Finally, any bridge annotated as "via MIR XMI" is not available outside the original vendor of that tool. Indeed the Meta Integration Repository (MIR) XML Metadata Interchange (XMI) is the proprietary file format internally used by some MIMB OEM partner, but not an official import/export file format of that tool.