Ecore Export Format
Farkitect exports metamodel and model content in Eclipse EMF format — an .ecore file for the metamodel definition and an .xmi file for model instances.
Files produced
Section titled “Files produced”| File | Content | Purpose |
|---|---|---|
.ecore |
M2 metamodel as an Ecore model | Metamodel definition for Eclipse EMF |
.xmi |
M1 model instances | Model data conforming to the .ecore metamodel |
.ecore file
Section titled “.ecore file”The Ecore file captures:
- EPackage — mapped from Farkitect M2 packages
- EClass — mapped from M2 element types (Class)
- EAttribute — mapped from M2 properties
- EReference — mapped from M2 relationship types
- EEnum — mapped from M2 enumerations
- EDataType — mapped from M2 primitive types
.xmi file
Section titled “.xmi file”The XMI file contains M1 instances conforming to the .ecore metamodel:
- Element instances with property values
- Relationship instances with source/target references
Use cases
Section titled “Use cases”- Validation — load the .ecore into Eclipse EMF and validate models against it
- Code generation — use EMF codegen tools to generate Java model classes from the .ecore
- Transformation — use ATL, Acceleo, or other model transformation tools
- Interoperability — exchange metamodels with Eclipse-based modelling tools (Sirius, Xtext)