IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Thu, 03 October 2013 18:28 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 2BBFC21E80B0 for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 11:28:45 -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=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 bGK5v1Rr+pVa for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 11:28:31 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id E480C21E80EB for <json@ietf.org>; Thu, 3 Oct 2013 11:18:43 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTP id 984CB2007F211 for <json@ietf.org>; Thu, 3 Oct 2013 11:18:43 -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=+hBZ8N4rpkwocMYOAbqj 6sUedk4=; b=zAGXGsY0A521YzHBFTjsVXLxrvTdgS0YoCTKIHsr3orIIlNkVjR2 aHn7Z2DmdMeGImKfyLBM9Wq01a7xa6l/FHzSS1GENc08WjGuortl8xPen0xSrsyt 7VI5sFQvXTPXLTh3pxLmJ9oPQmgDQfBCd2LUQQpaGZJTf0V5Z9NxObU=
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTPSA id 4D1CE2007F20F for <json@ietf.org>; Thu, 3 Oct 2013 11:18:43 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id hm2so437938wib.12 for <json@ietf.org>; Thu, 03 Oct 2013 11:18:41 -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=rrjwyLGTz2DujbMfo1DjZXDsXbq9m4iEJV3u+ydrjFA=; b=Cj9RsNbWc/6s4CFRz5BCX1Eupr3MHWo2amc5HvG6dPIwLgIGUmOF1Ul3UcsTOXEnec GLrjgLoQXY8kNJjOX5ap4kTIe4VmlnvRTQrwO+candaohGEfLkUMTRwpfg9ayitnuIu1 Z8Q/9mymCJ3RiasjPxXL3AtCJtQ3oahUMmqO3nZMMts+wXi/GwR6qDpfP+fLDej/V2LR RE5/akyMuKMa0+UcqfAs7WRHmtZH1GfeG+TS3ZjALEWwXmZXUAwSs1w961/1WEE65e8p QW/dMaPxABlnKjuchjF8xumnDp2xdUFigFI09ipYWdP8fyjLokVMf9JQmlH9gARDHxqk QiNA==
MIME-Version: 1.0
X-Received: by 10.180.73.239 with SMTP id o15mr3705649wiv.36.1380824321836; Thu, 03 Oct 2013 11:18:41 -0700 (PDT)
Received: by 10.216.165.5 with HTTP; Thu, 3 Oct 2013 11:18:41 -0700 (PDT)
In-Reply-To: <CAMpDgVw2MkRZTtDqoOpLfAH2bD8i8Q+ojk2mXnbAoA4s5R8dfg@mail.gmail.com>
References: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com> <CAMpDgVw2MkRZTtDqoOpLfAH2bD8i8Q+ojk2mXnbAoA4s5R8dfg@mail.gmail.com>
Date: Thu, 03 Oct 2013 13:18:41 -0500
Message-ID: <CAK3OfOhYs3QYoeKpaeTjeY=oqnCp0yLCTuYBJGm7Q8x=C=LohA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Peter Patel-Schneider <pfpschneider@gmail.com>
Content-Type: text/plain; charset="UTF-8"
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: Thu, 03 Oct 2013 18:28:45 -0000

On Thu, Oct 3, 2013 at 12:34 PM, Peter Patel-Schneider
<pfpschneider@gmail.com> wrote:
> The proposal is to *change* JSON in a way that would break some current JSON
> parsers and, worse, break some current consumers of JSON, to get closer
> syntactic conformance with the ECMAScript JSON implementation.

Not really: you can have two definitions of top-level and describe
their interoperability characteristics (the original array-or-object
interops best).

In practice many, many JSON parsers already support at least an option
for top-level value types other than array/object.

> If there is a goal to align JSON with the ECMAScript JSON implementation,
> then I suggest that requiring EMCAScript numbers is much more important and
> that even officially requiring support for unpaired UTF-16 surrogate code
> units is more important.

I think the OP wanted one cheap ECMAScript compat improvement.  I
agree that this is the "cheapest" such improvement.  All the others
you propose have significantly more impact on existing implementations
for them to be able to support the ECMAScript variant.

I'd settle for noting the differences between IETF JSON and ECMAScript.

Nico
--

v2.23.0 | Report a Bug | By Email