Error responses to api calls

[thompson-tomo]

The response body for all all api calls which generate non non 2xx http status code should generate a problem detail response.

[duglin]

@thompson-tomo which spec are you referring to?

I'm guessing the subscription spec

[thompson-tomo]

Correct The primary one which should have it is the subscriptions api.

With that being said I just had a thought that an argument could be made that it could also be mentioned in the http bindings documentation.

[duglin]

ok I added the Subscription Spec label.

Just an FYI, the spec is basically "on hold" while the authors are busy trying to finish up the xRegistry spec. So, we may not get back to this issue for a while. I'll try to get the team to at least chime in to see if the idea is reasonable to them (which I think it might be given we're doing the same thing for xReg). Of course, if you're in a hurry, after the general idea is approved, you could submit a PR to get the ball rolling. E.g. a PR to add the infrastructure to the spec that explains how errors look in general, define the set of errors for current bad states, etc... setup the infra so that we just need to add new errors as those are identified into the template/pattern that's defined. Just a thought.