Re: [Json] JSON & ECMA

Tim Bray <tbray@textuality.com> Fri, 15 March 2013 20:03 UTC

Return-Path: <tbray@textuality.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 CF02221F85BB for <json@ietfa.amsl.com>; Fri, 15 Mar 2013 13:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 ZWkDXF5jZAqL for <json@ietfa.amsl.com>; Fri, 15 Mar 2013 13:03:49 -0700 (PDT)
Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by ietfa.amsl.com (Postfix) with ESMTP id B241C21F85AC for <json@ietf.org>; Fri, 15 Mar 2013 13:03:48 -0700 (PDT)
Received: by mail-lb0-f174.google.com with SMTP id l12so3116547lbo.33 for <json@ietf.org>; Fri, 15 Mar 2013 13:03:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=GKxoZrIcdLZRjW9RA6DAEsAQY7KTkaAupzeYa/dpF8A=; b=kH/KlGzGRZ02RDLuZONbmsjozp9366ekMveWbg0MbCjnzkeqh/CZrHX78Yw9GR6Qe+ J3D7P5Ts8XXaXSHQvERQqn+qPUUk5w0Dyq6BiB0hDAAl7a9cRDYxXhOoZW2VDMXyM1kT SegzDrXA/O7Kqs4YXCxqtdDYDCYwRoZ2+76ultsNSim95rpAIuVvlC1DH+qcN++IJ6lb zBktGQTQ8g1uaM5iYRiKMcN8bCdvw0JurCCF4+VqXCAk8Tm0gHfnsflSnS2SDlatyyFz yZPHd2td79ShofrlGX1/29P48wUgw8MMHB53HAWU05dKYLXKxEn3reD5USItwwCj6u6B IYxQ==
MIME-Version: 1.0
X-Received: by 10.152.108.1 with SMTP id hg1mr6793053lab.12.1363377827145; Fri, 15 Mar 2013 13:03:47 -0700 (PDT)
Received: by 10.114.37.228 with HTTP; Fri, 15 Mar 2013 13:03:46 -0700 (PDT)
X-Originating-IP: [172.19.244.230]
In-Reply-To: <51437A60.607@crockford.com>
References: <51437A60.607@crockford.com>
Date: Fri, 15 Mar 2013 13:03:46 -0700
Message-ID: <CAHBU6isT4TUYiPRPC9Fi75_=OLHcHHsrqxGWr72qv0QL2rDDxw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Douglas Crockford <douglas@crockford.com>
Content-Type: multipart/alternative; boundary=bcaec54ee22415031904d7fc2371
X-Gm-Message-State: ALoCoQmLLyP9OwRB8pxk6hohNPe5UZ/eq21tFXCd4uLz+UJd0+dTpxR/Bh7XxW6302acAHcA4rWQ
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] JSON & ECMA
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: Fri, 15 Mar 2013 20:03:50 -0000

It should live somewhere with good googlejuice that has moderately sane
editorial processes and where the likelihood that someone will grab the
steering wheel and do something stupid is acceptably low.  IETF is
plausible on that metric.

In my personal experience (which may be unusual), ISO and (to a greater
degree) ECMA combine corruption and ineptitude on an epic scale, so that
association would be a negative. Others may differ. -T


On Fri, Mar 15, 2013 at 12:45 PM, Douglas Crockford
<douglas@crockford.com>wrote;wrote:

> The JSON Standard was inspired by ECMA's ECMAScript Standard, Third
> Edition, but is not dependent on it. ECMAScript Fifth Edition does not
> define JSON, but implements the JSON standard in ECMAScript. Changes in the
> ECMAScript Standard have no impact on JSON. JSON is language independent.
>
> There is a question about where the JSON Standard should live. One theory
> is that it should be at IETF, because there is an informational RFC that
> associated JSON with the MIME type application/json. The other theory is
> that the standard should live at ECMA because JSON was initially derived
> from ECMAScript, and because ECMA is related to ISO.
>
> I do not know how this should be decided.
> ______________________________**_________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/**listinfo/json<https://www.ietf.org/mailman/listinfo/json>
>