Peter Van den Bosch

Confirmed that oneOf with simple types gives bad code generation results, for instance: ```YAML BelgianRemittanceInformationOneOfTwoStrings: oneOf: - description: Unstructured Remittance Information as supported by Belgian banks type: string maxLength: 140...

Tested oneOf with object-type subschemas without discriminator in Java. It doesn't seem to work as desired: * inheritance is generated, but the base interface doesn't have any common properties *...

WG: OK to add that enum values should be valid wrt the schema in which they are defined. Can be added to [[oas-enum]](https://www.belgif.be/specification/rest/api-guide/#rule-oas-enum)

WG: We'll add a line to [[err-problem]](https://www.belgif.be/specification/rest/api-guide/#rule-err-problem) to explicitly indicate that `title` and `detail` should not be parsed; and additional properties may be added to provide more **structured** information on...

@jpraet , I released belgif-openapi-location 1.2.0 with the new Github Actions without a problem. The artifacts still have to be indexed by Maven Central, but I verified staging.

Reusable workflow looks a bit easier to maintain in the long run; if it isn't too much work

WG is okay to add this new rule, I'll work out a PR.

openapi-generator seems to convert to language-specific conventions, tested with python-flask, e.g. `operationId: getOneOfTwoStrings` => `def get_one_of_two_strings()` it also generates an openapi.yaml file with the operationId replaced this converted method name...

WG: OK to mandate operationId. Prefer to have lowerCamelCase as naming convention, consistent with property naming convention.

Current rule is [[oas-reuse]](https://www.belgif.be/specification/rest/api-guide/#rule-oas-reuse). I'm okay with adding the organization level to this rule, the belgif-openapi artifacts are already compliant with this structure. For code generation, there could be use...