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

Nico Williams <nico@cryptonector.com> Wed, 12 March 2014 04:02 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 263031A03A5 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 21:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.753
X-Spam-Level: *
X-Spam-Status: No, score=1.753 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, 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 5ZaKB0NUkaVz for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 21:02:19 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (unknown [69.163.253.179]) by ietfa.amsl.com (Postfix) with ESMTP id 078BE1A039A for <json@ietf.org>; Tue, 11 Mar 2014 21:02:18 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTP id 115A71DE059 for <json@ietf.org>; Tue, 11 Mar 2014 21:02:11 -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=0ByGTvEHI0yb9LlXpdqu fj9V48Q=; b=ViU2EotjxO3ey3d0ra8LeTCDytOssMRaF7uQJxUJHjtOiWXNCn9r YaGWcxtV6d8FnrNozMTgA0mVJn6w6ZZXNb/COmIifAzOiLR+jTzmoTLUri7kHxby Qiis9d1tBUqXDLOCwW0xshuXFheTSqeVgPfSSkl+WV0vvKBVMH27Tjs=
Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTPSA id BADC21DE005 for <json@ietf.org>; Tue, 11 Mar 2014 21:02:10 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id w62so10934275wes.14 for <json@ietf.org>; Tue, 11 Mar 2014 21:02:09 -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=ixV8HZ9tLpsFB80Jx/XoGbKlKeXmRJKlH6STv+Qp0S8=; b=B6sjBCNsgAO+dADJActQ59s10IFtPUza3q2NHJQ64meYBMdw92ClddbNI6lg4eLLjI EAiCaIGneVYUsUyPdrIjm0BjeBuJfro/nKL4XgvsUlKzM6B9Q3hUzyCIwHDQyHr9ojdv VG6DiE3rhedESTJUafsl+3UfHcuZszRAxypERsxDKaS55ib+N0h2KWtbjhq1MoNpk49A yL8406gRX0lM/dSpt2cftpbn2ptafTUi8FdIr5ZIDPUnNd08mbir7fZAwEvVOnvpi8MC osNpDBemw1jZGgNGrTMYerWx6CLLQLb7eWLoWZbwhVfKfzwNa2vQLaPebd4qGqWdNlrg J50g==
MIME-Version: 1.0
X-Received: by 10.180.163.206 with SMTP id yk14mr5787153wib.5.1394596929749; Tue, 11 Mar 2014 21:02:09 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Tue, 11 Mar 2014 21:02:09 -0700 (PDT)
In-Reply-To: <CAHBU6isGGLCVkc53sPoOVPktQvR4ATYBWpxSmG2TRsMSQ605gg@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>
Date: Tue, 11 Mar 2014 23:02:09 -0500
Message-ID: <CAK3OfOg-BQA6FTvCOs-Diukjj9g+gwKKo-4BKMBcuruthtuhsQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/sVZ1KSQ7KeOZEPduMmdbTmD3SYQ
Cc: "Manger, James" <James.H.Manger@team.telstra.com>, "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 04:02:20 -0000

On Tue, Mar 11, 2014 at 10:49 PM, Tim Bray <tbray@textuality.com> wrote:
> Yeah, the options are:
>
> 1. zero or more whitespace characters

Not an option for values where that would result in ambiguity.  (E.g.,
two top-level numeric values in a row.)

> 2. 1 or more whitespace characters
> 3. A specific required set of whitespace characters, for example \s*\n\s* or
> just \n

Given that there's no such thing as an empty JSON text, clearly any
number of JSON text separators is logically the same as one.  That
makes (2) and (3) OK.

jq allows any whitespace to separate JSON texts in input sequences,
but it always uses \n to separate texts when outputting JSON text
sequences.  So I'm inclined to go for (2).

Nico
--