Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 02 November 2020 12:20 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 0388E3A0E75; Mon, 2 Nov 2020 04:20:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, 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=joelhalpern.com
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 GaML5zw6P8LO; Mon, 2 Nov 2020 04:20:00 -0800 (PST)
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 C23813A0EAD; Mon, 2 Nov 2020 04:19:35 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CE03BF406F5; Mon, 2 Nov 2020 04:19:17 -0800 (PST)
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 40F45F406F5 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 04:19:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 Dx9mWA__nMHi for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 04:19:11 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by rfc-editor.org (Postfix) with ESMTPS id DFB8DF406D8 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 04:19:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4CPsRP59K5z1nvlM; Mon, 2 Nov 2020 04:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1604319569; bh=bpzN1uU3whoJi7c2NyxPbSKRNU2XdgGa5VbutK/MB3w=; h=Subject:To:References:From:Date:In-Reply-To:From; b=BrPr9+urhHE4UiHw4VUcUIaKgeuSjlCGM6xER8984rFF4TYXpV82cJU/el6NoIFfN kTHrTZ6vIZ6Rrc+Ge5vrTXS/Q6jNBCumnuJMWRF2lbq1HlUDQBAGllXViG2mkcJ5RY kFEX6Kd1lL5wiQwSaoZ+lySV1H4SOrKVKHrC0dsQ=
X-Quarantine-ID: <tMM2F9-ZBt4L>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4CPsRP0Jm9z1nt7Q; Mon, 2 Nov 2020 04:19:28 -0800 (PST)
To: tom petch <daedulus@btconnect.com>, rfc-interest@rfc-editor.org
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <CADaq8jdSeTDWy_0fCV25ykxKFMV1ZBtUMMNesoOuaXCzFVfpOA@mail.gmail.com> <D2D0455D-8D6C-4A19-ACAE-4DD972D83DC1@bluepopcorn.net> <20201028164053.GB12700@faui48f.informatik.uni-erlangen.de> <263C265C19B24BA97AF48934@PSB> <225062D7-C061-4543-8665-53A4F4831510@isc.org> <20201029005519.GT39170@kduck.mit.edu> <A05242FC-C38C-474F-A2AC-412329CA5C52@isc.org> <CAKq15ve-kAFZWH_f7=1XXC5PfxvO-sAzppB1fVTyqUufLftkVg@mail.gmail.com> <D2DB703DBF2A44A19B8F80DD@PSB> <CAKq15vdFVkG6_grNtqUqq-yDwj9QQcHJFZB5+RB-8fdxQXhFSw@mail.gmail.com> <fa36e919-b1a0-5b3c-9b42-54c6fdaadfb@iecc.com> <e8554ea2-1849-279f-733d-5798de8817b9@gmail.com> <26d1ff54-777f-884b-e35-d91e9fe59662@iecc.com> <00a1fc15-7559-96c6-7cd7-3ae5afd62237@gmail.com> <a34f219b-7c76-4b48-4844-5af3cd4f344@iecc.com> <be8dce95-2b4c-52c8-7eda-8a9b127a6dd4@gmail.com> <cdc14c1-54c9-5273-584c-ddb656912952@iecc.com> <5F9FDB7E.1080805@btconnect.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <6e23df24-4ac2-5021-b9c9-584ae3307f30@joelhalpern.com>
Date: Mon, 02 Nov 2020 07:19:28 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <5F9FDB7E.1080805@btconnect.com>
Content-Language: en-US
Subject: Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?
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>

And this Tom is exactly why many of us flinch at the generally 
reasonable request that people be able to get page numbers of printed 
documents and the on line form from which it was printed.

If you refer to page numbers in a comment, then folks looking in some 
other form factor will have no way of using that reference.  For YANG 
modules, my experience is that one is much better to use other reference 
indicators (e.g the grouping name, ...).

Yours,
Joel

On 11/2/2020 5:12 AM, tom petch wrote:
> On 01/11/2020 14:59, John R. Levine wrote:
>>>> What formats do you believe don't have section numbers?  They're in all
>>>> three rendered formats and in the XML as tags like "section-3.1".
>>>
>>> They aren't in raw XML and they aren't in kramdown, so they aren't where
>>> an author needs them when processing comments on an I-D. (So, strictly,
>>> that isn't an RFC format issue, but it is an issue created by our format
>>> choices and it's quite an annoyance.)
>>
>> Sounds like yet another thing that could be improved with better
>> tooling. Adding and updating comments with section numbers isn't exactly
>> rocket science.
> 
> YANG modules do not have section numbers and can be 50 (five zero) pages 
> long and the same identifier (e.g. 'status') can appear multiple times 
> in different branches of the schema tree and the tree can be over 10 
> levels deep so providing the absolute form of the identifier of the leaf 
> that you are commenting on can take more than one line.  Reference by 
> page number is so simple (even ADs use it:-).
> 
> Tom Petch
> 
>>
>> Regards,
>> John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for
>> Dummies",
>> Please consider the environment before reading this e-mail. https://jl.ly
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>> .
>>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest