You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CAMARA Service APIs need future proof, extensible schema for error handling beyond pure HTTP Status Codes
Possible evolution
IETF RFC 9457 is a promising and already adopted by some organizations.
This RFC would allow the use of HTTP Standard, CAMARA Specific, and even API Specific problem types side-by-side in an IETF standardized way.
With the move from the current proprietary error format to the format defined by the RFC will alleviate the need for another proprietary error format for developers to deal with.
A proposal is available for review: 20240304-CAMARA-Issue 133 - RFC 9457 URN Option.pdf
Problem description
CAMARA Service APIs need future proof, extensible schema for error handling beyond pure HTTP Status Codes
Possible evolution
IETF RFC 9457 is a promising and already adopted by some organizations.
This RFC would allow the use of HTTP Standard, CAMARA Specific, and even API Specific problem types side-by-side in an IETF standardized way.
With the move from the current proprietary error format to the format defined by the RFC will alleviate the need for another proprietary error format for developers to deal with.
A proposal is available for review: 20240304-CAMARA-Issue 133 - RFC 9457 URN Option.pdf
Alternative solution
Retain existing non-standard format.
Additional context
Previous issues #133 and #31 have been closed.
Proposal supports #156
Based on decision at Commonalities meeting on March 4, 2024, it was agreed to open this issue.
cc: @lbertz02
The text was updated successfully, but these errors were encountered: