Re: [Json] Working Group Last Call on draft-ietf-json-text-sequence

Nico Williams <nico@cryptonector.com> Sat, 24 May 2014 22:37 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 DCEFA1A00C2 for <json@ietfa.amsl.com>; Sat, 24 May 2014 15:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 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, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] 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 EwvGH3ABRtGD for <json@ietfa.amsl.com>; Sat, 24 May 2014 15:37:24 -0700 (PDT)
Received: from homiemail-a29.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D0D4B1A00B5 for <json@ietf.org>; Sat, 24 May 2014 15:37:24 -0700 (PDT)
Received: from homiemail-a29.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a29.g.dreamhost.com (Postfix) with ESMTP id CC5E6674058 for <json@ietf.org>; Sat, 24 May 2014 15:37:22 -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:content-transfer-encoding; s= cryptonector.com; bh=DMCus6vYMeQps+RJmx/1hT5J+TQ=; b=Q3n5lASOJDq 4vxUT+N5tIey3vwxsey7uSmc2HInYy8Ibh4ksxpw95oTqigupkFRYWhITYX0c4KJ GYwlLRamkGvTsWiXvMAxPhtJon/1qlhkUr+p1bP0CiQO1Oh6ifdTrUq/4v0yN/CS 2HrLJuZjayZtvcONqcuio201hbfN1DFM=
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a29.g.dreamhost.com (Postfix) with ESMTPSA id 7FE2E674057 for <json@ietf.org>; Sat, 24 May 2014 15:37:22 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id bs8so2483475wib.12 for <json@ietf.org>; Sat, 24 May 2014 15:37:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.212.77 with SMTP id ni13mr14205292wic.5.1400971041236; Sat, 24 May 2014 15:37:21 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Sat, 24 May 2014 15:37:21 -0700 (PDT)
In-Reply-To: <4E4FB86A-7DD7-462D-83F7-1FAFD947FF46@tzi.org>
References: <F6B74FE0-AEBE-43CC-BDE6-BA443BC04F2D@vpnc.org> <537EF070.6060503@it.aoyama.ac.jp> <4E4FB86A-7DD7-462D-83F7-1FAFD947FF46@tzi.org>
Date: Sat, 24 May 2014 17:37:21 -0500
Message-ID: <CAK3OfOh6cAdkj2Ab_VUspZ+NiF1Xh1eFRCsPz417vg_mt3OhCQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/LBsSFd-gJQ5oi_7JZGSxEezBorQ
Cc: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>, Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Working Group Last Call on draft-ietf-json-text-sequence
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: Sat, 24 May 2014 22:37:26 -0000

On Sat, May 24, 2014 at 12:02 PM, Carsten Bormann <cabo@tzi.org> wrote:
> On 23 May 2014, at 08:53, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
>
>> it's not too difficult to parse the delimiters separately and only have the values parsed by a JSON parser
>
> Indeed.  I continue to believe that this is the only reasonable way to operate on sequences of JSON instances.
> Either

jq has no problems using LF.  LF is only a problem if you have
corrupted entries, which is only really a problem for logfiles.

Nico
--