IETF Logo Mail Archive

Re: [Json] [apps-discuss] JSON mailing list and BoF

Nico Williams <nico@cryptonector.com> Tue, 19 February 2013 21:41 UTC

Return-Path: <nico@cryptonector.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 A078E21F8A33; Tue, 19 Feb 2013 13:41:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.608
X-Spam-Level:
X-Spam-Status: No, score=-3.608 tagged_above=-999 required=5 tests=[AWL=-1.631, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0fhK0a3fdfz; Tue, 19 Feb 2013 13:41:41 -0800 (PST)
Received: from homiemail-a33.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by ietfa.amsl.com (Postfix) with ESMTP id 2AD7621F8A0D; Tue, 19 Feb 2013 13:41:41 -0800 (PST)
Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id 891A4594074; Tue, 19 Feb 2013 13:41:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=fzASUCRbln4lHgmbPZv+S3pcksA=; b=Uw6EkdwQ/Ha F6wWwzbzN78ydMFZwg/o5YYMKji+OaCG8QaolmycQox67fsf2URlnQzWFZUlXkCW WE+99QY1eX791ZwFqCbYyh+eipeDeMfmWV9i85m+QewwBZerHkcByp8L2Fn7FJax hBGICOFMPMWvkw10aqnEEmD1aHjptWuI=
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com [74.125.82.180]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPSA id B67DB594058; Tue, 19 Feb 2013 13:41:29 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id k14so5914958wer.25 for <multiple recipients>; Tue, 19 Feb 2013 13:41:28 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.84.165 with SMTP id a5mr30482493wiz.6.1361310087977; Tue, 19 Feb 2013 13:41:27 -0800 (PST)
Received: by 10.216.254.217 with HTTP; Tue, 19 Feb 2013 13:41:27 -0800 (PST)
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F8975C6@xmb-rcd-x10.cisco.com>
References: <4E1F6AAD24975D4BA5B168042967394367477490@TK5EX14MBXC284.redmond.corp.microsoft.com> <A723FC6ECC552A4D8C8249D9E07425A70F8975C6@xmb-rcd-x10.cisco.com>
Date: Tue, 19 Feb 2013 15:41:27 -0600
Message-ID: <CAK3OfOi5muC1kBgZHZKCzoVTgQLRLwLmwd3Jnrv_N8AkEkWPkw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Mike Jones <Michael.Jones@microsoft.com>, "json@ietf.org" <json@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Tue, 19 Feb 2013 21:41:41 -0000

On Tue, Feb 19, 2013 at 3:27 PM, Joe Hildebrand (jhildebr)
<jhildebr@cisco.com> wrote:
> I somewhat agree, but have you at least read
> draft-staykov-hu-json-canonical-form?  It's pretty straightforward, and
> nowhere near as scary as xmlenc.

Indeed.

Lexicographic sorting... makes me wonder about Unicode normalization.
Before your heads explode, what is the ECMAScript rule regarding
normalization of object keys?  Are the two normalization forms of
'foó' allowed as distinct keys in an object?

Nico
--

v2.23.0 | Report a Bug | By Email