RFC Errata
Found 2 records.
Status: Verified (1)
RFC 8785, "JSON Canonicalization Scheme (JCS)", June 2020
Source of RFC: INDEPENDENT
Errata ID: 6292
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Matt Langston
Date Reported: 2020-09-20
Verifier Name: Adrian Farrel
Date Verified: 2020-09-22
Section 3.2.2.2 says:
see Section 24.3.2.2 of [ECMA-262]
It should say:
see Section 24.5.2.2 of [ECMA-262]
Status: Reported (1)
RFC 8785, "JSON Canonicalization Scheme (JCS)", June 2020
Source of RFC: INDEPENDENT
Errata ID: 7920
Status: Reported
Type: Technical
Publication Format(s) : HTML
Reported By: Peter Patel-Schneider
Date Reported: 2024-05-02
Section 3.2.2.3 says:
ECMAScript builds on the IEEE 754 [IEEE754] double-precision standard for representing JSON number data. Such data MUST be serialized according to Section 7.1.12.1 of [ECMA-262], including the "Note 2" enhancement.
It should say:
ECMAScript builds on the IEEE 754 [IEEE754] double-precision standard for representing JSON number data. Such data MUST be serialized according to Section 7.1.12.1 of [ECMA-262], including the "Note 2" enhancement, with the exception that negative zero MUST be serialized as the String "-0".
Notes:
IEEE 754 includes as distinct values both positive and negative
zero. Section 7.1.12.1 of ECMA-262 says: If m is +0 or -0, return
the String "0". This appears to break one of the ideas of
canonicalization, namely that each distinct value has its own
canonical form.