Draft: draft-ietf-httpapi-rfc7807bis

Commentary: preliminary terminology review 
 Looks very good thanks ! A few additional suggestions below .
HTTP status codes (Section 15 of HTTP) cannot always convey enough
information about errors to be helpful.  While humans using Web
browsers can often understand an HTML HTML5 response body, non-human
consumers of HTTP APIs have difficulty doing so.
HTTP status codes (Section 15 of HTTP) cannot always convey enough
information about errors to be helpful.  While humans using Web
browsers can often understand an HTML HTML5 response content, non-
human consumers of HTTP APIs have difficulty doing so.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 RFC2119 RFC8174 when, and only when, they appear in all capitals,
as shown here.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 RFC2119 RFC8174 when, and only when, they appear in all
capitals, as shown here.
Consumers can use the status member to determine what the original
status code used by the generator was, in cases where it has been
changed (e.g., by an intermediary or cache), and when message bodies
persist without HTTP information.  Generic HTTP software will still
use the HTTP status code.
Consumers can use the status member to determine what the original
status code used by the generator was when it has been changed (e.g.,
by an intermediary or cache), and when a message's content is
persisted without HTTP information.  Generic HTTP software will still
use the HTTP status code.
The "title" string is advisory and included only for users who are
not aware of the semantics of the URI and can not discover them
(e.g., during offline log analysis).
The "detail" member, if present, ought to focus on helping the client
correct the problem, rather than giving debugging information.
The "title" string is advisory, and is included only for users who
both are not aware of and cannot discover the semantics of the type
URI (e.g., during offline log analysis).
The "detail" string, if present, ought to focus on helping the client
correct the problem, rather than giving debugging information.
Problem details are not a debugging tool for the underlying
implementation; rather, they are a way to expose greater detail about
the HTTP interface itself.  Designers of new problem types need to
carefully consider the Security Considerations (security-
considerations), in particular, the risk of exposing attack vectors
by exposing implementation internals through error messages.
Problem details are not a debugging tool for the underlying
implementation; rather, they are a way to expose greater detail about
the HTTP interface itself.  Designers of new problem types need to
carefully take into account the Security Considerations (security-
considerations), in particular, the risk of exposing attack vectors
by exposing implementation internals through error messages.