fix(metamodel) Switches to Concerto metamodel 0.3

[jeromesimeon]

Signed-off-by: jeromesimeon [email protected]

Description

Switches metamodel support to Concerto Metamodel 0.3 which includes terminology and some structural changes (no more abstract ClassDeclaration.

Changes

• field renamed to property
• no longer use class using concept instead
• toplevel declarations are now enums and concepts

Flags

• This is fundamentally a breaking change for anyone using the metamodel API. Releasing a version 2.0 seems somewhat overkill though. Keeping a backward compatible version would be quite a lot of work. Anyone has suggestions?
• The new model reference definition is in feature(concerto) Add version 0.3 of Concerto metamodel models#146

[jeromesimeon]

@stefanblaginov Feedback welcome. Those are changes to the metamodel API for Concerto based on accordproject/models#146

[dselman]

LGTM. We will still have the round-trip ordering issue with enums / concepts to/from CTO - but perhaps we live with that for now?

[jeromesimeon]

LGTM. We will still have the round-trip ordering issue with enums / concepts to/from CTO - but perhaps we live with that for now?

Yeah, there are a few things that we could consider depending on our release timing:

• revert the enums / concepts declaration separation (it does round trip but loses the order atm). it's been done this way mostly for UI because in the UI it is more readable to separate enums from concepts -- but conceptually it would be better to leave that as a task for the UI developer to figure out.
• should fully qualified names just have a namespace instead? (a user would have to split the FQN to get the namespace atm)
• version? I think this one is likely out of reach

[jeromesimeon]

@mttrbrts @dselman Made the changes we discussed today. A follow up review would be appreciated. New metamodel is available here: accordproject/models#147