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

mellon at fugue.com (Ted Lemon) Fri, 23 January 2015 22:12 UTC

From: "mellon at fugue.com"
Date: Fri, 23 Jan 2015 17:12:47 -0500
Subject: [rfc-i] v3imp #8 Fragment tagging on sourcecode
In-Reply-To: <54C2C021.3060909@alum.mit.edu>
References: <54C20F92.4090400@seantek.com> <54C232FC.1000604@gmx.de> <54C275BC.1040905@alum.mit.edu> <20150123175511.GI2350@localhost> <54C28E3F.4040901@alum.mit.edu> <20150123181608.GJ2350@localhost> <54C294FC.5000204@alum.mit.edu> <20150123190759.GK2350@localhost> <54C2A4AF.6040108@seantek.com> <D8E02C3B-8C62-47D7-8947-B6B679DADD03@fugue.com> <54C2C021.3060909@alum.mit.edu>
Message-ID: <1E471A11-933C-4818-9DAF-D14543415289@fugue.com>

On Jan 23, 2015, at 4:41 PM, Paul Kyzivat <pkyzivat at alum.mit.edu> wrote:
> I think it may be worth discussing how important this would be if there was a straightforward and consistent way to extract the full ABNF. ISTM that this style [presenting the ABNF in fragments and then in full in the appendix] exists primarily because of a lack of that tool.

I think this is probably true.   However, some people may feel that being able to _look_ at the entire ABNF as a unit is important, so I don't think we should assume that, given a proper ABNF extraction tool, this style will suddenly vanish from use.   If we want it to vanish from use, it should probably be something that the IESG and/or the RSE considers and that gets mentioned in a new version of the style guide.

> OTOH, there are times when I just want to look at the syntax, and having it there in one place is nice.

Yup.   Of course, an extraction tool, if it were really easy, would address that need.

> It is a bit of an editorial burden to manually maintain the consistency between the two. But whether that justifies tooling to avoid it is debatable.

I think that it neither does nor does not justify tooling.   It might at some point be used as a justification to add a feature like this to some tool.   The real question is, do we want to support such a tool in the syntax, and if so, to what degree of completeness?

> If you can extract all the fragments as one file, and the appendix as another file, then it is pretty trivial to compare them, without any specific tooling.

Yup.

>> 3. The RFC has ABNF in an appendix, and references the ABNF in the appendix appear throughout the document.   Now you need anchor tags for the references.   I don't think this is actually very usable, though, so I'm not sure we really need to support this mode.   But I agree that we need to support anchor tags.
> 
> This seems largely unworkable.

You mean this style of referencing wouldn't be very usable?   I tend to agree.   I just mentioned it for completeness.   But the anchor tags seem useful, and shouldn't be that hard.