X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: barryleiba.mailing.lists@gmail.com Received: by 10.58.181.71 with SMTP id du7csp38857vec; Thu, 7 Aug 2014 09:38:16 -0700 (PDT) X-Received: by 10.70.61.67 with SMTP id n3mr9207543pdr.90.1407429496396; Thu, 07 Aug 2014 09:38:16 -0700 (PDT) Return-Path: Received: from mail.ietf.org (mail.ietf.org. [4.31.198.44]) by mx.google.com with ESMTPS id rs10si3899068pab.188.2014.08.07.09.38.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Aug 2014 09:38:16 -0700 (PDT) Received-SPF: pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 4.31.198.44 as permitted sender) client-ip=4.31.198.44; Authentication-Results: mx.google.com; spf=pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 4.31.198.44 as permitted sender) smtp.mail=abnf-discuss-bounces@ietf.org; dkim=pass header.i=@ietf.org Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 628621B2E46; Thu, 7 Aug 2014 09:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1407429495; bh=YnDieaMCJmowRFjqFwkTsXNcOhsq2qCi36fqEswK9t0=; 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-Transfer-Encoding:Content-Type:Sender; b=BdoKB1Q7tgYWIbAESBRD4vfGjTqTj0X95gbNJUv+s3hXheWPFQe2ezhK0dKEcFAcw +3IWCLUo5czKT+GJdzmcjrl0R7UPzmPJPNlTz2kcTIH35eSx/LkdN7F3knskTmEuOj tY3CgyD+9gr8kkSm9CspXUOxI/26/HWTXSE8R+dM= 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 673051B2E46 for ; Thu, 7 Aug 2014 09:38:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.235 X-Spam-Level: X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no 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 6WpFB7GdWyCn for ; Thu, 7 Aug 2014 09:38:12 -0700 (PDT) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id E02D51B2DDE for ; Thu, 7 Aug 2014 09:38:07 -0700 (PDT) Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta07.westchester.pa.mail.comcast.net with comcast id bqhu1o0070mv7h057se7wC; Thu, 07 Aug 2014 16:38:07 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta11.westchester.pa.mail.comcast.net with comcast id bse71o0093ZTu2S3Xse7MN; Thu, 07 Aug 2014 16:38:07 +0000 Message-ID: <53E3AB6F.9080606@alum.mit.edu> Date: Thu, 07 Aug 2014 12:38:07 -0400 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: abnf-discuss@ietf.org References: <53E26154.8020308@alum.mit.edu> <01PB24L5SC060000SM@mauve.mrochek.com> <53E27A1A.10609@alum.mit.edu> In-Reply-To: <53E27A1A.10609@alum.mit.edu> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1407429487; bh=Govae0fs5AeSk8NT5JIBRwML12cNOm+R0A3vf6ugt5E=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=sptYEOtagjfH76WAUU+JM0wrDt/zu/eF21E3gGaJcPK8PqE5lr04YDUjGzrFzILVV uBc9Um90Ulv7iwZPuqL+zOvgzRzTMhwSFJChSQxbYkEBSeRBh4KeGNpeJ+EJvUeCFM eRZw/8ycYLKtRAE+/JniCE54uYeRFq4t7G81n+aee6Z2rM3foFlBMfqqhJtZgjiUCu Z6CELyjoR7+oxvuSqB3ktO6iW86bRPwMHJc32MwXtB3HGyjqOK2AME+KfNxgSrz/3H xu2kGVWqQR5GgIbILNbxKw5KAPOWu5a9HOyDmN6RYNctVCL+nisycVGucj9To5wGOs M43amrpKh0ZyQ== Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/b0iNbIPHtcaISqUsM-5KM54LQVs 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: abnf-discuss-bounces@ietf.org Sender: "abnf-discuss" On 8/6/14 2:55 PM, Paul Kyzivat wrote: > But it isn't obvious what type indicator characters to use to denote > case sensitivity and the converse. The %S and %I were the first things > that came to mind, but I don't love them. > > It also occurred to me that there might be other string modifiers that > people might want. E.g., unicode. Once you get to unicode it might not > make sense to talk about case-insensitive comparison. Thinking more about this... Right now the ABNF strings are limited to ASCII. And that makes sense for case-insensitive matching, because when you go beyond ASCII the meaning of case-insensitivity gets complicated. Perhaps case-insensitive strings should allow more of UTF8. (Perhaps only the graphic parts.) Is there a reason not to allow that? Concerns that come to mind: - it might just be too messy to define what to allow, or not - if UTF8, then do we also need UTF16, ...? - introduces an increased possibility that people looking at the ABNF might not know what character they are looking at. Thanks, Paul _______________________________________________ abnf-discuss mailing list abnf-discuss@ietf.org https://www.ietf.org/mailman/listinfo/abnf-discuss