File formats
Content may include inaccuracies, outdated information, or technical errors. Users are advised to cross-check critical information before implementation.
Architeezy reads and writes model content in several formats. This page names each one with its extension and content type, and says where in the product you get it.
Model files
Right-click a model in the model explorer and open the Download submenu to get its content as a file. The entries offered depend on what the model holds.
| Entry | Extension | Content type | Available for |
|---|---|---|---|
| JSON | .json | application/json | every model |
| XMI | .xmi | application/vnd.xmi+xml | every model |
| RDF Turtle | .ttl | text/turtle | every model |
| RDF TriG | .trig | application/trig | every model |
| ArchiMate | .archimate | application/xml | ArchiMate models |
| IFC | .ifc | application/x-step | IFC models |
JSON and XMI are the two general-purpose serializations of model content: the same objects, features and identifiers, written as JSON or as XML. Turtle and TriG write that content as RDF triples. ArchiMate writes the file format of the Archi desktop tool, and IFC writes a STEP physical file.
Uploading a model
Choose Upload model in the project menu, then pick files or drop them onto the dialog. Several files can be uploaded at once, and each becomes a model of its own; a file's name, without its extension, becomes the model name.
The extension decides how the file is read: .json, .xmi, .ttl, .trig,
.archimate and .ifc map to the formats above. A file in any other format is
rejected, and the rest of the batch still loads.
An ArchiMate upload may also be a ZIP archive whose model.xml entry holds the
model.
Metamodels
A metamodel can also be fetched in two derived forms, both read-only:
GET /api/models/<id>/ecore?format=xmi
GET /api/models/<id>/owl?format=ttl
GET /api/models/<id>/owl?format=trig
The ecore projection is the metamodel as an Ecore package, served as XMI with
an .ecore extension. The owl projection is the metamodel as an OWL ontology,
in Turtle or TriG.
REST API
The same serializations back the REST API. Request a format with the format
parameter or with an Accept header carrying the content type from the table
above:
GET /api/models/<scope>/<project>/<version>/<model>/content?format=json
PUT /api/models/<id>/content?format=ttl
GET returns the model's content in the requested format; PUT replaces the
content of an existing model from a file in that format.
SPARQL
The SPARQL endpoint takes a query as application/sparql-query (or
text/plain) and an update as application/sparql-update.
Results come back by query form: SELECT answers as
application/sparql-results+json, ASK answers as {"boolean": true}, and
CONSTRUCT and DESCRIBE answer as text/turtle.
Diagram images
The diagram toolbar has an export button with two entries, SVG and PNG.
Choosing one renders the whole diagram - not only the visible part - onto a
white background and downloads it as diagram.svg or diagram.png.
Images and documents
- Images. A project holds its own images, managed from the project menu. Icons and node shapes of a metamodel are SVG.
- Documents. A document is stored inside its model, so it is exported in the model formats above rather than in a format of its own.