Re: [Json] Add Extension to JS MIME

Allen Wirfs-Brock <> Mon, 14 August 2017 18:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4A50B1323C4 for <>; Mon, 14 Aug 2017 11:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wthG7FReABIr for <>; Mon, 14 Aug 2017 11:31:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9D7921323B5 for <>; Mon, 14 Aug 2017 11:31:13 -0700 (PDT)
X-MHO-User: bf2feb20-811e-11e7-950d-03a3531dacf2
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from [] (unknown []) by (Halon) with ESMTPSA id bf2feb20-811e-11e7-950d-03a3531dacf2; Mon, 14 Aug 2017 18:31:12 +0000 (UTC)
From: Allen Wirfs-Brock <>
Message-Id: <>
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: <>
Cc: "Matthew A. Miller" <>,,
To: Bradley Meck <>
References: <> <> <>
X-Mailer: Apple Mail (2.3273)
Archived-At: <>
Subject: Re: [Json] Add Extension to JS MIME
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Aug 2017 18:31:16 -0000

> On Aug 14, 2017, at 11:00 AM, Bradley Meck <> wrote:
> TC39 / ECMA262 has said that they are not in the business of the MIME in <> . 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.