RFC Errata
Found 2 records.
Status: Reported (2)
RFC 7493, "The I-JSON Message Format", March 2015
Source of RFC: json (app)
Errata ID: 5354
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Anders Rundgren
Date Reported: 2018-05-10
Section 2.2 says:
An I-JSON sender cannot expect a receiver to treat an integer whose absolute value is greater than 9007199254740991 (i.e., that is outside the range [-(2**53)+1, (2**53)-1]) as an exact value.
It should say:
An I-JSON sender cannot expect a receiver to treat an integer whose absolute value is greater than 9007199254740992 (i.e., that is outside the range [-(2**53), (2**53)]) as an exact value.
Notes:
The limit is presumably derived from ECMAScript which says:
"The value of Number.MAX_SAFE_INTEGER is the largest integer n such that n and n + 1 are both exactly representable as a Number value"
However, Number.MAX_SAFE_INTEGER is 9007199254740991.
Errata ID: 6861
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Chris Morgan
Date Reported: 2022-02-25
Section 2.1 says:
Object member names, and string values in arrays and object members, MUST NOT include code points that identify Surrogates or Noncharacters as defined by [UNICODE].
It should say:
Object member names, and string values, MUST NOT include code points that identify Surrogates or Noncharacters as defined by [UNICODE].
Notes:
The expression “string values in arrays and object members” is overly qualified, excluding cases where the *entire message* is a string value, which should clearly be covered also. So the qualification “in arrays and object members” should be removed.
Supporting citations:
RFC 7493, section 2: “An I-JSON message is a JSON text, as defined by RFC 7159.”
RFC 7159, section 2: “A JSON text is a serialized value. Note that certain previous specifications of JSON constrained a JSON text to be an object or an array. […]”
RFC 7159, section 2:
JSON-text = ws value ws
RFC 7159, section 3:
value = false / null / true / object / array / number / string