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 23:13 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 DDF721A00D7 for <json@ietfa.amsl.com>; Sun, 1 Jun 2014 16:13:27 -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 fcyQO7aSXNui for <json@ietfa.amsl.com>; Sun, 1 Jun 2014 16:13:27 -0700 (PDT)
Received: from homiemail-a70.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 5796F1A00CF for <json@ietf.org>; Sun, 1 Jun 2014 16:13:27 -0700 (PDT)
Received: from homiemail-a70.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTP id 6E66576805C for <json@ietf.org>; Sun, 1 Jun 2014 16:13: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; s=cryptonector.com; bh=OpM/ftcS+jVHeOZxO9+r O5QuuoI=; b=yhD3ZhFqwLlNoGXFOjVlelu0gx7C3BY49E+mgMoD0jid4FiRKaHB IpzXDYpjMFi/jfbZFJ2bW1XnsheGcG9ecCSNbahPQHeiGWXPnBMrUsegMgm1pleq v0UP0vIrV5sFtshxz0azsIfU2JGXh3ro0GAJQws162wUbhYKRq+f0fw=
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com [74.125.82.180]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTPSA id 23A7D768059 for <json@ietf.org>; Sun, 1 Jun 2014 16:13:21 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id q58so4306950wes.25 for <json@ietf.org>; Sun, 01 Jun 2014 16:13:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.102.10 with SMTP id fk10mr17373463wib.42.1401664401136; Sun, 01 Jun 2014 16:13:21 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Sun, 1 Jun 2014 16:13:21 -0700 (PDT)
In-Reply-To: <CAK3OfOhy-N0zjCVxtOMB8SqZEKceVvBz9Y6i0fo2W8i+gHKm4Q@mail.gmail.com>
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>
Date: Sun, 01 Jun 2014 18:13:21 -0500
Message-ID: <CAK3OfOiQnLq29cv+kas3B8it-+82VmXvL3Rq1C5_767FDhBjRg@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/c3togjVY0c-GisG2QYZtQazMaw0
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 23:13:28 -0000

On Sun, Jun 1, 2014 at 6:12 PM, Nico Williams <nico@cryptonector.com> wrote:
> Oh, right, the separator must be a character that must be escaped in
> strings.  That greatly limits the range of characters we can choose
> from.

And it has to be a one-byte character (therefore an ASCII character,
and the texts must be encoded in UTF-8).

Nico
--

v2.23.0 | Report a Bug | By Email