Peter Van den Bosch

I see some potential maintenance problems if we create a BOM: if the use case is to easily let projects update to the most recent patch versions, and we have...

The guide can't ensure compatibility with every generator, but we do try to make it compatible with the most commonly used ones. We should test if this also causes problems...

Concern if spaces could cause problems (e.g. escaping when using curl). Flanders uses ":asc" and ":desc". Some use free string instead of explicit enum parameters. &sort=name,-type &sort=name,type:desc WIP guidelines around...

WG status: alternatives not tested yet, needs work

do you have an example use case? Is there any overlap with use of embedding? Can the resource representation still be kept consistent throughout POST/PUT/GET operations, or is it only...

Example: GET /orders/1?select=orderLines orderLines = child resource of orders GET /orders/1/lines/1 Other use cases: calculated result, other referenced resource other possibilities pros/cons?: * embedded? (for other use cases than calculated)...

After a quick look, these seem to be the incompatibilities with the most impact in descending order: * use of null values (slide 28) * hyphen-case in URL vs lowerCamelCase...

There's a next meeting on the differences between the guides organized by IV, to which we are invited. We can address the incompatibilities there.

https://data.vlaanderen.be/standaarden/standaarden-in-ontwikkeling/api-guidelines/api-guidelines-index.html has two presentations (werkgroep 1 on REST standards, 2nd on data sync/events). Security werkgroep is being prepared.

we should check if there are still any incompatibilities