IETF Logo Mail Archive

Re: [Json] What is a JSON-text? [REVISITED]

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 03 October 2013 19:09 UTC

Return-Path: <paul.hoffman@vpnc.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 2532421F89A5 for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 12:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hUNYJHcVccZ3 for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 12:09:49 -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 85B3A21F8BD8 for <json@ietf.org>; Thu, 3 Oct 2013 11:59:17 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r93IxF1T077137 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Thu, 3 Oct 2013 11:59:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
Date: Thu, 03 Oct 2013 11:59:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB92A76C-9537-4C89-911A-F94949F7EE73@vpnc.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
To: JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1510)
Subject: Re: [Json] What is a JSON-text? [REVISITED]
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Oct 2013 19:09:56 -0000

<no hat>

On Oct 3, 2013, at 9:33 AM, Matt Miller (mamille2) <mamille2@cisco.com> wrote:

> There was previously much discussion on this topic[2].  Some have restated their support.  What do others think about changing JSON-text to allow any JSON value versus just objects or arrays?

I'm +.5 on the proposal. It would make 4627bis more aligned with ECMAScript, and there is no rationale given for "a JSON-text can be less that what you think it can be". This change will make some parsers that are 4627-but-not-ECMAScript compliant become not compliant. To me, the latter is not as important as the former.

--Paul Hoffman

v2.26.15 | Report a Bug | By Email | System Status