IETF Logo Mail Archive

Re: [Json] JSON & ECMA

Eliot Lear <lear@cisco.com> Mon, 25 March 2013 15:41 UTC

Return-Path: <lear@cisco.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 E83E021F84EF for <json@ietfa.amsl.com>; Mon, 25 Mar 2013 08:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.499
X-Spam-Level:
X-Spam-Status: No, score=-110.499 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 fv-Ahm5Q9idq for <json@ietfa.amsl.com>; Mon, 25 Mar 2013 08:41:25 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id B056321F84DF for <json@ietf.org>; Mon, 25 Mar 2013 08:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1883; q=dns/txt; s=iport; t=1364226084; x=1365435684; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=b8IVzsOv0UCMuQaVCQ+2Z1VXwtzZGZZWDgcp+pcz048=; b=f2ZVeFzQqkV6u/zM6T2z17GAzPbzB2fn2uAkIWULKCqe8VHTHt3/riuX meMZMpCE4jDjoemEWeto6mV/AxRd5OV5Xw8DaTLrt6nDNmqc215oJbSnG cwKD2GtTDtdUxy1pcQYgQgkXAcQsoMlT3jiZxicVOQGRh6eJa2S/aUYBm c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAARvUFGQ/khN/2dsb2JhbABEiEq9GYIDFnSCJAEBAQQjTwYBEAsEAQkKCRYLAgIJAwIBAgFFBg0BBwEBEIgAsFOSLY8YB4ItgRMDkmeEAJEEgws7
X-IronPort-AV: E=Sophos; i="4.84,905,1355097600"; d="scan'208,217"; a="12419208"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 25 Mar 2013 15:41:23 +0000
Received: from dhcp-10-55-89-38.cisco.com (dhcp-10-55-89-38.cisco.com [10.55.89.38]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2PFfM4e008728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Mar 2013 15:41:23 GMT
Message-ID: <51507022.6030100@cisco.com>
Date: Mon, 25 Mar 2013 16:41:22 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Tim Bray <tbray@textuality.com>
References: <C68CB012D9182D408CED7B884F441D4D1E883516CD@nambxv01a.corp.adobe.com> <6F8EC872-CF09-428A-A675-E96462DD5972@vpnc.org> <CAHBU6isfWR=qP5aK0T=tH7ozFF+JjQh+rNB=m7F-5h=vK=MYPQ@mail.gmail.com>
In-Reply-To: <CAHBU6isfWR=qP5aK0T=tH7ozFF+JjQh+rNB=m7F-5h=vK=MYPQ@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------020301060304040305060205"
Cc: json@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, Larry Masinter <masinter@adobe.com>
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: Mon, 25 Mar 2013 15:41:26 -0000

Tim,

On 3/16/13 11:53 PM, Tim Bray wrote:
>
>
> Does the community get a chance to comment? I would argue strongly
> against any relationship with ECMA given an opportunity.
>

I'd like to understand your concerns.  We are already normatively
referencing ECMA-262 in RFC-4627.  It's important to establish who the
design authority is.  At least one person at ECMA thinks they are, for
what it's worth.  That argues for some communication to avoid two
competing standards.

Eliot

v2.23.0 | Report a Bug | By Email