Peter Van den Bosch

todo: contact organizations for okay to include their logo

WG agrees with proposal. example: ``` /meetings/{id}/invitees/{inviteeId} /meetings/{meetingId}/invitees/{inviteeId} => this is the new recommendation ``` renaming path parameters doesn't have impact on runtime backwards-compatibility (over-the-wire remains the same) rest-guide-validator: warn...

I propose to add this to: [[oas-contra]](https://www.belgif.be/specification/rest/api-guide/#rule-oas-contra) > Interactions with a REST API (i.e. both requests and responses) MUST be valid with respect to the constraints in its OpenAPI description....

TODO: also response validation guideline > If a REST API validates its responses before returning it, invalid response should result in a 500 Internal Server Error, or a client that...

Web logs (a.k.a. access logs) is still applicable. The URLs are indeed encrypted, but the risk is about what happens beyond the TLS endpoints. Access logs are typically made by...

PR created. A difficulty to map between OTel- and BelGov-headers is that OTel requires both trace-id (16 bytes) and span-id (8 bytes), while belgif only has a single BelGov-Trace-Id (max...

presented at WG, to be continued in next WG

1) That may be up for debate. Having a lot of `href`s could clutter responses and increase implementation effort; we're not too strict on it in practice. Then again, an...

"civilStateType": 1 vs. civilStateType: { "code": 1, "href": "https://myapiUrl.be/thisSameApi/v1/refData/civilStateTypes/1" } vs inline description "civilStateType": { "code": 1, "description": { "nl": "gehuwd", "fr": "...", "de": "..." } } response of refData:...

WG agrees to drop OpenAPI 2.0 support: * remove sections in REST guide, include warning (don't refer to outdated version) * rest-guide-validator: create 3.0 version , print warning "validator doesn't...