[rfc-i] v3imp #8 Fragment tagging on sourcecode

julian.reschke at gmx.de (Julian Reschke) Sun, 25 January 2015 08:57 UTC

From: "julian.reschke at gmx.de"
Date: Sun, 25 Jan 2015 09:57:21 +0100
Subject: [rfc-i] v3imp #8 Fragment tagging on sourcecode
In-Reply-To: <54C3CF7F.6090901@seantek.com>
References: <54C20F92.4090400@seantek.com> <54C232FC.1000604@gmx.de> <54C275BC.1040905@alum.mit.edu> <20150123175511.GI2350@localhost> <54C28E3F.4040901@alum.mit.edu> <E378C876-5217-4274-86B6-1DBFB653DE24@vpnc.org> <54C29891.6040101@alum.mit.edu> <54C3576A.9030206@greenbytes.de> <54C3BE06.8010707@alum.mit.edu> <54C3C6A3.6080003@seantek.com> <54C3CF7F.6090901@seantek.com>
Message-ID: <54C4AFF1.6030608@gmx.de>

On 2015-01-24 17:59, Sean Leonard wrote:
> On 1/24/2015 8:21 AM, Sean Leonard wrote:
>> First of all there is no such thing as "ABNF modules" yet--only ABNF
>> grammar (combined with specification text). I recognize this
>> conversation is trending to creating them.
>> Providing different definitions of the same rule in the same RFC is
>> reckless
>
> The more I thought about this, the more I would like to propose that the
> RFC itself be unit of analysis (i.e., "module").
> ...


I agree that it's good to formalize this somewhat, but I'm not convinced 
updating/extending RFC 5234 is a good idea.

For instance, in the HTTP specs we use prose rules with a well-defined 
syntax:

<http://greenbytes.de/tech/webdav/rfc7231.html#imported.abnf>

This might be enough for automated checkers to do the right thing.

Best regards, Julian