[Model Update]: io.catenax.shared.message_header V.2.0.0

[jonbckr]

Update Reason

We want to correct the current message header model (e.g. Traits) so it is semantically correct.

MS1 Criteria

• The model that should be updated exists
• The referenced use case exists
• The potential updates are discussed with all stakeholders
• A decision on versioning was made in consensus with the affected parties according to the guidelines.
• The potential update will be either
  • backward compatible or
  • a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed
• A modeling steward has been assigned

[jonbckr]

FYI @johannsvarela @BenediktMuellerIML

[agg3fe]

Is this new model backward compatible with existing version? If not, then it would make sense to create new model with major version change, v2.0.0

[BenediktMuellerIML]

Is this new model backward compatible with existing version? If not, then it would make sense to create new model with major version change, v2.0.0

We talked about it and will do a v2.0.0.

[johannsvarela]

@agg3fe Since our colleague - who created this issue - is on vacation for the next two weeks, we can't adapt this issue. Therefore we can offer you to create a new Issue, so that you can close this one. What's your opinion?

[agg3fe]

@agg3fe Since our colleague - who created this issue - is on vacation for the next two weeks, we can't adapt this issue. Therefore we can offer you to create a new Issue, so that you can close this one. What's your opinion?

if only change is changing the version, I can also do that if you want. If there is any other change also, then we create new one.

[johannsvarela]

@agg3fe Since our colleague - who created this issue - is on vacation for the next two weeks, we can't adapt this issue. Therefore we can offer you to create a new Issue, so that you can close this one. What's your opinion?

if only change is changing the version, I can also do that if you want. If there is any other change also, then we create new one.

@agg3fe then lets keep this issue and you only change the title for us :-) We will link the PR to fix the bug soon.