Visual RFC.
ALL RFCs / RFC 9457
Read the RFC ↗
RFC 9457 / MECHANISM GUIDE

Human-readable details

03

Title summarizes a problem type; detail explains a particular occurrence.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 9457 · § 3.1.3EXAMPLE
3 / 3
Human-readable detailsTitle summarizes a problem type; detail explains a particular occurrence.Human-readable detailstitle: Insufficient creditdetail: This account is 10 credits short.balance: 20read structured balanceDo not scrape detail prose for application logic
03
Use fields for logic

Machine logic uses stable identifiers and extension fields, not prose scraping.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Title normally remains stable across occurrences except localization.

  • Title normally remains stable across occurrences except localization.
  • Detail helps a person correct the problem.
  • Consumers should not parse detail text for machine-readable facts.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A problem response
  2. Problem type identity
  3. Human-readable details
  4. Extension members
  5. Types and safe disclosure
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗