Re: [Json] Proposal: JSON text sequence MIME type and Proposed Standard

"Markus Lanthaler" <markus.lanthaler@gmx.net> Wed, 12 March 2014 08:36 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 C08CC1A0915 for <json@ietfa.amsl.com>; Wed, 12 Mar 2014 01:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.447
X-Spam-Level:
X-Spam-Status: No, score=-1.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] 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 jgig2EZmEpUX for <json@ietfa.amsl.com>; Wed, 12 Mar 2014 01:36:31 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 876A91A091F for <json@ietf.org>; Wed, 12 Mar 2014 01:36:31 -0700 (PDT)
Received: from Vostro3500 ([2.34.218.166]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MAyVY-1WFz8F28Ci-009zT1; Wed, 12 Mar 2014 09:36:15 +0100
From: "Markus Lanthaler" <markus.lanthaler@gmx.net>
To: "'Nico Williams'" <nico@cryptonector.com>, "'Tim Bray'" <tbray@textuality.com>
References: <255B9BB34FB7D647A506DC292726F6E1153F8CA38B@WSMSG3153V.srv.dir.telstra.com> <CAK3OfOjZ4nDQ7OBpbF-0D9dK9+08MhXiRe9VxKvWTXwBosd-RA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E115401A0B02@WSMSG3153V.srv.dir.telstra.com> <CAHBU6isGGLCVkc53sPoOVPktQvR4ATYBWpxSmG2TRsMSQ605gg@mail.gmail.com> <CAK3OfOg-BQA6FTvCOs-Diukjj9g+gwKKo-4BKMBcuruthtuhsQ@mail.gmail.com> <CAHBU6iv6iUkQZPgt4J6cPpURLK5EzdkuGot2Np7OUQaVaiy97g@mail.gmail.com> <CAK3OfOiVX_=UzHjE4FhM+xH7SJYUqcJ69shCPLKB9DjmaBzWBA@mail.gmail.com>
In-Reply-To: <CAK3OfOiVX_=UzHjE4FhM+xH7SJYUqcJ69shCPLKB9DjmaBzWBA@mail.gmail.com>
Date: Wed, 12 Mar 2014 09:36:11 +0100
Message-ID: <00c201cf3dce$210c3840$6324a8c0$@lanthaler@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac89sGJQlLbupa6qSXK5sE5tkky3AgAHWVJw
Content-Language: de
X-Provags-ID: V03:K0:gyuZP+l+R+Xoysp76WmCFsVlMN5s+RlWxvZXK1pwbeHwB4m3D+1 xBO9P/R85htLJP87UME+ANP2lQIaiSqek0RUUuHcMC7UnE54W/dyFgPCnIo5qjIe5tfufbM K2BWgh5D4EusRipij8vK0RvoWFkdD3ltVTWRkxNC/WtDCQwd6I6S44aq8h/VbAZ+hAZMh2f s1BGumAnEGtxaAzJkSc3A==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/tGa6lZ0ddOeFo6vpyym0-VssmDQ
Cc: "'Manger, James'" <James.H.Manger@team.telstra.com>, json@ietf.org
Subject: Re: [Json] Proposal: JSON text sequence MIME type and Proposed Standard
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, 12 Mar 2014 08:36:33 -0000

On Wednesday, March 12, 2014 6:03 AM, Nico Williams wrote:
On Tuesday, March 11, 2014, Tim Bray wrote:
> > I lean to \s+ because as soon as you see the first char, you’re
> > at the start of the next legal JSON text. 
>
> The separator can be whitespace.  It can be any whitespace recognized
> as such in the JSON ABNF.  It could be a subset of that.  It also
> could be any character or string of them that can't start a JSON value's
> encoding.  Since in practice existing apps use whitespace, we should use
> whitespace.  If other apps can be found using ", " or "," or whatever,
> we might be able to require parser support for all of them or else define
> multiple MIME types.

Given that "," is already used as separator in objects and arrays, I think it would make sense to at least include that as additional separator (and not just whitespace). Please let's not create multiple media types.


--
Markus Lanthaler
@markuslanthaler