flexoffer / flexoffer-specifications

Specifications of FlexOffer
2 stars 2 forks source link

[CCP] Clarify the behaviour if a mandatory attribute is missing or an unknow attribute is added #34

Open oliviergenest opened 4 months ago

oliviergenest commented 4 months ago

Similar to #33

Examples:

What should be the behaviour? Discard the message? Return an error? We could imagine to manage a version to be added in each message to clarify what model is being used. And the supported versions could be negotiated when establishing the connection, and/or by replying to an unsupported message version.

It also raises: how to manage possible extensions? Should we reserve some values? This is required to achieve proper backward compatibility. And avoid conflicts.

The initial question (behaviour) is a CCP, but the version/extension management could be an EP