Re: [apps-discuss] JSON Schema considered harmful

Phillip Hallam-Baker <hallam@gmail.com> Wed, 19 September 2012 21:49 UTC

Return-Path: <hallam@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 8304721E80B6 for <apps-discuss@ietfa.amsl.com>; Wed, 19 Sep 2012 14:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.625
X-Spam-Level:
X-Spam-Status: No, score=-3.625 tagged_above=-999 required=5 tests=[AWL=-0.627, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 q0NDeDVBUA6L for <apps-discuss@ietfa.amsl.com>; Wed, 19 Sep 2012 14:49:10 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8B22621E80B4 for <apps-discuss@ietf.org>; Wed, 19 Sep 2012 14:49:10 -0700 (PDT)
Received: by oagn5 with SMTP id n5so1083370oag.31 for <apps-discuss@ietf.org>; Wed, 19 Sep 2012 14:49:10 -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; bh=pQwj+cAvJavmGFwKo1mfBDrI3ErTTBZ6mRUmaJIBHNA=; b=0LaoGPvMDRgemjIZh1ikCgmYapc/5oy0Eem6KKdQl7Eo+3fYxVzN0vfWvEUbbBZbme mYeuFndqInnl94ValJnRfPsNbfuEqxW1Cr+7HxegO1qgO2UnKiLDo2zWcuQQ93zluyRW +UiW9iAD6w9jxL1+lCf3AZHSxMb6xHABpHJXjMiZB1gko3pvVMuICApIwx6X5MCK5d6l F1QtI5dgdrE67htp9HZSNXufpEgIZtC8Q0x2icV/9ouWk2qRILMwekTOLbKHRjV1E/FZ Cr7zPmv80z33WoaKioykp2mF9NHwTvYjaV6Zl3L4LsxDBI6K6FRzLg2KaPFvVXgTU1CS CSAQ==
MIME-Version: 1.0
Received: by 10.60.170.229 with SMTP id ap5mr3947880oec.101.1348091350219; Wed, 19 Sep 2012 14:49:10 -0700 (PDT)
Received: by 10.76.29.50 with HTTP; Wed, 19 Sep 2012 14:49:10 -0700 (PDT)
In-Reply-To: <CALcybBAwYPGep4QMGK1Bx0SSmB=yTXRbjH9VGPZ0MKHcQzr_Mw@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> <CALcybBDkOOfWq-qzR-6mtU8TULcp4BfS0h=WRKJZDSh+G8M9zw@mail.gmail.com> <CAMm+LwgNZuLYvyhayA2JQtH36e05HJWbdkKUt6yei10p5p-XRA@mail.gmail.com> <CALcybBAwYPGep4QMGK1Bx0SSmB=yTXRbjH9VGPZ0MKHcQzr_Mw@mail.gmail.com>
Date: Wed, 19 Sep 2012 17:49:10 -0400
Message-ID: <CAMm+LwgJRAK6k_xp1Zky84owtWDD7m7ptZJpFsGwe80ikVmQBQ@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Francis Galiegue <fgaliegue@gmail.com>
Content-Type: multipart/alternative; boundary="bcaec54b4ac00dfacd04ca14fa20"
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 21:49:11 -0000

On Wed, Sep 19, 2012 at 5:36 PM, Francis Galiegue <fgaliegue@gmail.com>wrote:

> On Wed, Sep 19, 2012 at 11:28 PM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
> [...]
> >>
> >> There is no maxOccurs, no minOccurs. Where on earth did you see that?
> >
> >
> > http://tools.ietf.org/html/draft-zyp-json-schema-03
> >
> >     5.13. minItems . . . . . . . . . . . . . . . . . . . . . . . . . 11
> >      5.14. maxItems . . . . . . . . . . . . . . . . . . . . . . . . . 11
> >
> [...]
> >
> > That would seem to be the same as the XML Schema constraints only someone
> > changed the name.
> >
>
> This is the old specification. It is being redone.
>

So when you were attacking me for not reading the specification you were
referring to a version that has not yet been submitted as a draft?

You really are a piece of work.


And you don't understand JSON at all, do you? Can you tell a JSON
> array from a JSON object? From what I read: no...


I think that we are reaching the point where I suggest that you no longer
be heard. You keep making these personal attacks. In fact I think they have
somewhat marred your whole approach from the start.

You really don't have standing to lecture other people on what they do or
do not understand.

I didn't say I was referring to objects when I mentioned the maxItems
thing. I used the XML Schema terminology but that hardly changes my case
that the feature is unnecessary in XML Schema and almost certainly
unnecessary here.


Before you dig yourself in deeper I suggest you find out who you are
directing your attacks at and decide whether my being unable to understand
you would be a fault of mine, a defect in your presentation or a confusion
in the case you present.



> >> 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!
> >
> >
> > I read the Internet draft. If you are refering to a different spec then
> we
> > have an even bigger problem.
> >
>
> YOU have a problem. You don't know how to read.


I don't know how to read documents that have not been submitted.

Argument from undisclosed specification is not exactly convincing.

-- 
Website: http://hallambaker.com/