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

Nico Williams <nico@cryptonector.com> Wed, 21 May 2014 15:51 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 819DB1A0445 for <json@ietfa.amsl.com>; Wed, 21 May 2014 08:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.744
X-Spam-Level:
X-Spam-Status: No, score=-0.744 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, MIME_8BIT_HEADER=0.3, 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 LcXx-J_MKErv for <json@ietfa.amsl.com>; Wed, 21 May 2014 08:51:15 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 579571A03DD for <json@ietf.org>; Wed, 21 May 2014 08:51:15 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTP id 949B62AC06E for <json@ietf.org>; Wed, 21 May 2014 08:51:14 -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:content-transfer-encoding; s= cryptonector.com; bh=dosckdCmPlVg54H/lovPbhdERwk=; b=xzV9FsPzZJS Bp8uidna2FpDjs2ZvfUbC37jKm0/zAG9KLRFsKnBeY8jDlOIkpbUFbP86f2WQoZP 75iNoLSvB8VpNoNZvn/2pvpADCbliqvrDhlJ95NYSgN8OAhvNo6VAIhsLLoUfYZB uyUdaUK7XkmOiiGKWMvrih97kmDc1ix8=
Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTPSA id 7550E2AC06A for <json@ietf.org>; Wed, 21 May 2014 08:51:14 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id l6so2497219oag.2 for <json@ietf.org>; Wed, 21 May 2014 08:51:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.155.33 with SMTP id vt1mr52240451oeb.3.1400687474057; Wed, 21 May 2014 08:51:14 -0700 (PDT)
Received: by 10.182.234.4 with HTTP; Wed, 21 May 2014 08:51:13 -0700 (PDT)
In-Reply-To: <537C64B3.1010502@it.aoyama.ac.jp>
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>
Date: Wed, 21 May 2014 10:51:13 -0500
Message-ID: <CAK3OfOjR_ixkprPUpcR-MdcH1nwPcmyvpVt8BdMvsX-vf4mz5g@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/TlIemps2_Wsrwy-AlKiKEElrr2c
Cc: 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:51:16 -0000

On Wed, May 21, 2014 at 3:32 AM, "Martin J. Dürst"
<duerst@it.aoyama.ac.jp> wrote:
> On 2014/05/21 15:16, Carsten Bormann wrote:
>> Restricting I-JSON to top-level objects only, would immediately make JCard
>> (RFC 7095) and JCal (draft-ietf-jcardcal-jcal-10.txt, in RFC-EDITOR state)
>> non-I-JSON.
>
> I wanted to write that I didn't see that much of a need for single strings,
> numbers,... in any serious format for data interchange.
>
> [...]

Well, one could make use of JSON text sequences where each text is not
an object or an array.  The canonical example for me would be database
query results when the result set is of indeterminate length at first.

Suppose you have an I-JSON application that you want to extend to use
JSON text sequences...

Nico
--