Re: [apps-discuss] JSON Schema considered harmful

Francis Galiegue <fgaliegue@gmail.com> Wed, 19 September 2012 20:49 UTC

Return-Path: <fgaliegue@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E239A21E8064 for <apps-discuss@ietfa.amsl.com>; Wed, 19 Sep 2012 13:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.305
X-Spam-Level:
X-Spam-Status: No, score=-3.305 tagged_above=-999 required=5 tests=[AWL=-0.306, BAYES_00=-2.599, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_LOW=-1]
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 YLHT3S-DUniY for <apps-discuss@ietfa.amsl.com>; Wed, 19 Sep 2012 13:49:58 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 21C3421E8034 for <apps-discuss@ietf.org>; Wed, 19 Sep 2012 13:49:58 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so1888420vbb.31 for <apps-discuss@ietf.org>; Wed, 19 Sep 2012 13:49:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=h6UfAc3jtHn/isE3AmGnsu7u5nNgRPyf1WoFskYv3rE=; b=efQJTTmVhuB9AyTD3jkKIcDv6N0KEHn/FeNTYRnBTEdong25hdKADg+we/5IxV8rYB JVwLK6bDq1ee5UQERk/pgkZ6kvmjxj6WG5dzb0pCwnFJAijm6jOxC78MFIr8cX4xkuUQ G5JcpDwla2yXMd85wgxSWgK3f4tWLKHTRBvEo12B/G+mjn48u+nsPgEpNIs/rHmiIrki AcfD89Nd6PJ2zTSc088bj/Q5AhBlkO+fsbi6girBKTGKOxv0rciG9eS+Xu6Bji0EUiRN s2jIpbc384i5h60lPesQGg+2IYQIBG0kBb2lGTN+X6dXbXcWqA0MABpab3V6CzxHuOug zF0Q==
MIME-Version: 1.0
Received: by 10.52.27.229 with SMTP id w5mr2089143vdg.126.1348087797333; Wed, 19 Sep 2012 13:49:57 -0700 (PDT)
Received: by 10.52.23.103 with HTTP; Wed, 19 Sep 2012 13:49:57 -0700 (PDT)
In-Reply-To: <CAMm+LwgQLc8v+V7JhEr4zEw37e0ovrUkFy0RZKOszg1FbkMjeA@mail.gmail.com>
References: <CAMm+LwjYj0gd3Cxjj8WFcLy-zgBwfVDCPaRGcNSgOHD9m_07yw@mail.gmail.com> <CALcybBCqAMLi8v61u1+oPpHaMpHrK4ufUm6fUUyMb8XMmz8JSg@mail.gmail.com> <CAMm+LwiyohqhRA+m3M0ViSkt74q3yOfUkZj8b-upc4V_qUv22g@mail.gmail.com> <CALcybBCBScuO797yBmY3c_wRUa98=DYwN2rXXbq41pE2GHK4vw@mail.gmail.com> <CAMm+LwgQLc8v+V7JhEr4zEw37e0ovrUkFy0RZKOszg1FbkMjeA@mail.gmail.com>
Date: Wed, 19 Sep 2012 22:49:57 +0200
Message-ID: <CALcybBDkOOfWq-qzR-6mtU8TULcp4BfS0h=WRKJZDSh+G8M9zw@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] JSON Schema considered harmful
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 20:49:59 -0000

On Wed, Sep 19, 2012 at 9:14 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> Excuse me but you just did refer to the 'Github JSON Schema group'
>
> And yes, I have read the purported JSON Schema spec. It is far too complex
> with far too many options.
>
> Having written protocols using schemas, I can tell you for example that you
> don't need maxOccurs or minOccurs, the only options that make sense 95% of
> the time are one or none [0..], exactly one [1..1], at least one [1..MAXINT]
> or any [0...MAXINT].
>

There is no maxOccurs, no minOccurs. Where on earth did you see that?

No, you decidedly DID NOT make even an ATTEMPT to read the proposed
specifications. It's in the README.md on the main page, damnit!

> The spec replicates XML Schema in JSON.

Yet another proof of my statement above.

Read what is proposed before making any comments, and if you have any
_constructive_ criticism, I'd be glad to hear it.

Not before.

-- 
Francis Galiegue, fgaliegue@gmail.com
JSON Schema: https://github.com/json-schema
"It seems obvious [...] that at least some 'business intelligence'
tools invest so much intelligence on the business side that they have
nothing left for generating SQL queries" (Stéphane Faroult, in "The
Art of SQL", ISBN 0-596-00894-5)