Re: [Json] Add Extension to JS MIME

Allen Wirfs-Brock <allen@wirfs-brock.com> Mon, 14 August 2017 18:31 UTC

Return-Path: <allen@wirfs-brock.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 4A50B1323C4 for <json@ietfa.amsl.com>; Mon, 14 Aug 2017 11:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wthG7FReABIr for <json@ietfa.amsl.com>; Mon, 14 Aug 2017 11:31:13 -0700 (PDT)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D7921323B5 for <json@ietf.org>; Mon, 14 Aug 2017 11:31:13 -0700 (PDT)
X-MHO-User: bf2feb20-811e-11e7-950d-03a3531dacf2
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 50.39.217.219
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from [192.168.254.4] (unknown [50.39.217.219]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id bf2feb20-811e-11e7-950d-03a3531dacf2; Mon, 14 Aug 2017 18:31:12 +0000 (UTC)
From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Message-Id: <BE1E82B2-0761-4294-A73C-8F0F7FB03F15@wirfs-brock.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8830C186-3C3B-443E-BC36-8ED72B0418ED"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 14 Aug 2017 11:31:09 -0700
In-Reply-To: <CANnEKUaFaFwxsEVA1vUyosPn8e-+jG9ESpAvHdxvw1R+LadN9A@mail.gmail.com>
Cc: "Matthew A. Miller" <linuxwolf@outer-planes.net>, art-ads@ietf.org, json@ietf.org
To: Bradley Meck <bradley.meck@gmail.com>
References: <CANnEKUb_pd_T6h5O4gEYttv4wWCcTNmeNvBw+TCiRtsqVgxkQg@mail.gmail.com> <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> <CANnEKUaFaFwxsEVA1vUyosPn8e-+jG9ESpAvHdxvw1R+LadN9A@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/KYVAzB1eEwYlEMJuxkyiCaPY4lw>
Subject: Re: [Json] Add Extension to JS MIME
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 18:31:16 -0000

> On Aug 14, 2017, at 11:00 AM, Bradley Meck <bradley.meck@gmail.com> wrote:
> 
> TC39 / ECMA262 has said that they are not in the business of the MIME in https://github.com/tc39/ecma262/issues/322 <https://github.com/tc39/ecma262/issues/322> . So there won't be any need to change references to that standard.

Actually the references (and some of the referencing text) probably should be updated given that 4329 says:

"The types defined in this document are applicable to scripts written in [JS15] and [ECMA], respectively, as well as to scripts written in   a compatible language or profile such as [EcmaCompact].

This document does not address scripts written in other languages. In particular, future versions of JavaScript, future editions of [ECMA], and extensions to [ECMA], such as [E4X], are not directly addressed.  This document may be updated to take other content into account.
“

and the reference [ECMA]] is specifically to ECMA-262, Edition 3.  Also [EcmaCompact] and [E4X] have been withdrawn as Ecma standards   [JS15] is very obsolete and a vendor specific document.

Given that ECMA-262 is not revised on a year scheduled, the [ECMA] reference should probably change to an undated reference.

Allen