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 03:58 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 B42511A088C for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 20:58:23 -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 Ulj4L2lt4jsM for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 20:58:21 -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 7E1A11A0888 for <json@ietf.org>; Thu, 13 Mar 2014 20:58:21 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id s2E3w2mR014239; Fri, 14 Mar 2014 12:58:02 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 712a_cfd6_d72a079e_ab2c_11e3_991c_001e6722eec2; Fri, 14 Mar 2014 12:58:02 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 478D2C042B; Fri, 14 Mar 2014 12:58:02 +0900 (JST)
Message-ID: <53227E37.9050300@it.aoyama.ac.jp>
Date: Fri, 14 Mar 2014 12:57:43 +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: John Cowan <cowan@mercury.ccil.org>
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> <53226496.5020806@it.aoyama.ac.jp> <20140314022711.GL1554@mercury.ccil.org>
In-Reply-To: <20140314022711.GL1554@mercury.ccil.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/xaqPS-4pExaLoF204mIDn5PtbCE
Cc: Nico Williams <nico@cryptonector.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, "Manger, James" <James.H.Manger@team.telstra.com>, "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 03:58:23 -0000

On 2014/03/14 11:27, John Cowan wrote:
> "Martin J. Dürst" scripsit:
>
>> 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.
>
> No format is widely used when first defined.

Yes. But many if not most formats are defined but then never widely used.

> An advantage of a simple identifier is that it can be used as a "+"
> suffix.

As far  as I know, there are no limits on the theoretical number of 
characters in Mime types, subtypes, or "+" suffixes.

And I think creating a pleothra of json-related formats, and even giving 
them "+" suffixes, goes just way overboard.

The JSON text sequence idea comes from a minor inconvenience of JSON 
arrays. The benefit of JSON is that it is simple and straightforward, 
but that's apparently lost on most people in this discussion ;-(.

Regards,   Martin.