IETF Logo Mail Archive

Re: [Json] Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09

Patrik Fältström <paf@frobbit.se> Mon, 08 December 2014 07:48 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EA91A6FF9; Sun, 7 Dec 2014 23:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level:
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Jv6sJQdi9QIs; Sun, 7 Dec 2014 23:48:10 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A02821A1A9B; Sun, 7 Dec 2014 23:48:10 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::22] (unknown [IPv6:2a02:80:3ffc::22]) by mail.frobbit.se (Postfix) with ESMTPSA id 10B40202B8; Mon, 8 Dec 2014 08:48:09 +0100 (CET)
Subject: Re: [Json] Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0589C141-61FB-4151-A814-0A3968E0EA25"; protocol="application/pgp-signature"; micalg="pgp-sha1"
X-Pgp-Agent: GPGMail 2.5b3
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <CAHBU6iu2F=XMu32155ktXXzK0O4p+-ud8jUjYr8ZDosSusDNLw@mail.gmail.com>
Date: Mon, 08 Dec 2014 08:48:08 +0100
Message-Id: <D6E2DDF5-C8F1-4687-A8AE-66EE66236612@frobbit.se>
References: <CE03DB3D7B45C245BCA0D24327794936289DC7@MX104CL02.corp.emc.com> <89601952-AA04-44EE-A6DA-E76D0AB07C21@frobbit.se> <20141207180528.GA1116@mercury.ccil.org> <D4E95FE1-0C25-4541-8327-16313175F13A@frobbit.se> <20141207210754.GA18507@mercury.ccil.org> <CE03DB3D7B45C245BCA0D2432779493628C75E@MX104CL02.corp.emc.com> <12AE30EF-529A-4B47-A40C-A2E0EE5A6317@frobbit.se> <CAHBU6iu2F=XMu32155ktXXzK0O4p+-ud8jUjYr8ZDosSusDNLw@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xdPONQ2UJh93egCGPtPUcZMTXsk
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, John Cowan <cowan@mercury.ccil.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "json@ietf.org" <json@ietf.org>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 07:48:13 -0000

FWIW, I think this is a good view. I just felt that given the other discussion about RFC20, you do not HAVE TO talk about ASCII or the name of the code point in the standard. Sure, that is the reason you picked U+001E, but that is more a nice story ;-)

It was not my intention to say that you should not talk about ASCII.

   Patrik

> On 8 Dec 2014, at 08:37, Tim Bray <tbray@textuality.com> wrote:
> 
> I agree 100% that the fact that JSON Text Sequences MUST BE UTF-8 should be highlighted.  Both the ASCII and Unicode names of 30/0x1e/00011110 should, for completeness, be provided.  It would be inappropriate to omit ASCII, because we picked 0x1e because of its ASCII name.
> 
> On Sun, Dec 7, 2014 at 9:44 PM, Patrik Fältström <paf@frobbit.se> wrote:
> 
> > On 8 dec 2014, at 03:59, Black, David <david.black@emc.com> wrote:
> >
> > OLD
> >   In prose: any number of JSON texts, each preceded by one ASCII RS
> >   character and each followed by a line feed (LF).
> > NEW
> >   In prose: any number of JSON texts encoded as UTF-8, each preceded
> >   by one ASCII RS character and each followed by a line feed (LF).
> >
> 
> My point is that you do not have to talk about ASCII RS. You can as well talk about the UTF-8 encoding of the unicode character INFORMATION SEPARATOR TWO, U+001E. Much cleaner.
> 
> Just say it must be UTF-8 encoded text, done.
> 
>    Patrik
> 
> 
> _______________________________________________
> 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.23.0 | Report a Bug | By Email