X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with SMTP id bt9csp184473ved;
        Thu, 3 Jan 2013 09:03:32 -0800 (PST)
X-Received: by 10.68.197.8 with SMTP id iq8mr154540788pbc.56.1357232611606;
        Thu, 03 Jan 2013 09:03:31 -0800 (PST)
Return-Path: <abnf-discuss-bounces@ietf.org>
Received: from mail.ietf.org (mail.ietf.org. [2001:1890:126c::1:1e])
        by mx.google.com with ESMTP id zs6si47970754pbc.301.2013.01.03.09.03.30;
        Thu, 03 Jan 2013 09:03:31 -0800 (PST)
Received-SPF: pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1890:126c::1:1e as permitted sender) client-ip=2001:1890:126c::1:1e;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1890:126c::1:1e as permitted sender) smtp.mail=abnf-discuss-bounces@ietf.org; dkim=pass (test mode) header.i=@ietf.org
Received: from ietfa.amsl.com (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id B99E021F8CF4;
	Thu,  3 Jan 2013 09:03:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1357232610; bh=K/Ylv1hi15UOdGtNFD3kNTVSdvLdI6h5Mw+a7yaWzI8=;
	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=nuxnavgtwOv9H3h1x4vsIm3dYbqai3bjS/tKXKCQtHJQyE1uAlPE13mbWfV3bp+WE
	 wJwhV3pQ/LB5AuMv6Dm4BP/8hu7ikZgiKhotlxdAs6jTiXd+3m+TsAaq6MHGRHPM6i
	 EMf7WseS3asoDlCaZbnZmk1Oj7oNO3KqQszoqysY=
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 26C4321F8CF3
	for <abnf-discuss@ietfa.amsl.com>; Thu,  3 Jan 2013 09:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.162
X-Spam-Level: **
X-Spam-Status: No, score=2.162 tagged_above=-999 required=5
	tests=[FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30])
	by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jFmccTQSL-S3 for <abnf-discuss@ietfa.amsl.com>;
	Thu,  3 Jan 2013 09:03:28 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net
	(qmta01.westchester.pa.mail.comcast.net
	[IPv6:2001:558:fe14:43:76:96:62:16])
	by ietfa.amsl.com (Postfix) with ESMTP id 6BD0C21F8CF2
	for <abnf-discuss@ietf.org>; Thu,  3 Jan 2013 09:03:25 -0800 (PST)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52])
	by qmta01.westchester.pa.mail.comcast.net with comcast
	id jRGN1k00617dt5G51V3QrJ; Thu, 03 Jan 2013 17:03:24 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164])
	by omta13.westchester.pa.mail.comcast.net with comcast
	id jV3Q1k00q3ZTu2S3ZV3QZl; Thu, 03 Jan 2013 17:03:24 +0000
Message-ID: <50E5B9DB.4030500@alum.mit.edu>
Date: Thu, 03 Jan 2013 12:03:23 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: abnf-discuss@ietf.org
References: <50E4A900.1070408@alum.mit.edu>
	<alpine.LSU.2.00.1301030943590.15409@hermes-1.csi.cam.ac.uk>
	<50E5B175.1030308@gmail.com>
In-Reply-To: <50E5B175.1030308@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
	s=q20121106; t=1357232604;
	bh=pjjzioAVTArw9rT3shqRJQ6gOV+XOZJp/AuncfHePr0=;
	h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject:
	Content-Type;
	b=QUkZWYF1+sUvUJBYF5yK8lz+0kfGLluQu3Hocjkby/fS/IxKYLodvICAuUvKUXyuI
	3gYorOVVUSqqFNw1woJ2H4np9Pz/wUKC2BzJ14r4VBDQCN8gcZAly2MBnli7qCAWpj
	N9Bec5zlEkl9OvOy9jWfElW56ey8zG5fde9MyVTWnmeTE+hcBN2uNInkWkFPhNQ4ly
	QwsO3tQqsRzXPpaYOIcIU1gcXtQ3ZyKel3ejgiSy1SQUZwYkHgi2NLWmQYd8aHhSPm
	Ci3298lUy7TD5xCIXNCvJ8nadcwSuteMf4UGhH4DIrdbRsQKwzrJPIibRvAke61YIz
	RyZElf56cp3Lw==
Subject: Re: [abnf-discuss] How to indent ABNF figures in draft?
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "General discussion about tools,
	activities and capabilities involving the ABNF meta-language"
	<abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>,
	<mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/abnf-discuss>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>,
	<mailto:abnf-discuss-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: abnf-discuss-bounces@ietf.org
Errors-To: abnf-discuss-bounces@ietf.org

On 1/3/13 11:27 AM, Dave Crocker wrote:
>
>
> On 1/3/2013 2:09 AM, Tony Finch wrote:
>> I suggest the following, which still requires rules to start on new lines
>> but removes sensitivity to horizontal white space.
>>
>>           rulelist       =  1*( *c-wsp rule ) *c-wsp
>>
>>           rule           =  rulename defined-as elements c-nl
>>
>>           c-wsp          =  WSP / c-nl
>
>
> If intent is to require indentation for a rule that wraps around to an
> additional line, I think you mean:
>
>              c-wsp          =  WSP / (c-nl WSP)
>
> (I'm completely ignoring the issue of starting a new rule indented.  We
> seem to be handling that adequately, already...)

I'm not sure what you mean by "handling that adequately"?

If you mean "we have some tools that handle indented ABNF", then maybe.

If you mean "RFC5234 unambiguously specifies how ABNF may be indented" 
then I disagree. We have an ABNF for ABNF that says there may be no 
whitespace at the beginning of a rule. And then there is some text, that 
may or may not be normative, that informally describes how ABNF may be 
indented.

And even if that text is considered normative, it isn't entirely clear 
what is and isn't valid. I *think* it says that the beginning of all 
rules must be indented the same amount, and continuation lines must be 
indented more. So that the file could be preprocessed by finding the 
first non-whitespace line, removing leading whitespace from that line, 
and then removing identical leading whitespace from all subsequent 
lines. Then process the result according to the ABNF for ABNF.

But that becomes messy when both tabs and spaces are used. In doing 
leading whitespace removal, what if some lines start with spaces and 
some start with a tab? E.g. what if I have:

<sp><sp><sp><sp>foo-stmt = "foo:" bar
<tab>"," baz

Is that valid? Should the <tab> be removed from the 2nd line? If so, 
does that mean the line starts without whitespace and so isn't part of 
the rule from the first line? Or should the <tab> be considered 
equivalent to some number of spaces? If it is considered equivalent to 8 
spaces, then the 2nd line is a continuation. If it is considered 
equivalent to four spaces then the 2nd line isn't a continuation.

IMO this isn't "adequate". :-)

	Thanks,
	Paul
_______________________________________________
abnf-discuss mailing list
abnf-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/abnf-discuss

