IETF Logo Mail Archive

Re: [Json] ABNF nits

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 07 June 2013 08:15 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 B797221F9485 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 01:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.79
X-Spam-Level:
X-Spam-Status: No, score=-102.79 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 uJgyWjhrswBz for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 01:15:16 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id DCCA821F9310 for <json@ietf.org>; Fri, 7 Jun 2013 01:15:10 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r578F03g028436; Fri, 7 Jun 2013 17:15:00 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 3a18_da10_59103446_cf4a_11e2_aaec_001e6722eec2; Fri, 07 Jun 2013 17:14:59 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 6A819BF521; Fri, 7 Jun 2013 17:13:52 +0900 (JST)
Message-ID: <51B19672.8040706@it.aoyama.ac.jp>
Date: Fri, 07 Jun 2013 17:14:42 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: stefan@drees.name
References: <255B9BB34FB7D647A506DC292726F6E1151B21F79E@WSMSG3153V.srv.dir.telstra.com> <A723FC6ECC552A4D8C8249D9E07425A70FC326C8@xmb-rcd-x10.cisco.com> <255B9BB34FB7D647A506DC292726F6E1151B21F8CA@WSMSG3153V.srv.dir.telstra.com> <51B17E54.9030107@drees.name>
In-Reply-To: <51B17E54.9030107@drees.name>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] ABNF nits
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: Fri, 07 Jun 2013 08:15:22 -0000

On 2013/06/07 15:31, Stefan Drees wrote:

> If defining a grammar with real case-sensitive "word"-ish tokens in it,
> ABNF is IMO barely usable, unless you extend it with say single quotes
> as case-sensitve string delimiters. But then dealing with two kinds of
> strings also has it's catches =(

Another way to do this is to just note that you are using ABNF *except 
that literals are case-sensitive*. I'm sure there's an RFC or two which 
have done so.

Regards,   Martin.

v2.23.0 | Report a Bug | By Email