Description Ed Willink 2018-04-06 07:08:18 EDT

If a transformation is compiled and executed, the execution has a resultant trace model and trace metamodel.

If the transformation is improved and executed, there is a new trace model and trace metamodel.

The new trace metamodel will naturally overwrite the old making it hard to browse the old trace model.

There should therefore be an option to include a timestamp as part of the trace metamodel filename/nsURI, with a further option to reuse an old timestamp if there is no change.

Since trace metamodels are probably rather similar an upgrade facility might be helpful, although the small difference may often be semantically significant.

Or ?? a reflective trace model browser, or maybe the Sample Reflective Ecore XML Model Editor does this already.