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

Nico Williams <nico@cryptonector.com> Wed, 12 March 2014 15:44 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 663FA1A09C0 for <json@ietfa.amsl.com>; Wed, 12 Mar 2014 08:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.304
X-Spam-Level:
X-Spam-Status: No, score=0.304 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.347] 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 EjnVrcb2rNM4 for <json@ietfa.amsl.com>; Wed, 12 Mar 2014 08:44:02 -0700 (PDT)
Received: from homiemail-a105.g.dreamhost.com (agjbgdcfdbec.dreamhost.com [69.163.253.142]) by ietfa.amsl.com (Postfix) with ESMTP id 41B581A09B9 for <json@ietf.org>; Wed, 12 Mar 2014 08:44:02 -0700 (PDT)
Received: from homiemail-a105.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a105.g.dreamhost.com (Postfix) with ESMTP id 4D3E02005D90A for <json@ietf.org>; Wed, 12 Mar 2014 08:43:56 -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=JfYjo3Hzi2oPlpM1DQVd VBobr8k=; b=bcKHK/PYrcUo6KlhHWJF99qD/m7jhWV1PcKPujXBDIPhCF9EuoIM pRpieLQV5QZ0fnYl0BkwSjgTN4IQpiUUr/S6KbLt3a01Rq0y9P169pNccDuysCD7 h95pA6yGs29UTZqvtJ0ylcy3njWd4eEIyz8zPmJHFjpGSuEV1gH9h0s=
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a105.g.dreamhost.com (Postfix) with ESMTPSA id F34962005D909 for <json@ietf.org>; Wed, 12 Mar 2014 08:43:55 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id y10so11447000wgg.1 for <json@ietf.org>; Wed, 12 Mar 2014 08:43:54 -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=UdEakFLOf1uFlq8yaPnv5ZYL7FZQKxyD2fKjvxOJUDw=; b=XrE73w6/bl1yAvKTIjhJ8yCrote5iTSV/nsRK0WS+84byJaCQH35tVDk21spPB/TnM f2HuYrlbLy8FgLLc+wWn0vYoXkRbi1YJI4QczNIeTcz3lapx1YXeY4EMbtz7q97oyMu9 g4cISosnGSY8SLLIxkc32FL+T2EHqMj9TEtz6CmvauzM0TRzZppDT7aq2KsYywyNOXby fT+CiHuVKtABOeptCWyl4WYPE2sx3xCtV8hkTZeLu3pvI2KLzgadeVQOOWyw2F7XCb/9 LtQ76F6XU0vmobRSl9UYmWdiaEoquvpgSalmhaX/RBSebPHVq7vRq3Bjz2weUGEvpp62 RLww==
MIME-Version: 1.0
X-Received: by 10.180.163.206 with SMTP id yk14mr8261787wib.5.1394639027499; Wed, 12 Mar 2014 08:43:47 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Wed, 12 Mar 2014 08:43:47 -0700 (PDT)
In-Reply-To: <CAOodmJrk0ZVWixsJnTevgZeZnuB=tgfNSwKh0hRb+=9ebanV_w@mail.gmail.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> <CAMm+LwinkCumxR8bKDECqeXbUTQiZEOAt=it1u-cEEoURr7sUA@mail.gmail.com> <CAOodmJrk0ZVWixsJnTevgZeZnuB=tgfNSwKh0hRb+=9ebanV_w@mail.gmail.com>
Date: Wed, 12 Mar 2014 10:43:47 -0500
Message-ID: <CAK3OfOjonvjk2pTXLX52Z0RAWaKHTwLiQXWZ7ewdnnGX8k2YFA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Sean Gillies <sean.gillies@gmail.com>
Content-Type: multipart/alternative; boundary=00248c0d7938d34c6604f46ab3aa
Archived-At: http://mailarchive.ietf.org/arch/msg/json/2SWOJZbDCaoRIlpZlnQ6BfMYjVA
Cc: "json@ietf.org" <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 15:44:06 -0000

On Wednesday, March 12, 2014, Sean Gillies <sean.gillies@gmail.com> wrote:

> On Wed, Mar 12, 2014 at 5:26 AM, Phillip Hallam-Baker <hallam@gmail.com<javascript:_e(%7B%7D,'cvml','hallam@gmail.com');>
> > wrote:
>
>>
>> On Tue, Mar 11, 2014 at 11:49 PM, Tim Bray <tbray@textuality.com<javascript:_e(%7B%7D,'cvml','tbray@textuality.com');>
>> > wrote:
>>
>>> Yeah, the options are:
>>>
>>> 1. zero or more whitespace characters
>>> 2. 1 or more whitespace characters
>>> 3. A specific required set of whitespace characters, for example
>>> \s*\n\s* or just \n
>>>
>>
>> or
>>
>> 4. use the JSON separator character, the comma
>>
>
> I've thought about multi-text documents in the past and RFC 1521 Multipart
> immediately came to mind.
>
>   http://tools.ietf.org/html/rfc1521#page-29
>

Anything that isn't ambiguous as to the preceding or following text will
do.  The string "foobar" will do, for example.  Running code is using
whitespace though.  So at the very least the set of separators must include
whitespace.  Adding more than whitespace will mean modifying existing
sequence parsers.  How many separators do we really need, and what is the
benefit adding more?

Nico
--