Peter Van den Bosch
Peter Van den Bosch
Discussion of concrete use cases is continued in #113, to analyze how such problems would be best represented. If choosing to change the existing type, we'll have to consider impact....
> At CBSS we are caught up with these changes, but we only have 2 REST API's in production at the moment. We were able to perform the changes, but...
> Do you have any numbers on how many API's on the SocSec API Gateway already using the latest InputValidationProblem structure? I don't have exact numbers, but there are about...
* having a textual "detail" description is probably sufficient for most users (i.e. they don't use the parameter references) * concern that breaking change isn't worthwhile * conceptually, multiple parameters...
> When using IDs that belong to another API, it is not recommended to include the links to the resources in an response (because the path can change, ...). I...
Updated the issue description to limit the scope to duplication of resource data across APIs (the linking issue has been addressed). IMO this is an architecture decision for which we...
We could align with this zalando rule: http://opensource.zalando.com/restful-api-guidelines/#132
WG agreed to align with Zalando's guideline. I'll work out a PR.
created PR: https://github.com/belgif/rest-guide/pull/129
eHealth encountered a problem where a typo in a client did go unnoticed because it wasn't validated, so seems useful to them. Default Axway APIGW behavior is to strip unknown...