Metamodel JSON

Concerto models may be fully represented via the metamodel JSON format.

Given the following test.cto file:

namespace test@1.0.0

concept Person identified by email {
  o String email
  o DateTime dob optional
}

It can be converted to metamodel JSON format via the command:

Note: the excludeLineLocations argument removes the text stream positional information from the output JSON

concerto parse --model test.cto --excludeLineLocations

Giving the output:

{
    "$class": "concerto.metamodel@1.0.0.Model",
    "decorators": [],
    "namespace": "test@1.0.0",
    "imports": [],
    "declarations": [
        {
            "$class": "concerto.metamodel@1.0.0.ConceptDeclaration",
            "name": "Person",
            "isAbstract": false,
            "properties": [
                {
                    "$class": "concerto.metamodel@1.0.0.StringProperty",
                    "name": "email",
                    "isArray": false,
                    "isOptional": false
                },
                {
                    "$class": "concerto.metamodel@1.0.0.DateTimeProperty",
                    "name": "dob",
                    "isArray": false,
                    "isOptional": true
                }
            ],
            "identified": {
                "$class": "concerto.metamodel@1.0.0.IdentifiedBy",
                "name": "email"
            }
        }
    ]
}

A metamodel JSON document can be converted back to CTO format using the CLI command:

concerto print --input ./docs/test.json

Which will echo the CTO to the console:

namespace test@1.0.0

concept Person identified by email {
  o String email
  o DateTime dob optional
}

The full reference to the Concerto metamodel is available online.