IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Sun, 01 June 2014 22:35 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 B88641A00D5 for <json@ietfa.amsl.com>; Sun, 1 Jun 2014 15:35:08 -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 XnfAeELrWXEj for <json@ietfa.amsl.com>; Sun, 1 Jun 2014 15:35:08 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 050BA1A00CF for <json@ietf.org>; Sun, 1 Jun 2014 15:35:07 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTP id 86FA01DE060 for <json@ietf.org>; Sun, 1 Jun 2014 15:35:02 -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=vkFX6wrozZzy4TZ7Ulb4 dpsGGUY=; b=TpjXyEAzY71BPTiz9eMtSjWJs+SaYbY0Y9RC3lC4L1S+TbmG4cTA xF9+QrtlZQwxpBtcAx4pZkxeY5eZoSMfogW/m2mI3SXcnnp9aVVdvFHIzrIn2SUs cKUDsxa14NcJSr23+t3CFOQB+t7+JI8nKaSQeDX90HnbFTOvJ/w6yJA=
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) (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 3B9221DE059 for <json@ietf.org>; Sun, 1 Jun 2014 15:35:02 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id a1so4235441wgh.3 for <json@ietf.org>; Sun, 01 Jun 2014 15:35:00 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.102.10 with SMTP id fk10mr17221952wib.42.1401662100903; Sun, 01 Jun 2014 15:35:00 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Sun, 1 Jun 2014 15:35:00 -0700 (PDT)
In-Reply-To: <CAHBU6itr=ogxP4uoj57goEUSOCpsRx1AXVnW1NQwSTPxbbttkw@mail.gmail.com>
References: <CAK3OfOidgk13ShPzpF-cxBHeg34s99CHs=bpY1rW-yBwnpPC-g@mail.gmail.com> <CAHBU6itr=ogxP4uoj57goEUSOCpsRx1AXVnW1NQwSTPxbbttkw@mail.gmail.com>
Date: Sun, 01 Jun 2014 17:35:00 -0500
Message-ID: <CAK3OfOhft+XJeMrg5rdY9E6fxAkJ2qsT3UHwu7zt=NEz2Q3XOQ@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/LdIn_CTIB0lA49lLC4zrtEum7fE
Cc: Carsten Bormann <cabo@tzi.org>, IETF JSON WG <json@ietf.org>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Paul Hoffman <paul.hoffman@vpnc.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: Sun, 01 Jun 2014 22:35:08 -0000

On Sun, Jun 1, 2014 at 12:08 AM, Tim Bray <tbray@textuality.com> wrote:
> On Sun, May 25, 2014 at 4:05 PM, Nico Williams <nico@cryptonector.com> wrote:
>
>> Currently my thinking is that for backwards compatibility reasons I'd
>> want to to make this RECOMMENDED though, not REQUIRED, except for
>> cases where incomplete writes are a potential problem.
>
> No. There should be only one way to do things.

I'm not terribly fond of this.

It'd be easier if we picked a Unicode whitespace character that's not
used in the JSON whitespace rule and must be escaped in strings,
preferably one that terminals and such generally handle as a
whitespace.  Failing that a character that terminals will ignore.

But since the problem we're talking about is only relevant to log-like
writing patterns, I'd prefer to make this optional for writers,
mandatory for readers.

Nico
--

v2.23.0 | Report a Bug | By Email