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

Julian Reschke <julian.reschke@gmx.de> Tue, 27 October 2020 20:03 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 0F34B3A1563; Tue, 27 Oct 2020 13:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level:
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.247, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=gmx.net
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 GeUTSg-fUQ6t; Tue, 27 Oct 2020 13:03:57 -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 6C1843A155F; Tue, 27 Oct 2020 13:03:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 99262F40710; Tue, 27 Oct 2020 13:03:45 -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 8BB02F40710 for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 13:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 0d6UNZI3OycM for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 13:03:40 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by rfc-editor.org (Postfix) with ESMTPS id 05D39F406F7 for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 13:03:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1603829028; bh=ZuC1MtU7aJepEt7/WRPZs8R5zVUEwPFWVkau4KGosF0=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=HXVODN+wuiOw6i7xO9ubVWG4bw68k+bsP7IIESI5vVh95axLu92DpF1O5NwT9fxIo 8DEv1vV7uH3RG0K9cf7J07MytJDNcBdCOuOL3Wc2eJQ5+Y6fablcJMJRzYA5/IpPAK gaXeT0r5CGzyzyfExxmcXNmhY9QU3Fux8PjCib9o=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([91.61.57.60]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MeCtZ-1k0MdP2Vnz-00bL0v for <rfc-interest@rfc-editor.org>; Tue, 27 Oct 2020 21:03:48 +0100
To: rfc-interest@rfc-editor.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> <61675BA6-10C3-4825-ACEF-FA21C38EA186@pfrc.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <58f779b7-5380-8319-a66a-a3fdc779f8c8@gmx.de>
Date: Tue, 27 Oct 2020 21:03:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <61675BA6-10C3-4825-ACEF-FA21C38EA186@pfrc.org>
X-Provags-ID: V03:K1:aqjd9+3N+KDUCsn+yzxAwuFEsy39eFW2X0JXM/U7fhjanA4g24j vkyj+PqcFLVz08uUdJnF/s/7Lg6RuQPccI7i7dvSAusvAx0P69JfVoh143qoQuwPzkCnDMq MoAkVqTJwXliqYhkM8UqKYp77RAZDj2cMIIptYQGorD9LDAV0+9VnYyYuoU2BIzSq5E07Tb pagyHd0AxKXl4ekidKs5w==
X-UI-Out-Filterresults: notjunk:1;V03:K0:xWKzwgnmWJc=:/YBW2kBLvyZ6hmdF8Rqgzg gjR5KuppTXaU6HLBEODXBRkhEjoiE0xawrtmawLgqrJlOo+s0Kt5ZCbfLfimHA0QN2EUhidYB lssRQsgr21yv8thzuPaM5UqllRIciWOg1FgpJzAOKMhOqqj3XTfAfvmcpT9xqthKdWvJuRvEm A2RgN3D7MTx0T3j2U/5aN43L44DoIaoGeLChowTSANmys9U5xjKBrJstx8yB9Qw0bs6Xp4TN3 pxX4h+suvRF5sn2Ue74aiaqDnm4/MyXaG+Nuit/TKKjPA8nLcHD7sqjPjDKSrNKRhwsW5kFXx GUiKYe5HuTr+ek9Zawr6rlzOLLW9DGVmSXSH5dn9hRoUAgsua9yr41tm8fM2mUpoCvaAcd0XX JWnitNSPJZ1W5kj1ZfM2gHk1W7FSQDG8UAELtCl2X4/Y9srHgeIctcl2rL7PRYk4BHEIrjWnD l5+iTLZ6jU6Zf5mnuF6wrpkp/D/NdId9z65/ZqDXkGWo+nrzY8YScbrCTiXSITfhsuLXvoT/U gFOu+VrQB5EKtgQA1PMCVwBOGt6+IeuR6fRBAf8LIJASYolmfPy0I8ZU9e/N2cVHlJxF/1AjS AxlcYXIvKbIpwGeKSQevt2MlE5XzjkQdzNSCJnjH3SbTueHxyeVZvuk7vdN9yXxMvHeAT6yHH dj2Jp5y7rHOQTthmgvlUawmeU8DlFjmTL9alENJmMTFNXGKyWgvndrkyKBAZMHNGXmObQ5NJ0 NfH7O9QkDQuWHjuwtqG2Jva+vyfNt0Z4bdM/X30JfBIAHFGKN112N7A2ZjqvofXHBNIaI3kqy o9qlJG3IqC8EhEzRAmoNEwPPNhmo5o0OqpowKseEIG2ePPjC3WW+p48RHlOqRku41exRIip+G pTmOIwqfkpl+9y81XuQA==
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>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Am 27.10.2020 um 20:42 schrieb Jeffrey Haas:
> 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?
> ...

All anchors in HTML are supposed to be discoverable, either by clicking
on titles, section numbers, or paragraph symbols that show up after the
last characters of a paragraph.

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

Not sure how XML source code indentation is relevant. That said, the
"canonical" XML is supposed to be the output of a pretty printing step.
See <https://greenbytes.de/tech/webdav/rfc7998.html#pretty>.

Best regards, Julian

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest