Peter Van den Bosch

Zalando's guideline [MAY expose compound keys as resource identifiers](http://opensource.zalando.com/restful-api-guidelines/#241) on this topic is not very clear to me. Examples both with slashes as colon as separator. When using slash, should...

Guidelines we may consider: * compound key limits ability to evolve the structure of the resource identifier as it is no longer opaque. This can be a design choice between:...

**Context**: the identity/uniqueness of a resource is determined by the combination of multiple immutable properties design options: composite identifier = identifier composed from multiple property values, e.g. {employeeId}:{month} **0) Introduce...

On matrix params: * Matrix params are designed to be an alternative for "/" seperator ( e.g. GET /actors;enterpriseNumber=1234). From https://www.w3.org/DesignIssues/MatrixURIs.html: > Just as the slash separated set of elements...

open-sourcing has been green-lit suggested artifactid: belgif-rest-guide-validator, groupId: io.github.belgif.rest.guide.validator

We're working on cleaning up the code before publication; it will be published without history. We're also first releasing a last closed version to finish up all work in progress....

Initial Open Source version of the validator (2.0.0) has been released! => https://github.com/belgif/rest-guide-validator

Maybe a single issue type "invalid" suffices for all non-schema input structure validation issues? If the name of the input is returned, the client should be able to know which...

ok, added to [agenda of next WG](https://github.com/belgif/rest-guide/wiki/rest-design-meetings#meeting-2024-01-24)

> 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. This could be seen as a specific case...