Re: [apps-discuss] JSON Schema considered harmful
Phillip Hallam-Baker <hallam@gmail.com> Thu, 20 September 2012 16:33 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 A017921F870B for <apps-discuss@ietfa.amsl.com>; Thu, 20 Sep 2012 09:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.215
X-Spam-Level:
X-Spam-Status: No, score=-3.215 tagged_above=-999 required=5 tests=[AWL=-1.283, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 d51ZnhFiQoR3 for <apps-discuss@ietfa.amsl.com>; Thu, 20 Sep 2012 09:33:16 -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 AC27621F86DE for <apps-discuss@ietf.org>; Thu, 20 Sep 2012 09:33:16 -0700 (PDT)
Received: by oagn5 with SMTP id n5so2018496oag.31 for <apps-discuss@ietf.org>; Thu, 20 Sep 2012 09:33:16 -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=KM4mT0VxMv2BZcy2AoePzFcCWAwU2KPaz953F7/gaXg=; b=QQBJwb5Znoqc7TveRNem0lzf8zU72/ykgbbctRalI9EQOU4gGAtWwRp7qdnIXQGPqb Wf6KHq2BvpeABhcRQQb0/lNj/SPmJKu2es0uZ/g2dn+OyMV0/6g+nUV8An58I0/z8evh /ExiH/R8fzBCVzriX6R9Iikyb+MRCCCEAvcYK6nLxe2T58f7Rx2mKwBz9Bg4WgmIgwV2 I12DMOyw/gbY/expl1I/qm9rCMlJ6kCcBRFSqSkoWD5x6p3n1PScjkfL0Z5BtZC5juCc MJzZh6uGXFDfJ+ucEv7e31fcyRMdoEO/+0l7WpLJixRYyElfIcmuIFznAyy+jjc0ju/T qaBA==
MIME-Version: 1.0
Received: by 10.60.29.72 with SMTP id i8mr1718958oeh.26.1348158796313; Thu, 20 Sep 2012 09:33:16 -0700 (PDT)
Received: by 10.76.18.237 with HTTP; Thu, 20 Sep 2012 09:33:16 -0700 (PDT)
In-Reply-To: <505B43B3.7050503@berkeley.edu>
References: <CAMm+LwjYj0gd3Cxjj8WFcLy-zgBwfVDCPaRGcNSgOHD9m_07yw@mail.gmail.com> <999913AB42CC9341B05A99BBF358718D01DF0684@FIESEXC035.nsn-intra.net> <CAK3OfOgU-Kepre2Z2dg_S8DAVCU413SRvuWMvJcC3BmE0BjNbQ@mail.gmail.com> <505B43B3.7050503@berkeley.edu>
Date: Thu, 20 Sep 2012 12:33:16 -0400
Message-ID: <CAMm+LwhM-zQ2+APWpmOVdhBvxDM7-SvT__pp2f4oc84RnTWGow@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Erik Wilde <dret@berkeley.edu>
Content-Type: multipart/alternative; boundary="e89a8fb1f80627b3ea04ca24aeed"
Cc: 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: Thu, 20 Sep 2012 16:33:17 -0000
Actually you can do a lot more than Wildcards in XML Schema. And no, it is not a good idea to try. That is why SAML 2.0 became necessary as people had told me to use model groups in SAML 1.0. On Thu, Sep 20, 2012 at 12:26 PM, Erik Wilde <dret@berkeley.edu> wrote: > hello all. > > > On 2012-09-20 09:02 , Nico Williams wrote: > >> So, while I have no problem with specific complaints about >> shortcomings of one or another schema language, I do object to the >> idea that because they fail to denote semantics we should not use >> them. >> > > that's my general feeling as well. schemas are not able to and not > designed to completely capture protocol semantics, but they provide a good > starting point, and allow some level of formalism which then needs to be > augmented with documentation. > > > Regarding specific complaints... I am not very familiar with XML >> Schema, so I can't say much about it and extensibility. ASN.1 has >> extensibility rules nowadays, and often uses of ASN.1 predating >> extensibility rules are nonetheless extensibile (sometimes we need to >> resort to negotiation of extensions, but that's OK). I suspect that >> the situation w.r.t. XML Schema extensibility is not as dire as you >> paint it. >> > > imho, the real challenge is to *design* a good extension model for a > language; coding it in a schema language then is just an exercise in > figuring out what can be done in that specific language. in XSD, all you > can do is to use wildcards (possibly refined by namespace specifications > for them), and then you have to add documentation saying how processors are > supposed to handle wildcards (ignore, interpret, stop, ...). extension > rules cannot be fully captured (such as saying that extensions are not > allowed to change the semantics of any fields in the base format), but at > least the schema describes the base syntax, and also validates instances > containing extensions. > > i have to admit that i am really curious why the seasoned spec writers > that have voiced general concerns about the usefulness of schema languages > are feeling this way, but so far i have not really understood what they are > saying. could somebody please try again, i'd really like to understand why > the general idea of describing protocol syntax in a semi-formal (as opposed > to non-formal) way is considered a bad idea. > > thanks a lot and kind regards, > > dret. > > -- > erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | > | UC Berkeley - School of Information (ISchool) | > | http://dret.net/netdret http://twitter.com/dret | > > ______________________________**_________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/**listinfo/apps-discuss<https://www.ietf.org/mailman/listinfo/apps-discuss> > -- Website: http://hallambaker.com/
- [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Nico Williams
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Nico Williams
- Re: [apps-discuss] JSON Schema considered harmful James M Snell
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [apps-discuss] JSON Schema considered harmful Nico Williams
- Re: [apps-discuss] JSON Schema considered harmful Erik Wilde
- Re: [apps-discuss] JSON Schema considered harmful Nico Williams
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Erik Wilde
- Re: [apps-discuss] JSON Schema considered harmful Tim Bray
- Re: [apps-discuss] JSON Schema considered harmful Bob Wyman
- Re: [apps-discuss] JSON Schema considered harmful James M Snell
- Re: [apps-discuss] JSON Schema considered harmful evan@status.net
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Julian Reschke
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful Julian Reschke
- Re: [apps-discuss] JSON Schema considered harmful Mark Nottingham
- Re: [apps-discuss] JSON Schema considered harmful Dave Crocker
- Re: [apps-discuss] JSON Schema considered harmful Tim Bray
- Re: [apps-discuss] JSON Schema considered harmful Dave Crocker
- Re: [apps-discuss] JSON Schema considered harmful Phillip Hallam-Baker
- Re: [apps-discuss] JSON Schema considered harmful SM
- Re: [apps-discuss] JSON Schema considered harmful Francis Galiegue
- Re: [apps-discuss] JSON Schema considered harmful Martin J. Dürst
- Re: [apps-discuss] JSON Schema considered harmful Hannes Tschofenig
- Re: [apps-discuss] JSON Schema considered harmful Andrew Newton
- Re: [apps-discuss] JSON Schema considered harmful Dave Crocker