[Json] FYI: January 28 2015 Meeting Notes

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 09 February 2015 10:26 UTC

Return-Path: <derhoermi@gmx.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F8D1A0193 for <json@ietfa.amsl.com>; Mon, 9 Feb 2015 02:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.43
X-Spam-Level:
X-Spam-Status: No, score=-0.43 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_RP_RNBL=1.31, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 h1xhrBdzMLVN for <json@ietfa.amsl.com>; Mon, 9 Feb 2015 02:26:51 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 891261A0181 for <json@ietf.org>; Mon, 9 Feb 2015 02:26:51 -0800 (PST)
Received: from netb ([89.204.137.153]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M8pKi-1YSUmJ3LrQ-00C8Hz for <json@ietf.org>; Mon, 09 Feb 2015 11:26:49 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: json@ietf.org
Date: Mon, 09 Feb 2015 11:26:48 +0100
Message-ID: <tm2hda9gi7u9somrqj45u04bo6dtb48ot6@hive.bjoern.hoehrmann.de>
References: <CAHfnhfoW+JjhAoSPXcS0CabEYLDio2Mqz1A+XfA-ygE6zzvtgw@mail.gmail.com>
In-Reply-To: <CAHfnhfoW+JjhAoSPXcS0CabEYLDio2Mqz1A+XfA-ygE6zzvtgw@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:3pfwMHKVoBkeJ2AmfRRTf/8H6Jk5soRf8zMVSPsEtzfGUaQEcQ/ 6OHJlr9r1wY29YrqxQKT2S2AI/SxB8a/HarJq5BYLk+2uSKyKYgRun2FO0fhplDIgcWxlv0 lYoX3FPUhtdfMZvedgXXtmyuCs6icx6ECevaFWwRAsS/YYC1YyjjBqucSnt93hx0aoy0yEv eQL61QfGTBE/RlKHCidWA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/AEVjp6KlvU3Zy_XshYaJGd0yy4Q>
Subject: [Json] FYI: January 28 2015 Meeting Notes
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 09 Feb 2015 10:26:54 -0000

* Rick Waldron wrote:
>[...]

http://article.gmane.org/gmane.comp.lang.javascript.ecmascript4.general/37184

This might be of interest to the JSON community:

>## Report from the Ecma Secretariat
>(Istvan Sebastian)
>
>IS: Strange JSON development: The government of the Netherlands wants to
>get an EU recognition on IETF's JSON future standard as part of the
>European Commission's Multi-Stakeholder Platform. Netherlands submitted 27
>IETF standards to the Multi-Stakeholder Platform, and IETF's JSON happens
>to be among them. Normally only long-standing in the market already proved
>standards should be recognized. Also no "consortium specification" should
>be recognized where appropriate International Standard (like of ISO, IEC,
>ITU) exists. JSON in ECMA-262 is already part of ISO/IEC 16262:2011. In
>addition TC39 has standardized in 2013 ECMA-404 (JSON). We had originally a
>TC39 decision to fast-track it to JTC1, but after discussion the GA in
>December 2013 has approved the possibility of a Postal Balot on the JTC1
>fast track upon a new request  from TC39.  The iisue has been reported to
>the last Ecma GA and was worried about the situation.
>
>WH and IS: [Discussion about what the Multi-Stakeholder Platform is and its
>implication on governmental activities]
>
>IS: Recommend resuming the fast-track of ECMA-404 (JSON).
>
>AWB: We don't currently have an editor for the JSON spec.  Who wants to do
>it?
>
>CM: I volunteer!
>
>WH: Timeline? June GA?
>
>IS: Will discuss it with ECMA management. Might do it earlier via a letter
>ballot.

regards,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 · http://www.bjoernsworld.de
 Available for hire in Berlin (early 2015)  · http://www.websitedev.de/