Align behaviour between ContractOfferMessage and ContractRequestMessage #200
Description
Feature Request
where The ContractOfferMessage can container either consumerPid or callbackAddress based on the fact that it is a provider initiated CN or it is a counter offer from the provider.
We have the same behavior on the consumer side while sending a ContractRequestMessage which can be a first request or a counter request from the consumer to provider.
I'd propose to align also ContractRequestMessage to have oneOf with callbackAddress (initial consumer request) and providerPid (subsequent counter request)
Which Areas Would Be Affected?
e.g., data offering, policy negotiation, data transfer, etc.
Type: normative / non-normative <-- please specify the affected scope
Why Is the Feature Desired?
Are there any requirements?
Solution Proposal
If possible, provide a (brief!) solution proposal.