search

ietf-wg-httpapi / rfc7807bis

Revision of RFC7807: HTTP Problem Details
Other
20 stars 8 forks source link

Should `instance` be deprecated? #9

Closed sdatspun2 closed 3 years ago

sdatspun2 commented 3 years ago

In order to solve the multiple problems use case #6, potential schema change for the Problem Details Object would include an array of problems. In cases where there is singular problem, one can respond with having a single entry in the array. In that case, should we deprecate instance member?

If we do deprecate, how should we handle the deprecation? Should we use the Deprecation response header field?

asbjornu commented 3 years ago

Most problems will still be single-instance, so the top-level instance alongside the other defined properties should be kept as is, imho. Since all properties are optional, they can be omitted if the default single-instance problem scenario doesn't fit the specific error situation.

mnot commented 3 years ago

Agreed with @asbjornu. I think this issue is premature; let's figure out how to handle multiple problems first. @sdatspun2 do you mind if we close it, reopening if necessary later?

sdatspun2 commented 3 years ago

@mnot I am ok to close now.