X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: barryleiba.mailing.lists@gmail.com Received: by 10.58.181.71 with SMTP id du7csp54545vec; Wed, 6 Aug 2014 15:20:09 -0700 (PDT) X-Received: by 10.70.118.9 with SMTP id ki9mr13856228pdb.104.1407363608717; Wed, 06 Aug 2014 15:20:08 -0700 (PDT) Return-Path: Received: from mail.ietf.org (mail.ietf.org. [2001:1900:3001:11::2c]) by mx.google.com with ESMTPS id fl8si930482pdb.409.2014.08.06.15.20.08 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Aug 2014 15:20:08 -0700 (PDT) Received-SPF: pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) client-ip=2001:1900:3001:11::2c; Authentication-Results: mx.google.com; spf=pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) smtp.mail=abnf-discuss-bounces@ietf.org; dkim=pass header.i=@ietf.org; dmarc=fail (p=NONE dis=NONE) header.from=gmail.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDD781B28CA; Wed, 6 Aug 2014 15:20:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1407363607; bh=AIIBY3OSYF9XlqUTxPzhVccpAVenE+aHX1KPtQDpa18=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=j0IakfngbSVnlmC6hjAlCJyebpNZantoYgWtHqKd+K4uClySggIDV4DBynO5p1oU4 Lvy1lr/i5fVg+F3m5HajwwnjuO9Q5OCsKzTbu57zvjmv0yhlYXrV6Fjpm3XuwdLSlY bBMmvU61DAo49QwnhrkDnUz02BbOpigmQsqr7EPI= X-Original-To: abnf-discuss@ietfa.amsl.com Delivered-To: abnf-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005A31A0319 for ; Wed, 6 Aug 2014 15:20:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Vwt9Zrj1jBsU for ; Wed, 6 Aug 2014 15:19:54 -0700 (PDT) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38C191A0336 for ; Wed, 6 Aug 2014 15:19:54 -0700 (PDT) Received: by mail-pd0-f181.google.com with SMTP id g10so4034958pdj.12 for ; Wed, 06 Aug 2014 15:19:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=NtjUisKByzoAe6n3Dd198Kf2EOjkc2HEsL2W6+GrH4k=; b=ODZoqdG2hVNK4b3jS+7+RRTpX6ES0rJ2nI/x3cuMrip8XPCMhWI5G0rVsPN+hF9EBp qjno7P968RGUi4+wEigenKZuNgXSO4cPKJtRXepFBKTcYEq4UtR/z0DPW/CQiP8atj7S JzmOSNBpgBVEbhAA7mIlKPx2Lz+3OnqpdpAzV/o+hr4+3yjmu+Kthl/1BrAHCp8PpDsH /L3XQEqGG6skByYVSpt/oviY/Lurjlk63ZGi3Bbm1m+ZafokiRVVSs+wWvghVsAfc4QW Wj0ObTJWZibF64fJKKfK3KNdlKp535wtgAVwss9pMmGx94PraEDKZRHABTDl55xAfpgZ G3kg== X-Received: by 10.68.219.162 with SMTP id pp2mr13734739pbc.47.1407363593830; Wed, 06 Aug 2014 15:19:53 -0700 (PDT) Received: from [10.251.200.130] ([69.162.16.14]) by mx.google.com with ESMTPSA id gm1sm2311499pbc.40.2014.08.06.15.19.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Aug 2014 15:19:52 -0700 (PDT) Message-ID: <53E2A982.8000405@gmail.com> Date: Wed, 06 Aug 2014 15:17:38 -0700 From: Dave Crocker User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Paul Kyzivat , "abnf-discuss@ietf.org" References: <53E26154.8020308@alum.mit.edu> <53E26391.6060208@gmail.com> <53E27C4B.3050003@alum.mit.edu> In-Reply-To: <53E27C4B.3050003@alum.mit.edu> X-Enigmail-Version: 1.6 Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/1OCCXiCCKO9x0s5iCPiC0IwlWws Subject: Re: [abnf-discuss] Case-sensitive string constants in ABNF? X-BeenThere: abnf-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "General discussion about tools, activities and capabilities involving the ABNF meta-language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: abnf-discuss-bounces@ietf.org Sender: "abnf-discuss" On 8/6/2014 12:04 PM, Paul Kyzivat wrote: > On 8/6/14 1:19 PM, Dave Crocker wrote: >> On 8/6/2014 10:09 AM, Paul Kyzivat wrote: >>> >>> I see no *technical* problem with supporting both kinds. The only >>> questions are: >>> - Is it a good idea to support both? (Or is *not* supporting them >>> intentional, to discourage case-sensitive syntaxes?) >> >> >> As I recall, it's come up more than once. >> >> The issue seems to be that there has not been enough community pressure >> to warrant embedding the construct into the core specification. >> >> Personally, I think it would be a nice example of a useful "extension" >> that might warrant some sort of IANA registry, so that there is an >> established library of ABNF rulesets. > > If you want to go that way, then ISTM there is the need for some sort of > extension framework for ABNF. There would be need for a way for a > particular grammar to declare what extension(s) it depends upon. The simplistic approach is simply a library of rulesets, with no change the the meta-syntax. More ambitious would be an extensible syntax, such as "abc" being case independent and ^"abc" being case dependent. I'm not fond of the idea of pursuing the latter. > It also could lead to fragmentation, where not all tools support the > same extensions. Always an issue, yes. > Maybe its just my age, but for me it remains the go-to tool for modest > grammars. It is very approachable - most people that have reason to > understand a formal syntax can pick up ABNF quickly. (The quoted strings > are the thing that seem most confusing.) I've no idea what you mean. Having 40 years invested in ABNF has created no procrustean momentum with me at all. I'm sure... d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ abnf-discuss mailing list abnf-discuss@ietf.org https://www.ietf.org/mailman/listinfo/abnf-discuss