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

Benjamin Kaduk <kaduk@mit.edu> Tue, 27 October 2020 19:50 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 847AB3A15B3; Tue, 27 Oct 2020 12:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ae5Rlec6dNqF; Tue, 27 Oct 2020 12:50:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74F143A15F5; Tue, 27 Oct 2020 12:49:59 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8AE7DF4070C; Tue, 27 Oct 2020 12:49:47 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 2961FF40709 for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 12:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjGMvzmaxDU8 for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 12:49:42 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by rfc-editor.org (Postfix) with ESMTPS id 3757CF4070C for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 12:49:41 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 09RJndac002636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 27 Oct 2020 15:49:44 -0400
Date: Tue, 27 Oct 2020 12:49:39 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Jeffrey Haas <jhaas@pfrc.org>
Message-ID: <20201027194939.GU39170@kduck.mit.edu>
References: <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> <61675BA6-10C3-4825-ACEF-FA21C38EA186@pfrc.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <61675BA6-10C3-4825-ACEF-FA21C38EA186@pfrc.org>
Subject: Re: [rfc-i] [irsg] Resending: Page numbers in RFCs questions / preferences
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>, Toerless Eckert <tte@cs.fau.de>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On Tue, Oct 27, 2020 at 03:42:52PM -0400, Jeffrey Haas wrote:
> 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.

Ah, happy to help.

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

I don't remember a specific guide; I think I have just picked up on some
things by exploring and clicking on random stuff.  (Well, and perhaps
spending way too much time on the datatracker.)  But it's possible that one
of Heather's plenary talks had a summary of new and exciting features and
I've just forgotten about it.

> >> 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.

I suspect you are correct.

Thanks,

Ben
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest