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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 14 March 2014 02:08 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 E3BFD1A0813 for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 19:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.938
X-Spam-Level:
X-Spam-Status: No, score=-1.938 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] 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 rLYx4hv5Mn2W for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 19:08:54 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 626611A0831 for <json@ietf.org>; Thu, 13 Mar 2014 19:08:53 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id s2E28WuT023759; Fri, 14 Mar 2014 11:08:32 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 712a_8ba9_8aad333c_ab1d_11e3_991c_001e6722eec2; Fri, 14 Mar 2014 11:08:31 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 90598C048D; Fri, 14 Mar 2014 11:08:31 +0900 (JST)
Message-ID: <53226496.5020806@it.aoyama.ac.jp>
Date: Fri, 14 Mar 2014 11:08:22 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>, "Manger, James" <James.H.Manger@team.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> <CAK3OfOh0_cgArYrTNsWe1ZiXyaam34gtrgWcTs3LJWVvEf+4uw@mail.gmail.com>
In-Reply-To: <CAK3OfOh0_cgArYrTNsWe1ZiXyaam34gtrgWcTs3LJWVvEf+4uw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/json/VA3QbY9UdlyvEsEOgis-3-4s3P0
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 02:08:57 -0000

On 2014/03/14 10:25, Nico Williams wrote:
> 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.

The fact that something like application/json-text-sequence is lengthy 
also has the advantage that it may give a hint that this isn't a widely 
used format, whereas JSON itself is.

And yes, MIME types, like any other sort of identifiers, are cheap. The 
cost isn't in the identifier itself, but in the confusion and loss of 
network effects that may result.

Regards,   Martin.