IETF Logo Mail Archive

Re: [Json] Update reference for ABNF

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 06 June 2013 16:54 UTC

Return-Path: <paul.hoffman@vpnc.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 37CEB21F9A31 for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 09:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.008
X-Spam-Level:
X-Spam-Status: No, score=-102.008 tagged_above=-999 required=5 tests=[AWL=0.591, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pQJVWGJjJcpX for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 09:54:30 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C99821F9A2E for <json@ietf.org>; Thu, 6 Jun 2013 09:54:17 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r56GsAsI032745 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jun 2013 09:54:11 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <C8675622-C77B-4595-B8E7-3E2063094116@tzi.org>
Date: Thu, 06 Jun 2013 09:54:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <67FC4D12-AE76-45AC-A9B1-18FA33D030B4@vpnc.org>
References: <51AF9D4C.5060403@crockford.com> <60563185-85A8-4696-8B8C-9282256CFA71@vpnc.org> <255B9BB34FB7D647A506DC292726F6E1151B10582A@WSMSG3153V.srv.dir.telstra.com> <19943667-1EC6-427F-9122-EC037BDE47F1@vpnc.org> <51AFEC73.1030904@crockford.com> <2484862A-4DFF-44D7-9D9D-7E44520C5BED@vpnc.org> <51B06A44.1070008@crockford.com> <2E0B8DF9-BF9F-485E-B011-D9864C4DB875@vpnc.org> <C8675622-C77B-4595-B8E7-3E2063094116@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1508)
Cc: json@ietf.org
Subject: Re: [Json] Update reference for ABNF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 16:54:41 -0000

On Jun 6, 2013, at 9:46 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On Jun 6, 2013, at 17:32, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> 
>> Will one or more of you who care about good ABNF volunteer to do careful checks against RFC 5234?
> 
> Well, so far I only checked that 5234 is not worse for 4627bis than 4234.
> But I can also volunteer to torture-test the ABNF itself.

Thank you, we have a volunteer! Who will be the second? That's a serious question: some WGs have passed non-ABNF-compliant documents due to having too few checkers. Fortunately, there is little ABNF in this document, so that should cause others to want to gain this new and valuable skill.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email