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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 19 February 2013 22:29 UTC

Return-Path: <jhildebr@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 84A0021F8AF8 for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 14:29:46 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sj+0LauQF32r for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 14:29:46 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id C8A0321F8830 for <json@ietf.org>; Tue, 19 Feb 2013 14:29:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1029; q=dns/txt; s=iport; t=1361312985; x=1362522585; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=LzwVoMW5e2hJV9AeK57IlBcQtAe7kmE+6w6Ug+LRr2c=; b=L6vOseUIZg0uYEl9T6LIIRC/GPKZ51Dfo/b0aDXQjhyi0NgN3O2HkCm/ 8qH3HSoxSsjxRS8WriMW9mgdD9SEmX5kRxxM9MhcOeJC3QY0qs7cNWADM BbHYR76dWBjeG8RceHWeMMOHJKQtvffTE5REGDREv7Umga0L0do8P0RuD 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKX7I1GtJV2a/2dsb2JhbABFwEKBDRZzgiEBBG4LEgEIIlYlAgQBDQUIiAqwOZAojl0xB4JfYQOIMJ5TgweCJw
X-IronPort-AV: E=Sophos;i="4.84,697,1355097600"; d="scan'208";a="175917064"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 19 Feb 2013 22:29:45 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1JMTjSU016098 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 22:29:45 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 16:29:44 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>, Francis Galiegue <fgaliegue@gmail.com>
Thread-Topic: [Json] [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODuyeUCJbUuD1WEmc1GY8/86Ra5iCIeqA//+QsgA=
Date: Tue, 19 Feb 2013 22:29:43 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F897E66@xmb-rcd-x10.cisco.com>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411513EC09@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.129.24.68]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <47AFC4BD63F22041AB49C26D3792B492@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Nico Williams <nico@cryptonector.com>, Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
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 22:29:46 -0000

On 2/19/13 3:08 PM, "Matt Miller (mamille2)" <mamille2@cisco.com> wrote:

>And furthermore, "foó" versus "\u0066\u006f\u00f3" (or
>"\u0066\u006f\u006f\u00b4"?).  I think most of us clearly think the
>former is better than the latter, but it does need to be called out.
>
>I also do think some level of discussion on unicode normalization, even
>if the result is "this is out-of-scope," needs to take place.

One of the things we should also consider adding to the scope of a
potential WG is a set of design guidelines for protocols that use JSON.
One of those guidelines might be to avoid using human-language text as the
keys in an object, for this and other reasons.

However, I immediately thought of a counter-example: if you wanted to
encode a translation dictionary, you might want to do this:

{
  "Hello": {
    "en-US": "Howdy"
  }
}

It might be awkward to do this instead:

[
  {
    "word": "Hello",
    "translations": {
      "en-US": "Howdy"
    }
  }
]

-- 
Joe Hildebrand