[httpapi] [Technical Errata Reported] RFC9457 (7731)

[RFC Errata System <[e-mail]>]

The following errata report has been submitted for RFC9457,
"Problem Details for HTTP APIs".

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

--------------------------------------
Type: Technical
Reported by: Roman Kovařík <[e-mail]>

Section: appendix-A

Original Text
-------------
# NOTE: '\' line wrapping per RFC 8792
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "An RFC 7807 problem object",
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "format": "uri-reference",
      "description": "A URI reference that identifies the \
problem type."
    },
    "title": {
      "type": "string",
      "description": "A short, human-readable summary of the \
problem type."
    },
    "status": {
      "type": "integer",
      "description": "The HTTP status code \
generated by the origin server for this occurrence of the problem.",
      "minimum": 100,
      "maximum": 599
    },
    "detail": {
      "type": "string",
      "description": "A human-readable explanation specific to \
this occurrence of the problem."
    },
    "instance": {
      "type": "string",
      "format": "uri-reference",
      "description": "A URI reference that identifies the \
specific occurrence of the problem. It may or may not yield \
further information if dereferenced."
    }
  }
}

Corrected Text
--------------
# NOTE: '\' line wrapping per RFC 8792
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "An RFC 7807 problem object",
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "format": "uri-reference",
      "description": "A URI reference that identifies the \
problem type."
    },
    "title": {
      "type": "string",
      "description": "A short, human-readable summary of the \
problem type."
    },
    "status": {
      "type": "integer",
      "description": "The HTTP status code \
generated by the origin server for this occurrence of the problem.",
      "minimum": 100,
      "maximum": 599
    },
    "detail": {
      "type": "string",
      "description": "A human-readable explanation specific to \
this occurrence of the problem."
    },
    "instance": {
      "type": "string",
      "format": "uri-reference",
      "description": "A URI reference that identifies the \
specific occurrence of the problem. It may or may not yield \
further information if dereferenced."
    }
  },
  "additionalProperties": true
}


Notes
-----
As the schema doesn't have  "additionalProperties": true, the schema validation fails with additional fields although those are allowed according to https://www.rfc-editor.org/rfc/rfc9457#name-extension-members. Also the example in https://www.rfc-editor.org/rfc/rfc9457#name-the-problem-details-json-ob fails the validation for the same reason.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9457 (draft-ietf-httpapi-rfc7807bis-07)
--------------------------------------
Title               : Problem Details for HTTP APIs
Publication Date    : July 2023
Author(s)           : M. Nottingham, E. Wilde, S. Dalal
Category            : PROPOSED STANDARD
Source              : Building Blocks for HTTP APIs
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG