Re: [Json] Do not use ABNF for JSON schemas!

Tim Bray <tbray@textuality.com> Sat, 15 March 2014 18:10 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1881A0186 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 11:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 atwQkNlZ5qMA for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 11:10:57 -0700 (PDT)
Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4F21A017D for <json@ietf.org>; Sat, 15 Mar 2014 11:10:57 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id jz11so4004755veb.25 for <json@ietf.org>; Sat, 15 Mar 2014 11:10:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DoumYGEJ6l5hkDCnJtf9KSOHHmGdzIRpKA4+ZT41itc=; b=TqDb1vKVNrtZO0Tbdh1cQgLa0L10sgOfMEJTK0k7rvB6PraCGg8mAvP0G4gXc3C4UX arzfg14y0t7ER4cZQLJ0N7ko75FsBqfmp3rj0/xioD4cgh5XtqMozJXcU2YIlwGFpw2E ltumKHOTkMmj6KEf6MrwvFAUV6RveHdB0n9d8Q5+XMJsxQgZ2UP5MqsUdemP35m3Un5n Gms30M0W+m8bVjAaPxlDjAR8luCTUTx4YYmMuKwjvOT6+et+t8rtSCWp66MZl0zstHbL 28J0RA+Qmn+e9GfvgSHEz88IM9N13xodXNUGfrmfA4+LYFgU4HfLPALUguViDUXoNdxW 4m5A==
X-Gm-Message-State: ALoCoQlLluVCFLQ/iVwQWD4OtzOJkfL8x+x25QQd68qFZtcQnPl4rBoEmqpzHkRPs3qEelQGyD94
MIME-Version: 1.0
X-Received: by 10.52.113.1 with SMTP id iu1mr105806vdb.35.1394907049589; Sat, 15 Mar 2014 11:10:49 -0700 (PDT)
Received: by 10.220.98.73 with HTTP; Sat, 15 Mar 2014 11:10:49 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <619B38E7-B8FD-4640-97A8-B523AF655B9E@tzi.org>
References: <53238F2E.5010105@cisco.com> <CAHBU6itv0q7ZTrran+dKTcUxoSxNHYnND7yLmSPF35--iUMA+w@mail.gmail.com> <CAMm+Lwi6Ha0r55vb3VNsgz40Bds6HYZ-aM9u-JwyVmoRDuZaWw@mail.gmail.com> <420F0699-9F27-435E-924C-28966A743EAF@vpnc.org> <CAHBU6iv=pUmq1Jdi+VkFnEG0+Ef7pBnSMtPdVNaHFxu6x5RFBQ@mail.gmail.com> <D93BF076-90B2-4AF0-BDD6-29BF4332AABF@vpnc.org> <CAK3OfOhqfJWX747jZs40amrdRV5T3aTxrMHsCvW-5jdN9zq40w@mail.gmail.com> <C77851F1-FBB2-47AD-B263-565593899D8C@vpnc.org> <890D8059-2280-48D5-820B-2E75852AF334@vpnc.org> <619B38E7-B8FD-4640-97A8-B523AF655B9E@tzi.org>
Date: Sat, 15 Mar 2014 11:10:49 -0700
Message-ID: <CAHBU6ivPg=rW9715TiL6zLZqXx+-RrnETe-aEk6v42vfOBPccw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="bcaec547c6232f915404f4a91b5b"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/jjcSIeIoratzYHT4yrTkM02d9cQ
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Do not use ABNF for JSON schemas!
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 15 Mar 2014 18:10:59 -0000

+1


On Sat, Mar 15, 2014 at 10:03 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On 15 Mar 2014, at 17:50, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>
> > Here's a JSON format that could definitely use a simple JSON description
> language of some sort. The draft authors went the ABNF route, and it's
> completely unclear where they are going until you look at the examples and
> realize how trivial the format really is.
>
> One extremely useful result this WG could have is eliciting an IESG
> statement that ABNF representations of JSON schemas are verboten.
>
> Grüße, Carsten
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>