Jimmy Praet

Once the updated gh-actions release workflow of https://github.com/belgif/openapi-location/pull/9 has been validated, I will create PRs to apply the same changes to the other repos.

We also have these [workflow templates](https://github.com/belgif/.github/tree/master/workflow-templates) that I forgot about. It is also possible to define [reusable workflows](https://docs.github.com/en/actions/using-workflows/reusing-workflows).

Do I copy the configuration over to the other `belgif/openapi-*` repos, or should I try a [reusable workflow](https://docs.github.com/en/actions/using-workflows/reusing-workflows)?

Reusable workflows created in this new [workflows repo](https://github.com/belgif/workflows), and activated for all `belgif/openapi-*` repos.

I'm wondering about the "RECOMMENDED to follow common programming naming conventions". Doesn't that mean it would depend on the targeted programming language: * java: lowerCamelCase, e.g. getEnterprise * C#: UpperCamelCase,...

Updated issue type list of CBSS: urn:problem-type:cbss:input-validation:replacedSsin urn:problem-type:cbss:input-validation:canceledSsin urn:problem-type:cbss:input-validation:invalidSsin **urn:problem-type:cbss:input-validation:unknownSsin** urn:problem-type:cbss:input-validation:invalidPeriod **urn:problem-type:cbss:input-validation:invalidIncompleteDate** **urn:problem-type:cbss:input-validation:invalidYearMonth** urn:problem-type:cbss:input-validation:invalidEnterpriseNumber **urn:problem-type:cbss:input-validation:invalidEstablishmentUnitNumber**

That sounds like a good idea to us. `urn:problem-type:cbss:input-validation:invalidStructure` would replace these: * urn:problem-type:cbss:input-validation:invalidSsin * urn:problem-type:cbss:input-validation:invalidIncompleteDate * urn:problem-type:cbss:input-validation:invalidYearMonth * urn:problem-type:cbss:input-validation:invalidEnterpriseNumber * urn:problem-type:cbss:input-validation:invalidEstablishmentUnitNumber ... and the same issue can then also...

At CBSS we also introduced `urn:problem-type:cbss:input-validation:invalidRefData` to signal invalid reference data. e.g. example `/socialBenefits?socialBenefitCondition=BAD`, where `/refData/socialBenefitConditions/BAD` does not exist.

Having an issue type that can be used both for non-existing ref data and for other non-existing resource references sounds good to us. But reusing `resourceNotFound` for that can be...

Sometimes types are shared in multiple operations, but validation rules may be different depending on the situation. e.g. when you want to reuse a resource type for GET and POST,...