Re: [Json] Possible next work for the WG

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 16 October 2013 17:13 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 8068411E8118 for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:13:59 -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 mWU389sR227R for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:13:59 -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 7D9A511E8192 for <json@ietf.org>; Wed, 16 Oct 2013 10:13:56 -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 r9GHDsCJ063007 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Wed, 16 Oct 2013 10:13:55 -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]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20131016165406.GA9701@mercury.ccil.org>
Date: Wed, 16 Oct 2013 10:13:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDA6D428-0FA8-4E78-A9AD-C7C345EA1930@vpnc.org>
References: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org> <20131016165406.GA9701@mercury.ccil.org>
To: JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1510)
Subject: Re: [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 17:13:59 -0000

<no hat>

On Oct 16, 2013, at 9:54 AM, John Cowan <cowan@mercury.ccil.org> wrote:

>> - Requirements for JSON schema (which will be needed before the WG
>> considers working on an actual schema)
> 
> As reinvented wheels are often hexagonal, I think if we are going to
> do this we should adopt draft-zyp-json-schema-04 as a base document
> for further work.  

That draft is a specific schema proposal, not a set of requirements. If the WG first agrees on a set of non-ocean-boiling requirements, proposals to meet them will naturally follow. This would not be reinventing: it would be designing from requirements instead of the other way around.

--Paul Hoffman