- Enterprise Architecture
- Process Automation
- Real-time & Embedded Systems
- Service-Oriented Architecture
- Trusted Technology
The Open Group ArchiMate® Model Exchange File Format Standard Released!
The Open Group has published the ArchiMate Model Exchange File format - a standard file format for the exchange of ArchiMate models between different tools.
The Standard can be obtained from The Open Group publications catalog at https://www2.opengroup.org/ogsys/catalog/C154
(You will be required to register for an free web ID if you do not already have one).
A dedicated information site with resources including examples is available at http://www.opengroup.org/xsd/archimate/
See below for the FAQ.
version 1.03 24 May 2015
Q. What is The Open Group ArchiMate Model Exchange File Format?
A. It is a specification for a standard file format for the exchange of ArchiMate models between different tools. It is anticipated that multiple tools vendors will support the exchange file format.
Q. What is addressed in The Open Group ArchiMate Model Exchange File format?
A. The format includes a core exchange format and in addition the visual layout.
Q. Is the format intended as a persistent file format for an ArchiMate model?
A. The exchange file format is not intended as a persistent file format for the model itself, it is a mechanism to convey instance data from one tool to another (a simple analogy would be the csv file format for exchange of spreadsheet information). The data contained in the exchange file format is meant to be processed by an “ArchiMate aware” tool, thus ruling out standalone semantic inference. Once the instance data has been imported into an ArchiMate tool, that tool will probably save it in its own proprietary file format.
Q. Where can I obtain the a copy?
A. The Standard can be obtained from The Open Group publications catalog.
You will be required to register for an free web ID if you do not already have one.
Q.What is provided with the specification?
The deliverables included with the specification are as follows:
Q. Are all the elements defined in The Open Group ArchiMate Model Exchange File Format mandatory?
A. There are only two mandatory elements:
Everything else is optional. Of course, a minimal file containing only these two things would probably be unlikely, but it could be the case that there are no relationships in the model.
The following items are optional:
They are provided because they may be of use to the sender/receiver, but they don't have to be there. For example, with the Organization element, this may be useful if the tool sending or receiving would like to know how the elements/relations are organised in folders for example, but not every tool might support that and could happily ignore it.
Similarly, not every tool supports multi-language so there is need to use the xml:lang="xx" attribute. The example XML files provided with the Standard are more of a showcase of all the elements.
Q. What example models are provided with the Standard?
A. The ArchiSurance case study is provided and a Reference Model that can be used for interoperability testing. Additional examples are available at the resources site: http://www.opengroup.org/xsd/archimate
Q. I am a tool provider, how can I get involved?
A. You can get involved by joining The Open Group ArchiMate forum , email archimate-forum-AT-opengroup.org or simply visiting the resources site at http://www.opengroup.org/xsd/archimate
Q. Are there interoperability tests with other tools suppliers?
A. Yes, these are ongoing within the project within The Open Group ArchiMate Forum.
Q. I have suggestions for improvement to the exchange file format, where do I send them?
A. Please send comments by email to ogspecs-AT-opengroup.org.
Q. Is there a source code implementation available?
A. A plugin has been developed for the Archi tool. See http://www.archimatetool.com/plugins. Source code is available in the Github repository at https://github.com/archimatetool/OpenGroupXMLExchange .
Q. Are there plans to extend the standard?
A.Yes the forum is starting to look at extensions to the standard in the next phase.