IETF Logo Mail Archive

Re: [Json] Using a non-whitespace separator (Re: Working Group Last Call on draft-ietf-json-text-sequence)

Tim Bray <tbray@textuality.com> Wed, 04 June 2014 17:55 UTC

Return-Path: <tbray@textuality.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 3496F1A0306 for <json@ietfa.amsl.com>; Wed, 4 Jun 2014 10:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 2IbwgPGmIY7l for <json@ietfa.amsl.com>; Wed, 4 Jun 2014 10:54:56 -0700 (PDT)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB0241A024F for <json@ietf.org>; Wed, 4 Jun 2014 10:54:55 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id jz11so9138187veb.7 for <json@ietf.org>; Wed, 04 Jun 2014 10:54:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=+WLERh5bRDst83vkab0iTzgK5BH/lMW0Jt1h1OGm1qM=; b=PISGI3awhbBK9Q15o75rlttea7GCJ2FjLqd+8sgakXwsGwnyCVhOCDI2PRb5Pc+4H+ fibxmDxAPNoqvoMSnBXkUTuIrr6wKWTDi8FTyA2pJMKkxsHgdltiLPjayJFKzCeGTOcb qCpaMaj/TjVP9h8R3PZOrokKuLCUZOX/5ZBGPU8hsQJOlDeDJcTes6B85RDqB0ca66GX qa9SOAOFHWE5N49HI/ENm4mWeodpTqtXIA/jNCd2MkbAZfAB5oX4soR53P3NqU77+ued /zOJqjhutBNvloL0QkKglE/nmBBt8EJavvfyQ6GQd1fU1lYvBTLSUx+Z8S7fO8C8gqx9 pwYw==
X-Gm-Message-State: ALoCoQmQIDyoD2kGnHtyQuow7Ru47tt1USiKl+Tz0eVX5JwuXykwUfSQxyQrMPstJf5DoNx+cxbc
X-Received: by 10.58.118.228 with SMTP id kp4mr4473520veb.59.1401904489171; Wed, 04 Jun 2014 10:54:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.98.73 with HTTP; Wed, 4 Jun 2014 10:54:29 -0700 (PDT)
X-Originating-IP: [24.85.103.37]
In-Reply-To: <084664DB-A55D-465E-8888-97BA0BB59637@vpnc.org>
References: <CAK3OfOidgk13ShPzpF-cxBHeg34s99CHs=bpY1rW-yBwnpPC-g@mail.gmail.com> <CAHBU6itr=ogxP4uoj57goEUSOCpsRx1AXVnW1NQwSTPxbbttkw@mail.gmail.com> <CAK3OfOhft+XJeMrg5rdY9E6fxAkJ2qsT3UHwu7zt=NEz2Q3XOQ@mail.gmail.com> <CAK3OfOhy-N0zjCVxtOMB8SqZEKceVvBz9Y6i0fo2W8i+gHKm4Q@mail.gmail.com> <CAK3OfOiQnLq29cv+kas3B8it-+82VmXvL3Rq1C5_767FDhBjRg@mail.gmail.com> <03CFAB3E-F4C6-4AE8-A501-8525376C4AA7@vpnc.org> <CAK3OfOja-17V391tTK91R98X8XQzd0iPnur2=oo4ii+MCOt+Rg@mail.gmail.com> <CFB42410.4EDDC%jhildebr@cisco.com> <CAMm+Lwime-=UQPu3t2ty05CZLb7xUMi9KGi31Xi2B7RNF5S3Og@mail.gmail.com> <CAK3OfOg_k4Ngq+z1pn4b+XRf0M1Hqx8qZ9BtW0sa8QQ+bjKJyA@mail.gmail.com> <084664DB-A55D-465E-8888-97BA0BB59637@vpnc.org>
From: Tim Bray <tbray@textuality.com>
Date: Wed, 04 Jun 2014 10:54:29 -0700
Message-ID: <CAHBU6itEph5GzB-P8bUUvUMopRNxcCE-16qys7ofhdmsDvpN4w@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="089e0122f8fc16216204fb06532a"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/wLbrYeDY53yM_l6LWucTh4SMG-U
Cc: Nico Williams <nico@cryptonector.com>, Phillip Hallam-Baker <ietf@hallambaker.com>, Joe Hildebrand Hildebrand <jhildebr@cisco.com>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Using a non-whitespace separator (Re: 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: Wed, 04 Jun 2014 17:55:01 -0000

Hah, I hadn’t realized that RS (U+001E, INFORMATION SEPARATOR TWO) was
excluded.   OK, so the abnf for JSON-sequence becomes one of these two:

JSON-sequence = JSON-text *( %1e JSON-text )
JSON-sequence = *( ws %1e JSON-text )

Depending on whether you see the RS as an initiator or a separator.  I
think I very slightly prefer the second.


On Wed, Jun 4, 2014 at 10:43 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> <no hat>
>
> On Jun 4, 2014, at 9:12 AM, Nico Williams <nico@cryptonector.com> wrote:
>
> > Alright.  Two proposals:
> >
> > 1) Writers MUST precede texts with RS, and SHOULD follow texts with LF.
> >
> > (RS must precede at least so as to make any complete text parseable
> > even if the preceding one was written incompletely.  LF is needed so
> > as to make line-oriented tooling happy.)
> >
> > 2) Writers of logfiles (or any case where incomplete writes are a
> > problem) MUST do the same as in (1).  Other writers need only emit
> > (MUST emit) an LF after each text.  Symmetrically, parsers MUST be
> > able to parse either form.
>
> (1) seems much cleaner than (2).
>
> --Paul Hoffman
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>



-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)

v2.29.0 | Report a Bug | By Email | System Status