[art] [Errata Verified] RFC7807 (6178)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 19 May 2020 02:35 UTC

To: gary@realify.com, mnot@mnot.net, erik.wilde@dret.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: barryleiba@computer.org, iesg@ietf.org, art@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200519023458.5C987F4077B@rfc-editor.org>
Date: Mon, 18 May 2020 19:34:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/CSe6OSFSnA08J2g_ZievAEbLI8s>
Subject: [art] [Errata Verified] RFC7807 (6178)
Precedence: list

The following errata report has been verified for RFC7807,
"Problem Details for HTTP APIs". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6178

--------------------------------------
Status: Verified
Type: Technical

Reported by: Gary Peck <gary@realify.com>
Date Reported: 2020-05-18
Verified by: Barry Leiba (IESG)

Section: 3

Original Text
-------------
   The ability to convey problem-specific extensions allows more than
   one problem to be conveyed.  For example:

   HTTP/1.1 400 Bad Request
   Content-Type: application/problem+json
   Content-Language: en

   {
   "type": "https://example.net/validation-error",
   "title": "Your request parameters didn't validate.",
   "invalid-params": [ {
                         "name": "age",
                         "reason": "must be a positive integer"
                       },
                       {
                         "name": "color",
                         "reason": "must be 'green', 'red' or 'blue'"}
                     ]
   }


Corrected Text
--------------
   The ability to convey problem-specific extensions allows more than
   one problem to be conveyed.  For example:

   HTTP/1.1 400 Bad Request
   Content-Type: application/problem+json
   Content-Language: en

   {
   "type": "https://example.net/validation-error",
   "title": "Your request parameters didn't validate.",
   "invalid_params": [ {
                         "name": "age",
                         "reason": "must be a positive integer"
                       },
                       {
                         "name": "color",
                         "reason": "must be 'green', 'red' or 'blue'"}
                     ]
   }


Notes
-----
The "invalid-params" member in the example is named incorrectly. According to Section 4, it should contain an "_" rather than a "-" in its name:

>   If such additional members are defined, their names SHOULD start with
>   a letter (ALPHA, as per [RFC5234], Appendix B.1) and SHOULD consist
>   of characters from ALPHA, DIGIT ([RFC5234], Appendix B.1), and "_"
>   (so that it can be serialized in formats other than JSON), and they
>   SHOULD be three characters or longer.

--------------------------------------
RFC7807 (draft-ietf-appsawg-http-problem-03)
--------------------------------------
Title               : Problem Details for HTTP APIs
Publication Date    : March 2016
Author(s)           : M. Nottingham, E. Wilde
Category            : PROPOSED STANDARD
Source              : ART Area General Application Working Group
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG

[art] [Errata Verified] RFC7807 (6178) RFC Errata System