IETF Logo Mail Archive

Re: [Json] Another problematic JSON Schema use-case

John Cowan <cowan@mercury.ccil.org> Thu, 26 May 2016 21:45 UTC

Return-Path: <cowan@ccil.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 B2A9612D1DF for <json@ietfa.amsl.com>; Thu, 26 May 2016 14:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.027
X-Spam-Level:
X-Spam-Status: No, score=-4.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 R2o0uI7Z9Vns for <json@ietfa.amsl.com>; Thu, 26 May 2016 14:45:24 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A8B912D9C3 for <json@ietf.org>; Thu, 26 May 2016 14:45:24 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1b635n-00051x-21; Thu, 26 May 2016 17:45:23 -0400
Date: Thu, 26 May 2016 17:45:22 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Peter Cordell <petejson@codalogic.com>
Message-ID: <20160526214522.GE19074@mercury.ccil.org>
References: <CAMm+Lwg2rWh0_gjXnSAEAvWtsMO1U3UiA8jsBzc+rRR6fiKcJg@mail.gmail.com> <20160526173719.GA19074@mercury.ccil.org> <064f4df2-75d5-6952-cd18-e22e7510b3a6@codalogic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <064f4df2-75d5-6952-cd18-e22e7510b3a6@codalogic.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/011ro9Ec4sZL2xIi6BYa7cVMKqA>
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Another problematic JSON Schema use-case
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: Thu, 26 May 2016 21:45:26 -0000

Peter Cordell scripsit:

> I think sort of thing in JCR by having a directive such as
> #infer-types, e.g.

Pretty good.

> I think that would be useful as 'by-example' is perhaps an easy way
> to start creating a schema, but I feel you'd want to go beyond what
> it can offer within a matter of hours.

Remember that I'm aiming only at static typing, not general validation.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
Promises become binding when there is a meeting of the minds and consideration
is exchanged. So it was at King's Bench in common law England; so it was
under the common law in the American colonies; so it was through more than
two centuries of jurisprudence in this country; and so it is today.
       --Specht v. Netscape

v2.23.0 | Report a Bug | By Email