Re: [Json] serializing sequences of JSON values

Larry Masinter <masinter@adobe.com> Thu, 13 March 2014 21:23 UTC

Return-Path: <masinter@adobe.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 2673D1A07C8 for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 14:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 h7ZFEEyQogMc for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 14:23:55 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0139.outbound.protection.outlook.com [207.46.163.139]) by ietfa.amsl.com (Postfix) with ESMTP id 2D6361A0778 for <json@ietf.org>; Thu, 13 Mar 2014 14:23:54 -0700 (PDT)
Received: from BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) by BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) with Microsoft SMTP Server (TLS) id 15.0.893.10; Thu, 13 Mar 2014 21:23:46 +0000
Received: from BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) by BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) with mapi id 15.00.0893.001; Thu, 13 Mar 2014 21:23:46 +0000
From: Larry Masinter <masinter@adobe.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Thread-Topic: [Json] serializing sequences of JSON values
Thread-Index: Ac87TsixeUQAkrJATR2RmgrqNDBDCAAmU0IAACkfhYAAASkhgAABq9AAAAGHwYAALdgHoA==
Date: Thu, 13 Mar 2014 21:23:46 +0000
Message-ID: <58a4b20f768b484c94a850c4eba71ec5@BL2PR02MB307.namprd02.prod.outlook.com>
References: <em2c025504-6532-4513-a339-3d71c4cdfbda@helsinki> <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org>
In-Reply-To: <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.150.10.210]
x-forefront-prvs: 01494FA7F7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(189002)(199002)(51704005)(94316002)(31966008)(74662001)(97186001)(79102001)(2656002)(94946001)(97336001)(95666003)(92566001)(74502001)(85306002)(63696002)(87936001)(95416001)(74876001)(87266001)(90146001)(74316001)(56816005)(47976001)(81542001)(47446002)(83072002)(46102001)(85852003)(66066001)(59766001)(93136001)(65816001)(93516002)(77982001)(80022001)(76482001)(86362001)(51856001)(81686001)(53806001)(69226001)(54356001)(83322001)(76786001)(76576001)(81816001)(4396001)(47736001)(74706001)(74366001)(80976001)(33646001)(76796001)(50986001)(81342001)(56776001)(49866001)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR02MB307; H:BL2PR02MB307.namprd02.prod.outlook.com; CLIP:192.150.10.210; FPR:ACEEF8B6.9F26CF1D.8EF8B167.46EBAC68.20188; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: adobe.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/json/DNEB0qe9g7PWtqcVNFybW-k1hCM
Subject: Re: [Json] serializing sequences of JSON values
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: Thu, 13 Mar 2014 21:23:57 -0000

I wonder if there is any lesson from XMPP--  which wanted sequence-of-XML-values in an indefinite length stream -- that would apply to JSON.
What would XMPP look like if it were redone in JSON instead of XML?

If there a tendency to standardize on JSON as a replacement to XML in protocols, then would providing guidelines for how to do so be in scope?


> 
> > Why would sequences of objects not be preferred for logging.
> 
> Because the log is always open for appending, so the sequence never
> terminates.
> 
> This, and many other related topics, were discussed at length earlier on the
> mailing list and the rough consensus was that the current wording was
> sufficient.
>