[Json] Proposed document set from this WG

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 20 February 2013 00:47 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 4D7FA21F87CD for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 16:47:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level:
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0bkdeqQi2WJg for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 16:47:23 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CA03A21F87C3 for <json@ietf.org>; Tue, 19 Feb 2013 16:47:23 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r1K0lMlk056314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Tue, 19 Feb 2013 17:47:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <711B5AAF-4CAB-414C-8553-C84493FB005E@vpnc.org>
Date: Tue, 19 Feb 2013 16:47:22 -0800
To: "json@ietf.org" <json@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [Json] Proposed document set from this WG
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: Wed, 20 Feb 2013 00:47:24 -0000

Straw-man, personal opinions.

1) JSON base, 4627bis
   Target: current JSON users
   Current: grammar, encoding, parser rules, generator rules, MIME type registration)
   New: Internet transfer rules, list of changes from 4627

2) JSON value comparison
   Target: systems that want to compare two JSON values (usually objects) for equivalence
   Character equivalence rules
   Unicode normalization (if any)
   Numeric normalization (if any)

3) JSON document description
   Target: systems that want to be sure an incoming document is what they expect it to be
   Might be schema-like, might just be content rules

Both #2 and #3 are useful, but to a much smaller audience than #1. #2 and #3 are also much more exciting than #1, but that excitement in the XML world has led to efforts that have been actively harmful.

4) JSON patching and testing
   Target: systems that use JSON as a data model and need to change data

#4 is even more marginal than #2 and #3, but would need to be done in a JSON-focused WG.

5+) JSON format for X
   Target: systems that use data of type X (personal information, calendar items, DNS records, ...)

The WG might *not* be chartered to do any of #5+, and each X needs its own mailing list. Draft updates might be mentioned on the WG mailing list.

--Paul Hoffman