Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)

Nico Williams <nico@cryptonector.com> Fri, 14 March 2014 01:25 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 2E1611A07DA for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 18:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.1
X-Spam-Level: ***
X-Spam-Status: No, score=3.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.347, RDNS_NONE=0.793] 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 wSFNpTfs0rQa for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 18:25:19 -0700 (PDT)
Received: from homiemail-a107.g.dreamhost.com (unknown [69.163.253.144]) by ietfa.amsl.com (Postfix) with ESMTP id 0913B1A07B8 for <json@ietf.org>; Thu, 13 Mar 2014 18:25:18 -0700 (PDT)
Received: from homiemail-a107.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a107.g.dreamhost.com (Postfix) with ESMTP id 80A552005D10B for <json@ietf.org>; Thu, 13 Mar 2014 18:25:12 -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=FRClLRJI1ZpNfmH9OH/0 KF2eDW8=; b=R/j3aouomqEwqw7YISgDy7r0CIpsU9L4W/JmIO4YBfGQ92c55gXf 5IOwFhoZ/Du6RQk7eOwVejpd1W6G4Zblc9eIAmSZaW0k25NVe1ayWDKSvZ/JW4l0 Vl1J2aLd6/x3ybB/CdiBYJrgJPRX/WsYZHmg+opd504mWP9VpZ6L7Ac=
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a107.g.dreamhost.com (Postfix) with ESMTPSA id 33DD12005D10A for <json@ietf.org>; Thu, 13 Mar 2014 18:25:12 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id hm4so1952272wib.1 for <json@ietf.org>; Thu, 13 Mar 2014 18:25:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rGdvnOcmUqr5tiIdOSuU43VudduV3rnhLcquPDt/5DU=; b=PNoM6LsE3jtb8vfFEmjcs+qEhGLmkkevyHlZvKGxgLTt/MIgE18M5Q7+Y/667q+05z ixM+H8EOJsSPk2DndvgUbDl1gFXPE6QPL1G5CPnwQWy4It/QekGfDq2+Vh5363ZzvQay vPt7pFT86sSJlqpxxSTzkBxZPy0poRu3SPaa3lkmgiwbM6mwHBDucfDqeDa6R+MkcPcL BVJ2hZL9pYoS5zoM2o7mfvIW9FuEQtQkIORGPa69oFda4Jz/xSzrdiBHtWYJ3zCLwOHu bhuZMdUo3AooBkefm77r9D5mxxBwDIQMWNVWR7TwbhtPNLnETkoxpqXUuZVq9ZJMaJdY qT5A==
MIME-Version: 1.0
X-Received: by 10.180.163.206 with SMTP id yk14mr3900125wib.5.1394760311133; Thu, 13 Mar 2014 18:25:11 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Thu, 13 Mar 2014 18:25:11 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E115402F04C6@WSMSG3153V.srv.dir.telstra.com>
References: <CAK3OfOio58+1yuxQOcvWep1CADMfE1PVC48XDid0dWvd8=SVjA@mail.gmail.com> <CAOXDeqoYb=NXz4ikMxAg3EHFA+903bFgdpR_BL-K18U2oYriXQ@mail.gmail.com> <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com> <3416a6327a8a4cd3b49bee3c2e548870@BL2PR02MB307.namprd02.prod.outlook.com> <CAK3OfOifggWiLMiTLt8_9rDVd0anrpp+1P2bwvUSJWbaUsVKNQ@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E115402F019B@WSMSG3153V.srv.dir.telstra.com> <j7j4i9llmc2tfvjnrmllkpjso9hcp0li0i@hive.bjoern.hoehrmann.de> <255B9BB34FB7D647A506DC292726F6E115402F04C6@WSMSG3153V.srv.dir.telstra.com>
Date: Thu, 13 Mar 2014 20:25:11 -0500
Message-ID: <CAK3OfOh0_cgArYrTNsWe1ZiXyaam34gtrgWcTs3LJWVvEf+4uw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Manger, James" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/GyYOgzvVzH4tkRvPEfI1x0-_hEE
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Regarding JSON text sequence ambiguities (Re: 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: Fri, 14 Mar 2014 01:25:20 -0000

On Thu, Mar 13, 2014 at 8:16 PM, Manger, James
<James.H.Manger@team.telstra.com> wrote:
>> >  application/jsons
>
>> Single character differences are not a very good pattern and this one
>> may also have the wrong connotations (e.g., is 'jsons' to 'json' as
>> 'https' is to 'http').
>
> It has the perfect connotation: jsons looks like the plural of json, which is perfect for a format holding any number of JSON values.

I'm sympathetic to a "single character differences" lead to
typos/errors argument.  I'm also sympathetic to an argument about
wasting bandwidth.

I happen to like application/jsons, but would settle for
application/json-sequence.

Nico
--