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

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

Return-Path: <kaduk@mit.edu>
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 EC13A3A15C5; Tue, 27 Oct 2020 12:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 aGVmmh3f07mz; Tue, 27 Oct 2020 12:32:54 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44C913A157E; Tue, 27 Oct 2020 12:32:53 -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 09RJWepV027898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 27 Oct 2020 15:32:45 -0400
Date: Tue, 27 Oct 2020 12:32:40 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Jeffrey Haas <jhaas@pfrc.org>
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>
Subject: Re: [irsg] Resending: Page numbers in RFCs questions / preferences
Message-ID: <20201027193240.GS39170@kduck.mit.edu>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20201027193808.GF23518@pfrc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/0oPAdsXNzr5daUMktxnlZdQgc78>
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:33:03 -0000

Hi Jeff,

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).  So, if I assume that you knew that, I'm left with the
conclusion that the "paragraph" part of the reference/link needs to be more
prominent to someone that does not understand the URL fragment's structure.
Which is perhaps a valid position to hold, but I'm not entirely confident
if that is the position you are holding.

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

-Ben

> I'd simply note that XPath provides sufficient addressability.  But it's
> less easy to interact with it in plain text emails and still awkward in
> richer formats.
> 
> /section[@title='Security Considerations']/t[5]  as an example of the fifth
> text block of the security considerations section.
> 
> 
> -- Jeff