IETF Logo Mail Archive

Re: [rfc-i] [Tools-discuss] what metric replaces page-count?

John R Levine <johnl@taugh.com> Tue, 13 April 2021 01:54 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 02C033A0ADD; Mon, 12 Apr 2021 18:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.751
X-Spam-Level:
X-Spam-Status: No, score=-4.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=YXLTPUPZ; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=QuiA33t5
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 yopkYmgDd46f; Mon, 12 Apr 2021 18:54:13 -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 E36123A0ADB; Mon, 12 Apr 2021 18:54:12 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 196D2F407C5; Mon, 12 Apr 2021 18:53:59 -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 ED2C3F407C5 for <rfc-interest@rfc-editor.org>; Mon, 12 Apr 2021 18:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=YXLTPUPZ; dkim=pass (2048-bit key) header.d=taugh.com header.b=QuiA33t5
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 3GL-Unm4bP3F for <rfc-interest@rfc-editor.org>; Mon, 12 Apr 2021 18:53:53 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) by rfc-editor.org (Postfix) with ESMTPS id 533E2F407A4 for <rfc-interest@rfc-editor.org>; Mon, 12 Apr 2021 18:53:53 -0700 (PDT)
Received: (qmail 9605 invoked from network); 13 Apr 2021 01:54:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type; s=2580.6074f9bb.k2104; bh=+CN9FIiHmHDqkMfe8BOLZUgF84smsEV3yY7Ju3kgpLQ=; b=YXLTPUPZG1IwIxtxKYf6w+hjO2M6wbm7S+nblpH646YI14qqBAkZ8rrPIQdRje1zFkOrGltVjD+TFxG4UVf6KXMzCbrH9rUBE082COId5UvxlH8hsTgQnf24W/ujZjJAmHD5KePZ4D5U8YphHi6nWSKUQAzjZ5dWymbBSfJG77TIgQCm/ji/53wvB9SYROHar7n0KeWCMXe91UCjxumsVMAehEt6BdrqGjHPCF1BsTXCseKNM65PnP5aIVvFeDh+hOeybWnsCiiyFyOdIEWT9Tmg9L9o/sqerrE6cUDe/m+OrYgjAgUtKh9jy1Ks2n+K9sP11uYOYN18khMIbPiQoA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type; s=2580.6074f9bb.k2104; bh=+CN9FIiHmHDqkMfe8BOLZUgF84smsEV3yY7Ju3kgpLQ=; b=QuiA33t5guWQP8Wa9ufD0SZ1c4l6BEh++lAsjT29jmh6f0llU5sYC5SDI1/veSAaz696GWJAF84vbkvB+Hqo7e7vpZvcQOu6ZI6iWQbjzqdTFRpPTlNxKZ8p6pYIKWymHXTaDSdxY1UduTLC9CmhgVc6rJBjuc1oW4FlxgyGrKB3eheGaY1XwAEtWc7GtnLxVfv2WrhxJIV8LLW4liyMMbWZJmjThnofiGzIebgeATbPK88BlEfTxIV39+Gu9HgRiATzHeUEgBIbEI1QHKP6r2gx4O6w+p/sGhKqlzW3/IYmx0vA//edIRhILMrS7Ta6k10ta7XX1kIorZRj14D1Hg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 13 Apr 2021 01:54:03 -0000
Received: by ary.qy (Postfix, from userid 501) id E6D0272C483D; Mon, 12 Apr 2021 21:54:02 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id E620D72C483C for <rfc-interest@rfc-editor.org>; Mon, 12 Apr 2021 21:54:02 -0400 (EDT)
Date: Mon, 12 Apr 2021 21:54:02 -0400
Message-ID: <87f7996c-36ea-370-c20-a45049cfeebd@taugh.com>
From: John R Levine <johnl@taugh.com>
To: rfc-interest@rfc-editor.org
X-X-Sender: johnl@ary.qy
MIME-Version: 1.0
Subject: Re: [rfc-i] [Tools-discuss] what metric replaces page-count?
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: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

> I have never testified in court, but would they really use an XML source
> there?

When I'm putting together a declaration, I can use whatever I want so long as I 
provide it to the other party's lawyers.

The appearance of our HTML rendered RFCs is set by the stylesheet which is easy 
to override, so I could tweak the stylesheet to show the paragraph numbers and 
print that.

Alternatively, the PDF rendering is paginated and that's what we provide in 
response to legal document requests.  They have the XML file as an attachment 
if people want to look at or render the XML themselves.

R's,
John

>> On Apr 12, 2021, at 17:37, John Levine <johnl@taugh.com> wrote:
>> 
>> It appears that Ole Jacobsen  <olejacobsen@me.com> said:
>>> 
>>> And sections NEVER span more than a single page, do they now?
>>> 
>>> That would be "inaccurate" I guess.
>> 
>> If you look at an RFC's XML, every paragraph has a number. Hover over
>> the paragraph mark at the end of the paragraph in the HTML rendering
>> and you'll see the URL for that paragraph, including a fragment
>> identifier for the paragraph.

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

v2.23.0 | Report a Bug | By Email