Belgian Remittance Information

[pvdbosch]

awaits validation of vocabularies: belgif/fedvoc#25

[pvdbosch]

Added 'structured' / 'unstructured' properties as properties to BelgianRemittanceInformation, because previous draft with 'oneOf' for string field would require clients to do regexp to check type.

[pvdbosch]

Removed the oneOf, because its difficult to use with code generation. So now same as swagger version.

With oneOf, it generates a type for the BelgianRemittanceInformation with both structured and unstructured properties, and then two "BelgianRemittanceInformationOneOf" and "BelgianRemittanceInformationOneOf1" for the inline objects in the oneOf, but without any inheritance relation between them.

[pvdbosch]

As alternative to oneOf, add minProperties: 1, maxProperties:1 which also enforces exactly one occurrence.

[pvdbosch]

When using oneOf to list only the "required" constraint rather than full object types and properties, I don't find any problems with the generated code anymore.

It's more readable than the min/maxProperties solution and still allows additional properties (evolvability); so I've updated the schema.

   BelgianRemittanceInformation:
      description: Remittance Information for credit transfers as supported by Belgian banks.
        Only one of `unstructured` or `structured` fields should be used.
      type: object
      properties:
        unstructured:
          $ref: "#/components/schemas/BelgianRemittanceInformationUnstructured"
        structured:
          $ref: "#/components/schemas/BelgianRemittanceInformationStructured"
      oneOf:
        - required: [unstructured]
        - required: [structured]

[pvdbosch]

reviewed during both functional and technical WGs, so merging and releasing.

Version using oneOf is only in available for OpenAPI 3.0, the Swagger 2.0 version has to fall back to minProperties/maxProperties