This is at least seen with REQ_PATCH_BAD_PROP. Currently the spec states the following with regards to error handling with bad properties in a PATCH request:
If all properties in the update request are read-only, unknown, or unsupported, but the resource can be updated, the service shall return the HTTP 400 Bad Request status code and an error response with messages that show the non-updatable properties.
The "error response" clause does not make the usage if @Message.ExtendedInfo required (but it does recommend it). Depending on the circumstances, it's possible to encode everything in the top-level "code" and "message" properties and not need @Message.ExtendedInfo.
This is at least seen with REQ_PATCH_BAD_PROP. Currently the spec states the following with regards to error handling with bad properties in a PATCH request:
The "error response" clause does not make the usage if
@Message.ExtendedInfo
required (but it does recommend it). Depending on the circumstances, it's possible to encode everything in the top-level "code" and "message" properties and not need@Message.ExtendedInfo
.