We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There's an internet standard to model to carry machine-readable details of errors
https://datatracker.ietf.org/doc/html/rfc7807
The proposal is to use "Problem" instead of "ErrorMessage". This also facilitates the implementation of OJP in REST.
The text was updated successfully, but these errors were encountered:
@skinkie would like from @schlpbch what he wants to achieve with this.
Sorry, something went wrong.
we would have to change SIRI for that.
Will add this to SIRI github and leave it there.
Added to SIRI list: SIRI-CEN/SIRI#102
No branches or pull requests
There's an internet standard to model to carry machine-readable details of errors
https://datatracker.ietf.org/doc/html/rfc7807
The proposal is to use "Problem" instead of "ErrorMessage". This also facilitates the implementation of OJP in REST.
The text was updated successfully, but these errors were encountered: