Re: [irsg] Resending: Page numbers in RFCs questions / preferences

Jeffrey Haas <jhaas@pfrc.org> Tue, 27 October 2020 19:42 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BAA3A0EA7 for <wgchairs@ietfa.amsl.com>; Tue, 27 Oct 2020 12:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 vFsbjbaIrnRI for <wgchairs@ietfa.amsl.com>; Tue, 27 Oct 2020 12:42:53 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2083A0EA2 for <wgchairs@ietf.org>; Tue, 27 Oct 2020 12:42:53 -0700 (PDT)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id D38241E353; Tue, 27 Oct 2020 15:58:01 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: [irsg] Resending: Page numbers in RFCs questions / preferences
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <20201027193240.GS39170@kduck.mit.edu>
Date: Tue, 27 Oct 2020 15:42:52 -0400
Cc: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, WG Chairs <wgchairs@ietf.org>, Toerless Eckert <tte@cs.fau.de>, RFC Interest <rfc-interest@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <61675BA6-10C3-4825-ACEF-FA21C38EA186@pfrc.org>
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.com> <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org> <CADaq8je85zUHcCOMW6wCy+fiYUPfVE-1sjy3_Xhsxg85ACOkpQ@mail.gmail.com> <A062DE7F-4D21-4731-B59C-89232EACAF5C@tzi.org> <CAHw9_iJQ93M=Mkxd5H0QxgRUcwCTwVmkwFXjgBrKTnpcksx08g@mail.gmail.com> <66D76329-D7FB-4F44-897D-73E7E8B43771@cisco.com> <20201026214815.GE23518@pfrc.org> <20201026215117.GY39170@kduck.mit.edu> <20201027193808.GF23518@pfrc.org> <20201027193240.GS39170@kduck.mit.edu>
To: Benjamin Kaduk <kaduk@MIT.EDU>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/nmX3gt1gWngK-vPg7oJMGSDscfc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 19:42:56 -0000

Ben,


> On Oct 27, 2020, at 3:32 PM, Benjamin Kaduk <kaduk@MIT.EDU> wrote:
> 
> On Tue, Oct 27, 2020 at 03:38:08PM -0400, Jeffrey Haas wrote:
>> Ben,
>> 
>> On Mon, Oct 26, 2020 at 02:51:17PM -0700, Benjamin Kaduk wrote:
>>>> The input XML already provides blocks.  It should be fairly reasonable for
>>>> the tool to provide you something like "this is section X.Y, ¶5".
>>> 
>>> Like https://www.rfc-editor.org/rfc/rfc8815.html#section-3.1-5 ?
>> 
>> You seem to have missed the paragraph 5 symbol I added.
>> 
>> I regularly use the html anchor notation above. :-)
> 
> I am not sure which of us is confused -- the link I provided is directly to
> the fifth paragraph of the section (the "-5" suffix effectuates that
> functionality).  

No, I missed the distinction of the -5 vs. .5.  If so, certainly my primary use cases for such citations are covered.

Is there a guide that has any other such things I may have missed?

>> If it wasn't for the fact that our XML is of highly variable quality
> 
> Indeed.  And there does not seem to be much appetite for fixing that -- I
> had asked about even something as simple as consistent indentation for
> nested XML elements and got a response along the lines of "if authors care,
> they can put in the work to make the XML look pretty".  Which is
> unsatisfying to me, but I apparently failed to make a persuasive case for
> it.

This is a battle I'd have no stomach for.  Much like code indentation, it's a fight that only generates sore losers.  And much like code indentation, if you care - run it through your favorite indenter.  

That said, a tool that can generate such citations might still be of use if we continue further down this hole.  But I think if we have the ability to generate paragraph and section citations, we're probably covering the majority of the common use cases.

-- Jeff