Serialize AQR to be usable for other backends #191
Description
Currently, after parsing a view definition, the AQR is not serialized and stored somewhere, but the individual backends are called directly to either generate a view (EMF backend) or generate an eMoflon::Neo project (TGG backend). To integrate transformations based on NeoJoin view definitions in other tools, it would be useful to store the AQR as, e.g., a JSON file. The serialized AQR could then be loaded to transform between models and views in another tool, such as Vitruvius.
The AQR is defined here. One tricky part could be that the AQR contains Xbase expressions, such as here, which would have to be serialized as XMI, I suppose. Loading the XMI could be tricky as well, as the expressions need to have the environment, i.e., the meta-models, available. In NeoJoin, this is handled by the jvmmodel.