Received-SPF: fail (google.com: domain of abnf-discuss-bounces@ietf.org does not designate 2001:1890:123a::1:1e as permitted sender) client-ip=2001:1890:123a::1:1e;
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from
	:message-id:to:subject:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding; q=dns; s=sasl; b=hFwHwA
	dzahMBvPEOl07CARxWIpDJy8M0Cd9w7Kh7PXSSzbNjpPivdhUn9pzUvqedz+69c5
	eB6Q13nqXNAv/jwVq1TjxWKprQPtyU3PiCZoSHCvD9lULMyAMFHE+XVrlh0oU2Y6
	zatoC4QA67poQ7VyxYbmSXgW3LRItJ10ljQ3A=
Date: Wed, 13 Jun 2012 09:02:51 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
Message-ID: <125452205.20120613090251@pobox.com>
To: ABNF-Discuss <abnf-discuss@ietf.org>
In-Reply-To: <alpine.LSU.2.00.1206131151160.10149@hermes-2.csi.cam.ac.uk>
References: <2CCD27F5-B8D5-4C51-A830-54E6E2676029@lineone.net>
	<4FD79FAD.8040409@alum.mit.edu>
	<alpine.LSU.2.00.1206131151160.10149@hermes-2.csi.cam.ac.uk>
MIME-Version: 1.0
Subject: Re: [abnf-discuss] Unordered lists with specific cardinality
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: abnf-discuss-bounces@ietf.org
Errors-To: abnf-discuss-bounces@ietf.org


On Wed, 2012-06-13, Tony Finch wrote:
> Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> It would be nice to extend ABNF with some syntax to help with this. But no
>> good syntax for this leaps into my mind.

> This would make ABNF no longer straightforwardly translatable into other
> BNF-alikes. I don't think it would be worth it.

Although my parser theory may be a little rusty, isn't this the 
equivalent of forcing a context-sensitive feature into a 
context-free grammar?

-- 
Bill McQuillan <McQuilWP@pobox.com>

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