IETF Logo Mail Archive

Re: [Json] [apps-discuss] JSON mailing list and BoF

Francis Galiegue <fgaliegue@gmail.com> Tue, 19 February 2013 23:02 UTC

Return-Path: <fgaliegue@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A824721F891D for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 15:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.433
X-Spam-Level:
X-Spam-Status: No, score=-3.433 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbKfqfUNVe+p for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 15:02:17 -0800 (PST)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id C219321F8919 for <json@ietf.org>; Tue, 19 Feb 2013 15:02:16 -0800 (PST)
Received: by mail-ee0-f43.google.com with SMTP id c50so3797477eek.2 for <json@ietf.org>; Tue, 19 Feb 2013 15:02:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=UFzs2lz3V+BaXOiqdb9p/h4UBTZhc9AImaqWwZRMmUo=; b=z8mBRcd2hiP03D6LYUWXL2bSKCo9ZVdJiE40qDFVefiahQHoQ3pzl1MGHvMvRIL/6a f5yhHF906w6pypPsJmt50eB8gPVPOiJwlUbXFV1KdBdEWZ3ibxTSd5mCY257pf0Fner/ 3GE8Xg0xH+k0Lw1NdgZE8W48E5DTEwTjJmpqRfRbBoS/FAX3ry7FJUztWaoKdZENTgoh KYOa4YLSzSka2rgJ3L3Ktie6Vn3sen6lGlFeUAZpd2gzfj24xgTiZervjMEAAzFPFUQm juVIicJyzlUPyUinXVEvOyTST2bwK1Ul+p1iM0CdKqDD+lpsqLWvVeqGAJtYG2hB/lWz 0n0w==
MIME-Version: 1.0
X-Received: by 10.14.183.67 with SMTP id p43mr61667787eem.10.1361314936023; Tue, 19 Feb 2013 15:02:16 -0800 (PST)
Received: by 10.14.1.7 with HTTP; Tue, 19 Feb 2013 15:02:15 -0800 (PST)
In-Reply-To: <CAHBU6iuMZzEev0bcB12iCoUVEfaS9jZ64-Yr0RpbOH0c=NhLfA@mail.gmail.com>
References: <CAHBU6is92fgYKE-mvcUNmN--h2KYkwMJvNGgDCYJ_pt4+xynZQ@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A70F897E94@xmb-rcd-x10.cisco.com> <CALcybBDX+tZnndDAOuXChEWURGcxMdAD6d10Kh0qf4LM0kN+CQ@mail.gmail.com> <CAHBU6iuMZzEev0bcB12iCoUVEfaS9jZ64-Yr0RpbOH0c=NhLfA@mail.gmail.com>
Date: Wed, 20 Feb 2013 00:02:15 +0100
Message-ID: <CALcybBBPz1zQSf30LEfYuqi=_Szy_Bttks4Jh5UBkrLxEOm=Yw@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Nico Williams <nico@cryptonector.com>, "json@ietf.org" <json@ietf.org>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Tue, 19 Feb 2013 23:02:17 -0000

On Tue, Feb 19, 2013 at 11:40 PM, Tim Bray <tbray@textuality.com> wrote:
> JSON, unlike XML, does not exclude U+0000
>

And is there any valid reason as to why JSON should forbid this
particular code point? IMHO, no. Although it will certainly be a
_very_ rare code point in real life, I see no valid reason to
explicitly disallow it since it _is_ representable, after all.

-- 
Francis Galiegue, fgaliegue@gmail.com
Try out your JSON Schemas: http://json-schema-validator.herokuapp.com

v2.23.0 | Report a Bug | By Email