IETF Logo Mail Archive

Re: [Json] What is a JSON-text? [REVISITED]

Nico Williams <nico@cryptonector.com> Fri, 04 October 2013 18:59 UTC

Return-Path: <nico@cryptonector.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 A822721F9A37 for <json@ietfa.amsl.com>; Fri, 4 Oct 2013 11:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 Zkqf8S4rcQ+z for <json@ietfa.amsl.com>; Fri, 4 Oct 2013 11:59:02 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id AFACD21F9DB4 for <json@ietf.org>; Fri, 4 Oct 2013 11:58:37 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id B9AE436007F for <json@ietf.org>; Fri, 4 Oct 2013 11:58:35 -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=jO+7F5zEP/KtcLIFDCjL +d1M9zE=; b=ZycsA71lzA0NGPZfax435s+sBPLsYgv8sNZPU9mBay8gSIrq0U0L phKJo6vly6nnS512KTPgLUFj9HvYVYRPk8zTDWKzCQd3KopmjPnimHv3in9yDMFi dCt9y1Z/ihqgYkPRPi+U/g69R6XL/tHndcqkH6K/5hV0s6iwU3zBa9A=
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPSA id 58F4036007B for <json@ietf.org>; Fri, 4 Oct 2013 11:58:35 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id ez12so2151699wid.15 for <json@ietf.org>; Fri, 04 Oct 2013 11:58:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SyZoVloQuzXOHhTcGANRdCt4XtER8S6QgZ4yej0QqoQ=; b=WQuWIEOzT67xCP/tjESELEjHk5UTsLyu0MEEvXFqwxGK6WT4+4f7VTlB9kUL3nadkQ TBUSLfFUqb/B1eQbdQkJRosseTgtaCdtEnODa0XvvhLNFEiYnd3qEAXeniueHVoxPunm 9C3biqXaN2rLpyk2cYGtdUKCdRJm5LGklOXe9PGHfVQUSOvaPsJy1aQI0J8AV5lKrPlB T8nTbf3odAGQhQymf5z3pHfvtpPihfyMrri5nS+eEo5iJiia+pWtn3kL5j5FKMrq/xAE ISfKK/5vGQw595A3nw4MijNuupYRtHt2YWBWrBFXcrfZMY5Sl6VRYEjlTlK8VmveU3q1 kgHQ==
MIME-Version: 1.0
X-Received: by 10.194.250.6 with SMTP id yy6mr13762794wjc.13.1380913113014; Fri, 04 Oct 2013 11:58:33 -0700 (PDT)
Received: by 10.216.165.5 with HTTP; Fri, 4 Oct 2013 11:58:32 -0700 (PDT)
In-Reply-To: <866t495q4g8dv3ajpu35ic3vqig8rt411o@hive.bjoern.hoehrmann.de>
References: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com> <866t495q4g8dv3ajpu35ic3vqig8rt411o@hive.bjoern.hoehrmann.de>
Date: Fri, 04 Oct 2013 13:58:32 -0500
Message-ID: <CAK3OfOjgXEM3amxDBH_8+N=Uee-FHVzZq0qL0EspoTjsR8m-fQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary="001a11c1ba4a912c6104e7eee36c"
Cc: JSON WG <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] What is a JSON-text? [REVISITED]
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: Fri, 04 Oct 2013 18:59:19 -0000

On Oct 4, 2013 11:39 AM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote:
> [...]

Exactly.  To add to this, just as we'll have text about interop for
numbers, we should have text about top-level value interop.  There's no
reason to exclude a very commonly implemented aspect of ECMAScript (one
that is much simpler to manage than matching ECMAScript's number system).

That, is my proposal is to:

   allow any value type at the top-level in the ABNF, just as the ABNF
allows bignums, and then note that many implementations by default (or
always) only allow arrays and objects at the top-level.

I don't see how this creates an incompatibility given what's already out
there.

Nico
--

v2.23.0 | Report a Bug | By Email