The standard approach is to use content type of "application/problem+json", which allows the client to clearly inform that the problem detail structure is provided. Is there a reason why the VOP API specification prefers “application/json” for this purpose?
The VOP API WB agreed that it could be a good suggestion to be consistent with the RFC to include in the next publication of the specifications and the YAML File.
It could be considered as a clarification.