IETF Logo Mail Archive

Re: [Json] [Technical Errata Reported] RFC8259 (5218)

Carsten Bormann <cabo@tzi.org> Tue, 29 August 2023 18:58 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73728C15C513 for <json@ietfa.amsl.com>; Tue, 29 Aug 2023 11:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1RKLXZ31uEW for <json@ietfa.amsl.com>; Tue, 29 Aug 2023 11:58:45 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E066FC15C510 for <json@ietf.org>; Tue, 29 Aug 2023 11:58:44 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RZxXg0kz3zDCcP; Tue, 29 Aug 2023 20:58:43 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20171228183515.67E4BB81D5D@rfc-editor.org>
Date: Tue, 29 Aug 2023 20:58:42 +0200
Cc: Tim Bray <tbray@textuality.com>, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, linuxwolf+ietf@outer-planes.net, vfaronov@gmail.com, json@ietf.org
X-Mao-Original-Outgoing-Id: 715028322.9193079-426f1c7585d2a7967911d254338d759e
Content-Transfer-Encoding: quoted-printable
Message-Id: <9327566C-7A7D-4ABE-894A-B707513A4346@tzi.org>
References: <20171228183515.67E4BB81D5D@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/5oEsAVBLmtGKJ9srZDISjiXwojc>
Subject: Re: [Json] [Technical Errata Reported] RFC8259 (5218)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Aug 2023 18:58:49 -0000

See also <https://mailarchive.ietf.org/arch/msg/json/dzR4HztwWcc3YKcUZeAA2a92fVI>


> On 2017-12-28, at 19:35, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC8259,
> "The JavaScript Object Notation (JSON) Data Interchange Format".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5218
> 
> --------------------------------------
> Type: Technical
> Reported by: Vasiliy Faronov <vfaronov@gmail.com>
> 
> Section: 12
> 
> Original Text
> -------------
> JSON is a subset of JavaScript
> 
> Corrected Text
> --------------
> JSON is nearly a subset of JavaScript
> 
> Notes
> -----
> JSON is not a subset of JavaScript: there are syntactically valid JSON texts that are not syntactically valid JavaScript. Namely, JSON strings can contain unescaped U+2028 LINE SEPARATOR or U+2029 PARAGRAPH SEPARATOR characters, while JavaScript string literals cannot. Thus, a sequence of characters U+0022 U+2028 U+0022 matches this RFC's 'string' production, but does not match ECMA-262's 'Expression' production.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC8259 (draft-ietf-jsonbis-rfc7159bis-04)
> --------------------------------------
> Title               : The JavaScript Object Notation (JSON) Data Interchange Format
> Publication Date    : December 2017
> Author(s)           : T. Bray, Ed.
> Category            : INTERNET STANDARD
> Source              : Javascript Object Notation Update
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

v2.23.0 | Report a Bug | By Email