Re: [Json] Kicking Off JSONbis

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Mon, 09 November 2015 21:20 UTC

Return-Path: <jhildebr@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 142AA1B836F for <json@ietfa.amsl.com>; Mon, 9 Nov 2015 13:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level:
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 z1OlJzkCL8Vc for <json@ietfa.amsl.com>; Mon, 9 Nov 2015 13:20:27 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13AE11B847B for <json@ietf.org>; Mon, 9 Nov 2015 13:20:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1380; q=dns/txt; s=iport; t=1447104026; x=1448313626; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SwevyYca2NnmtozSTyg7IttTAwqrKbmVE/RXRC+mva4=; b=C3U1YbvvlP1FcKoJwiNJMoeKEtNjO5JIFGPfnKrMAiaHk6s24X6mqGG5 l2Nl0PsdC/eGz7gxN9bfAf9dUInaCHut0nWHPvtHxwJziry691qZQGlv8 qbcakt7WfToUPwWt83bdnUi5z88tJ1NFmUkCcwGcqgUBRU/w5gQ9IqjLP o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D1AQDXDUFW/4oNJK1eDoMtgUIGvjgBDYFjhhACHIEpOBQBAQEBAQEBgQqENgEBBCMRRRACAQgaAiYCAgIfERUQAgQBDQWIGQMSsRWMCw2ESQEBAQEBAQEBAQEBAQEBAQEBAQEBARiBAYVTghCCboJTggaDHC+BFQEEh0aPAgGIDYMkgXWBW4RAjleHUgEfAQFCg0Y+cgGEXoEHAQEB
X-IronPort-AV: E=Sophos;i="5.20,267,1444694400"; d="scan'208";a="45366856"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-6.cisco.com with ESMTP; 09 Nov 2015 21:20:05 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id tA9LK5uR004856 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Nov 2015 21:20:05 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 9 Nov 2015 16:20:05 -0500
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1104.000; Mon, 9 Nov 2015 16:20:05 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Carsten Bormann <cabo@tzi.org>
Thread-Topic: [Json] Kicking Off JSONbis
Thread-Index: AQHRF6V8wbG58cqRTk2NlHPfs03MdJ6NciuAgAalzoA=
Date: Mon, 09 Nov 2015 21:20:04 +0000
Message-ID: <FF6B7829-0FA5-42D5-848D-B279069376C8@cisco.com>
References: <DB74C466-D542-42D6-95B0-690A564435A9@cisco.com> <CAC4RtVD3cKThDTr_eS-QCUhKqZkMS0y+nPS5HxCk3f1RQ7VyJQ@mail.gmail.com> <CAHBU6iv_w_O95Nq-bU1z2GOKgouuGrMbZP4Uwio25pPtFCc3UQ@mail.gmail.com> <CALaySJ+==5_mstrgHEd7bUGzSo85Er9VR_zEaJ+gh-O+zSpK=w@mail.gmail.com> <88A80A45-E673-4D0A-995B-3872874C23AE@cisco.com> <CALaySJJ01gEoHqZ4ehVHzv8mqD1CXKV3Ave3yQPrgrAGe4yckg@mail.gmail.com> <CAHBU6iuxBvn3ug9LwcK9gvrQDLr1uz=3NCrcrZaejF2iUwiLVA@mail.gmail.com> <CAChr6SzuxZrCJ+Gfc9LkKX88SetAOTp3GpxpxVF1CmmT3j5MoQ@mail.gmail.com> <56241BFE.5080609@tzi.org> <2DB105A8-AB80-4386-915D-D9AD1FBF77AD@cisco.com> <56342E23.6000509@tzi.org> <563B15AD.3070309@it.aoyama.ac.jp> <563B17FF.5050002@gmail.com>
In-Reply-To: <563B17FF.5050002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.151008
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.203.19]
Content-Type: text/plain; charset="utf-8"
Content-ID: <849B17323D2B8046883E3BEBE108F023@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/9rsOHHxWw-SAv7SWF827DtpLTa4>
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Kicking Off JSONbis
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: <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: Mon, 09 Nov 2015 21:20:30 -0000

On 11/5/15, 1:49 AM, "json on behalf of Anders Rundgren" <json-bounces@ietf.org on behalf of anders.rundgren.net@gmail.com> wrote:



>Since EMCAScript introduces predictable property order, the reference to EMCA-404 doesn't
>really tell the whole interoperability story.

That predictability has nothing to do with the wire format, though.  It's specific to the ECMAscript serializer and does not affect the semantics of the generated document.  It's not even terribly useful for canonicalization, without going to the trouble of creating a new ES object built in the correct order, which seems error-prone.  On the parse side, I *guess* you might want to know that there is an information signal retained by the order of properties.  That could be used as a steganographic channel, for instance.  It doesn't seem specific to ES, though.

I think there maybe some other reason why ES's property order logic might be interesting to you though - can you say more, please?

-- 
Joe Hildebrand