IETF Logo Mail Archive

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

"Matt Miller (mamille2)" <mamille2@cisco.com> Thu, 03 October 2013 16:48 UTC

Return-Path: <mamille2@cisco.com>
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 1C6B821F9473 for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 09:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Ye4ZDFooi2LX for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 09:48:18 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 84D0F21E80B3 for <json@ietf.org>; Thu, 3 Oct 2013 09:33:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6744; q=dns/txt; s=iport; t=1380818015; x=1382027615; h=from:to:subject:date:message-id:mime-version; bh=VsliWiyqUN81exZsqDB+ga07n90mjnaM1PQttSfTXaw=; b=Be3TSLESv4vW7Lj0bYj/aybMbimYY/3G5YE3Py9j3gb95SzEgH8UUISh /a99EodQRh6MW3xJcxVkbLMxozkFEjNQrb1HMX7tWfNx5m2VFpi7Q1AVj XEcpu2gTy0RU0AFTeD75Kl00UMiMuMHvDSCl/5TS0YMZH2i5pb6MzXqVH o=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFABSbTVKtJV2Z/2dsb2JhbABZgwc4UsFCgSEWdIInAQSBCwEqJjAnBBsBBYd4DJthoTiOGIEIM4MkgQQDkCiBMJgogySBcTk
X-IronPort-AV: E=Sophos; i="4.90,1027,1371081600"; d="p7s'?scan'208"; a="267784892"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 03 Oct 2013 16:33:32 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r93GXVPn032174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Thu, 3 Oct 2013 16:33:31 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.253]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Thu, 3 Oct 2013 11:33:31 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: JSON WG <json@ietf.org>
Thread-Topic: What is a JSON-text? [REVISITED]
Thread-Index: AQHOwFZLzW8CgHOE6U+dHM+wYcr+wg==
Date: Thu, 03 Oct 2013 16:33:31 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [64.101.72.48]
Content-Type: multipart/signed; boundary="Apple-Mail=_D164DDD5-473B-48B1-82A6-447661734789"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Subject: [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 16:48:35 -0000

Hello all,

There appears to be rough consensus to reference ECMA-262 edition 5.1.  As James pointed out[1], something will need to be said about what is a JSON-text; either 4627bis states a difference from ECMA-262 edition 5.1, or 4627bis states a difference from RFC 4627.

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?


-  Paul Hoffman and Matt Miller

[1] < http://www.ietf.org/mail-archive/web/json/current/msg01721.html >
[2] < http://www.ietf.org/mail-archive/web/json/current/msg00553.html >

v2.23.0 | Report a Bug | By Email