IETF Logo Mail Archive

Re: [Json] Schemas & so on

Erik Wilde <erik.wilde@dret.net> Tue, 03 May 2016 02:17 UTC

Return-Path: <erik.wilde@dret.net>
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 CF82A12D540 for <json@ietfa.amsl.com>; Mon, 2 May 2016 19:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.net
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 vCWa2x3QPaTj for <json@ietfa.amsl.com>; Mon, 2 May 2016 19:17:30 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C664512D53B for <json@ietf.org>; Mon, 2 May 2016 19:17:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject; bh=4h8M66mtY5XhMd4VOTTNXbKdmtkWQRu2jHe+3/0SxQc=; b=C8UQi99UEh6GHODzhTygMwnCi8 UhVyQyJFgn2VZkorxPl0Dw6qoPfc/p2zglDQxMSHLZ6wORyccv+VK3RHj5yOPIFeKk4Bqrgou7akV JeZ/zxI2nLgK4I2AOM+IkWJCHi60g6RYCAP1LjSoHtJwUZjWCXYSKA5w9X5G4xMu86vw0QTn7kaHC R16g6dBHZZoVXRD7+zVIRPOU4wCw3uL0R5CcGeVnYGLxHQkDk5pd9PKA9DHzuEL704moEaBY9L0lD nAjyUuBxtuR8Z/sGj7uEqwF7Fy7NQTggERbeHOCGlbkHP7hJlgZMCQOYAt8PHoEeuX4JtJWdn1ky+ /xFl2gSQ==;
Received: from 108-67-65-66.lightspeed.sntcca.sbcglobal.net ([108.67.65.66]:59459 helo=[192.168.1.77]) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from <erik.wilde@dret.net>) id 1axPtw-0005px-E7; Mon, 02 May 2016 22:17:28 -0400
To: Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>
References: <CAHBU6itCV9MXmALdKtE9-vjUPG6-6ZqdqzrmZkcEzSUysi3S-w@mail.gmail.com> <AC93811D-A16A-4527-B2EB-C6A9FC6D4F17@mnot.net>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <4bb21809-bb40-7a3e-b7c7-f37da0976ea2@dret.net>
Date: Mon, 02 May 2016 19:17:27 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <AC93811D-A16A-4527-B2EB-C6A9FC6D4F17@mnot.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/IzIe0p71mV0wXX_Acd96mPxB_iU>
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Schemas & so on
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 03 May 2016 02:17:35 -0000

On 2016-05-02 17:10, Mark Nottingham wrote:
> It strikes me that it might be worth writing down what we think is good in such a beast, and what would be not-good. Getting agreement on that might be... interesting, but if we had such a document (or maybe just a wiki page), we'd be able to evaluate the current contenders, at least.

fwiw, after the discussion started on this list, it got me thinking 
because as mark noted, the discussion tends to start and then stop 
without a truly successful candidate emerging (so far). i think that 
there will be one, eventually, and over the weekend wrote down my 
thoughts about it here:

http://dret.typepad.com/dretblog/2016/05/json-schema-why-and-how.html

cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |

v2.23.0 | Report a Bug | By Email