[Json] Possible next work for the WG

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 16 October 2013 02:51 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 CB97221F9D30 for <json@ietfa.amsl.com>; Tue, 15 Oct 2013 19:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 pN3jtxNChwRT for <json@ietfa.amsl.com>; Tue, 15 Oct 2013 19:51:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5C99711E8209 for <json@ietf.org>; Tue, 15 Oct 2013 19:51:53 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id r9G2pqXF029191 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Tue, 15 Oct 2013 19:51:52 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org>
Date: Tue, 15 Oct 2013 19:51:50 -0700
To: JSON WG <json@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [Json] Possible next work for the WG
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 16 Oct 2013 02:51:53 -0000

Greetings again. While our AD ponders the 4627bis document (probably on its way to IETF Last Call), the Working Group can start to think about what it wants to do next, if anything. The chairs have heard of at least four topics that the WG might or might not want to add to its charter:

- I-JSON (a profile of JSON with some interoperability issues nailed down)

- Best practices document for JSON implementers and folks who use JSON in protocols

- Canonicalization rules so that two JSON texts can be compared for equality

- Requirements for JSON schema (which will be needed before the WG considers working on an actual schema)

The chairs request general comments on these or additional topics for the WG. If there is interest, we will re-open the topics on separate threads, and then put together a proposal for rechartering. If people really want this WG to shut down after 4627bis is done without doing additional work, that is a valid view as well. 

Note that we have also heard requests for non-compatible additions to the JSON syntax, particularly for comments and byte-oriented data. If the WG wanted to adopt this work, we would probably need to talk with our ADs and the IAB because that might be better handled by Ecma in a possible revsion to ECMA-404.

--Matt Miller and Paul Hoffman