Re: [Json] [Technical Errata Reported] RFC7159 (3915)

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 13 March 2014 15:25 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBA871A09EC for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 08:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wMF-7eVJ4zgk for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 08:25:35 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 86D3B1A08ED for <json@ietf.org>; Thu, 13 Mar 2014 08:25:35 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s2DFPPJF082771 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 13 Mar 2014 08:25:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140307171244.B1B8D7FC392@rfc-editor.org>
Date: Thu, 13 Mar 2014 08:25:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <20E56125-5F9D-412D-B79A-D5B450798292@vpnc.org>
References: <20140307171244.B1B8D7FC392@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/RT5VcMV5NOK7eIJ5ncYvd69NRvw
Cc: Pete Resnick <presnick@qti.qualcomm.com>, json@ietf.org, vfaronov@gmail.com, Tim Bray <tbray@textuality.com>, mamille2@cisco.com, Barry Leiba <barryleiba@computer.org>
Subject: Re: [Json] [Technical Errata Reported] RFC7159 (3915)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 13 Mar 2014 15:25:37 -0000

On Mar 7, 2014, at 9:12 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:

> The following errata report has been submitted for RFC7159,
> "The JavaScript Object Notation (JSON) Data Interchange Format".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7159&eid=3915
> 
> --------------------------------------
> Type: Technical
> Reported by: Vasiliy Faronov <vfaronov@gmail.com>
> 
> Section: 12
> 
> Original Text
> -------------
>   Since JSON's syntax is borrowed from JavaScript, it is possible to
>   use that language's "eval()" function to parse JSON texts.
> 
> Corrected Text
> --------------
>   Since JSON's syntax is borrowed from JavaScript, it is possible to
>   use that language's "eval()" function to parse most (but not all)
>   JSON texts.
> 
> Notes
> -----
> This wording may be construed as meaning that every compliant JSON text is parseable as JavaScript, which is not the case: <http://timelessrepo.com/json-isnt-a-javascript-subset>. (Actually I would prefer this to be stated clearly elsewhere in the document, e.g. where it says “JSON's design goals were for it to be [...] a subset of JavaScript”.)
> 
> Instructions:
> -------------
> This errata 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 (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC7159 (draft-ietf-json-rfc4627bis-rfc7159bis)
> --------------------------------------
> Title               : The JavaScript Object Notation (JSON) Data Interchange Format
> Publication Date    : March 2014
> Author(s)           : T. Bray, Ed.
> Category            : PROPOSED STANDARD
> Source              : JavaScript Object Notation
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG

The WG chairs request that you approve this errata.

--Matt Miller and Paul Hoffman