Re: [Json] Leading and trailing whitespace

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 10 June 2013 22:04 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 C2DE821F9994 for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 15:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.423
X-Spam-Level:
X-Spam-Status: No, score=-102.423 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBeHQIonIY0a for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 15:04:39 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CC86021F962B for <json@ietf.org>; Mon, 10 Jun 2013 15:04:39 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5AM4FHd054731 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 10 Jun 2013 15:04:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <06c101ce6625$0f891bf0$2e9b53d0$@augustcellars.com>
Date: Mon, 10 Jun 2013 15:04:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <379266A1-82C1-4FF5-BD7C-EE657F1FD41F@vpnc.org>
References: <06c101ce6625$0f891bf0$2e9b53d0$@augustcellars.com>
To: "Jim Schaad" <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1508)
Cc: json@ietf.org
Subject: Re: [Json] Leading and trailing whitespace
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 10 Jun 2013 22:04:41 -0000

<no hat>

On Jun 10, 2013, at 2:54 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:

> The current specification allows for arbitrary whitespace to occur before
> and after an array or object.  I would like to know if this is what was
> intended to begin with or not.

Why is the "intention" important?

> There are two different things that could be done about this (one of which
> would potentially be necessary if you allowed all values in a JSON-text.

Why should something "be done about this"? I think you are leading into canonicalization, but that's not part of RFC 4627, so introducing it seems like a pretty massive change.

Having said that, knowing your intention would be useful here.

--Paul Hoffman