IETF Logo Mail Archive

Re: [Json] I-JSON Topic #2: Top-Level

Matt Miller <mamille2@cisco.com> Wed, 28 May 2014 17:34 UTC

Return-Path: <mamille2@cisco.com>
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 C848F1A0417 for <json@ietfa.amsl.com>; Wed, 28 May 2014 10:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 apl6WeVgmZGo for <json@ietfa.amsl.com>; Wed, 28 May 2014 10:34:02 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B1711A04AF for <json@ietf.org>; Wed, 28 May 2014 10:34:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1038; q=dns/txt; s=iport; t=1401298439; x=1402508039; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=bVioL2/9EN9/kEXyXuQWB5CA8SgSaqY3bTCzzfiHMro=; b=j5VgRn8bZnzeMHBNh3ju8OJWosQ+12zfPXcG98piGg4ZxNibaY9qwQkE ePT1DIOKhj0FYOBeqUQQw7dk9AQI0P6R0qsXIl7KaWH85q7gHQytUWKKH CwPf0Ku2sRFjZ9XELbgb+tohsCJibJDgBfcmVeRGY22ylIbD48B4pJ462 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsYGANochlOtJV2Y/2dsb2JhbABagwdSWKoCCwEBAQEBAQUBmA0BgQ0WdIImAQEEeBELIRYPCQMCAQIBRQYNBgIBAYg+1xkXhVWISjqEQAEDiiKPU5Mng1eCEA
X-IronPort-AV: E=Sophos;i="4.98,929,1392163200"; d="scan'208";a="328381575"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 28 May 2014 17:33:58 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s4SHXwLB017772 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Wed, 28 May 2014 17:33:58 GMT
Received: from MAMILLE2-M-T03K.CISCO.COM (10.129.24.57) by xhc-rcd-x05.cisco.com (173.37.183.79) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 28 May 2014 12:33:58 -0500
Message-ID: <53861E05.9070208@cisco.com>
Date: Wed, 28 May 2014 11:33:57 -0600
From: Matt Miller <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: IETF JSON WG <json@ietf.org>
References: <535EB119.4000908@cisco.com>
In-Reply-To: <535EB119.4000908@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.129.24.57]
Archived-At: http://mailarchive.ietf.org/arch/msg/json/QpxVxXyHYES6HrTY2wp9kcPHmh0
Subject: Re: [Json] I-JSON Topic #2: Top-Level
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: Wed, 28 May 2014 17:34:05 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello All,

After another round of discussion, it appears there is rough consensus
for restricting the top-level in I-JSON to object or array.  The
Chairs note consensus is rough here.

Does anyone have additional arguments to make for or against what
constitutes an I-JSON top-level?


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJThh4FAAoJEDWi+S0W7cO19bgH/2KhplCVcPNTeowbFvHXBAyG
77fe/090hDAtLaDwJGQ6QcvN104Ov1fuMjkOJ7sniBGRcemUJq+RRZBIO9xzx5i6
ejYDOp26tQnfodR7lf0HXpCkeEdaX87jSjySDtsqwH1popqV5/JrPP4Ce26g5EcF
Jo7VroNcrXJWyRYCCZAn5X660U4FUPMeRAxoBvXVRaJcR0rKziatbmkZpqADEqvs
QPI0Wq29rI1dajaZNvGL5ZRtEQSlXmONjKucR0LqseN0Chq9U2AELquQcBl2+Q/C
cdBFr71vVsnGfdboyQrr3rerOcsIR2jDzVv3fQ+vi/4oxxjP0EcgalQ1ZpMbtLI=
=dJPJ
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email