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

Nico Williams <nico@cryptonector.com> Wed, 21 May 2014 15:54 UTC

Return-Path: <nico@cryptonector.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 62C461A0851 for <json@ietfa.amsl.com>; Wed, 21 May 2014 08:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 XNzkBSZDerKS for <json@ietfa.amsl.com>; Wed, 21 May 2014 08:54:17 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D53011A06F9 for <json@ietf.org>; Wed, 21 May 2014 08:54:17 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id 2451336006D for <json@ietf.org>; Wed, 21 May 2014 08:54:17 -0700 (PDT)
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; s=cryptonector.com; bh=C2GSGG/34OmXgTP5sTEG qQo14NE=; b=GRG45E1nln+PSbRgLvFuTPT2lwbUUpBvgDEkAUQj1BVfis+AX3VS R5LhKQhjjtuhvSva4ntPCGC8J+kbfZtcxDiVNNe6p8fjt0PS8Gk6Sp6bxMeB84Lw lumTk+R0ez92BBAk0//wIgKBIPKPBssZfX7ZYxa5TipQegQ2w9E1MGU=
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPSA id F313536006B for <json@ietf.org>; Wed, 21 May 2014 08:54:16 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id i4so2457060oah.21 for <json@ietf.org>; Wed, 21 May 2014 08:54:16 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.33.199 with SMTP id t7mr20069407oei.73.1400687656489; Wed, 21 May 2014 08:54:16 -0700 (PDT)
Received: by 10.182.234.4 with HTTP; Wed, 21 May 2014 08:54:16 -0700 (PDT)
In-Reply-To: <CFA22496.4A774%jhildebr@cisco.com>
References: <535EB119.4000908@cisco.com> <CAHBU6itycQmqzAuxWyrFZ_v=fHdenm2csyAqtUGGu+vteh6=yQ@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1154581E82F@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iuqosV91W6CJyow_eaKdCNm_VOairJysuLS8mrWV+HM9g@mail.gmail.com> <ABB2BA00-6A21-4710-A1F5-49D4FB469E8F@vpnc.org> <CAK3OfOig8y5KpYZ86KrMPxrJOYC_hLBew_nmyneHCC2mXX+tag@mail.gmail.com> <537BB89E.2040305@cisco.com> <3BF9B252-3CCD-4BC3-9F30-8634B483FAEE@tzi.org> <537C64B3.1010502@it.aoyama.ac.jp> <CAO1wJ5S=zrz3E+LUxHuYFi_Y56OUJumCKdUD7B2oMQm0kdb=Qg@mail.gmail.com> <CFA22496.4A774%jhildebr@cisco.com>
Date: Wed, 21 May 2014 10:54:16 -0500
Message-ID: <CAK3OfOix5-i--Q_HcnBcqr0m46hNNjjC90mO_OFt1nmMHbsc0A@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/JDXCoL8UUC7BWUZ8MPxjGNQOmXc
Cc: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Jacob Davies <jacob@well.com>, Carsten Bormann <cabo@tzi.org>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] I-JSON Tpic #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, 21 May 2014 15:54:18 -0000

On Wed, May 21, 2014 at 10:39 AM, Joe Hildebrand (jhildebr)
<jhildebr@cisco.com> wrote:
> For these cases, why send JSON at all?  Why not just send a string?  That
> way you also don't need the unnecessary double-quote envelope?

Because one might want to distinguish numeric, string, boolean, and
null values from each other.  Or because one might want to apply JSON
text sequencing.

If you use JSON, you can make use of JSON text sequences.

Nico
--