Re: [rfc-i] contributors section & tools

Adrian Farrel <adrian@olddog.co.uk> Wed, 15 July 2020 18:24 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 BECB03A0AEC; Wed, 15 Jul 2020 11:24:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 GGlt1yCgYeRa; Wed, 15 Jul 2020 11:24:17 -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 20E243A0A24; Wed, 15 Jul 2020 11:24:15 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8F7FEF4076C; Wed, 15 Jul 2020 11:24:10 -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 C13C1F4076C for <rfc-interest@rfc-editor.org>; Wed, 15 Jul 2020 11:24:09 -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 GjD_B35VMfXm for <rfc-interest@rfc-editor.org>; Wed, 15 Jul 2020 11:24:04 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) by rfc-editor.org (Postfix) with ESMTPS id 2EA74F40766 for <rfc-interest@rfc-editor.org>; Wed, 15 Jul 2020 11:24:03 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 06FINqxD022966; Wed, 15 Jul 2020 19:23:52 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 979BB2203B; Wed, 15 Jul 2020 19:23:52 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 827882203A; Wed, 15 Jul 2020 19:23:52 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.113.100.254]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 06FINpo8023881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 Jul 2020 19:23:52 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Toerless Eckert' <tte@cs.fau.de>
References: <20200715174047.GF38490@faui48f.informatik.uni-erlangen.de> <0b4801d65ad2$66a268c0$33e73a40$@olddog.co.uk> <20200715181233.GH38490@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200715181233.GH38490@faui48f.informatik.uni-erlangen.de>
Date: Wed, 15 Jul 2020 19:23:51 +0100
Organization: Old Dog Consulting
Message-ID: <0b5a01d65ad5$1763aaf0$462b00d0$@olddog.co.uk>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHiRzsBszWW1GjpXtoJ+9jPO0BeAAIvln4VAXHSPqio1A6TsA==
Content-Language: en-gb
X-Originating-IP: 87.113.100.254
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25544.002
X-TM-AS-Result: No--17.508-10.0-31-10
X-imss-scan-details: No--17.508-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25544.002
X-TMASE-Result: 10--17.508300-10.000000
X-TMASE-MatchedRID: C/snMIRQLS3xIbpQ8BhdbC0x8J2DopEN7CU4ZmhBVXQs7eP5cPCWQ/Tp Te7ql1uPf8yw9uJdYaY9ale0zS6mxOdv6cWcdrc0+LORUvwlJdsX705dnYk+LLV5fSMRD1zq0SK biBNG/RJJf6XORbvxvAUPiDTfgVGN1dVV831uoNACOhpLDQSMVWpgzIYzEnZ55NZMkA6RI/CD/m A2vw4bvUT88A7P9JJ26Bg7b0GYfyZuBvtXfPycCfIq3+8DQd0oDEUX84f6hBwZwGrh4y4izI0G9 GYox3FwXah1UHwoJAnGljl9xdOl4d7/CnI+7e6xKhQHv3RCSep9iuvWn3J8Ku+RjJ4FenTB6s5I QlEERpdFWRVWxTiqvDJbVwVN5kxljSWgDaRwEZ30UeM2i2l3EMzzMs2dyeyVabJxhiIFjJm0197 CyYl4Vt1MCYJynNUuy5PqnJRFA+HlRxm3A2wKujl/1fD/GopdyJ1gFgOMhOmbk3ZgcwPRvwzKt8 /2P4LV33fj+sMArfOEbaqKQSlAZfy0AbIe6BCt5r8UFBUmdGnW8+C2PgAaznBC9t6MqfT7T7urX jpJ51o=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Subject: Re: [rfc-i] contributors section & tools
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>
Reply-To: adrian@olddog.co.uk
Cc: rfc-interest@rfc-editor.org, tools-discuss@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

I just looked at RFC 8663.
Long list of Contributors. Jari appears to extract them OK.

The XML for 8663 is available in the datatracker.

I see that the RPC elected to use my magic formatting which has the whole
section presented as <artwork> to get the format correct.

Not sure whether xml2rfc v3 has special tags for contributors. If so, that
would solve the problem.

A

-----Original Message-----
From: 'Toerless Eckert' <tte@cs.fau.de> 
Sent: 15 July 2020 19:13
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: -interest@rfc-editor.org; tools-discuss@ietf.org
Subject: Re: [rfc-i] contributors section & tools

Thanks, Adrian

Any example XML for which you're aware that the contributor section was
correctly parsed, then
i will just clone that formatting. I do like the idea to format with all the
same contact
info as if the contributors where authors, but thats just for emphasizing
for human readers,
not for a poor script.

Cheers
    Toerless

On Wed, Jul 15, 2020 at 07:04:35PM +0100, Adrian Farrel wrote:
> I believe Jari's script attempts to do this and counts Contributors in the
> author stats it generates
> 
> The script is very vulnerable to formatting errors and since the
> Contributors section is usually hand-crafted, the script often misses
people
> or documents.
> 
> Jari always welcomes fixes to the scripts. Last I looked there were lots
of
> "IF RFC=abcd THEN make this special exception"
> 
> A
> -----Original Message-----
> From: rfc-interest <rfc-interest-bounces@rfc-editor.org> On Behalf Of
> Toerless Eckert
> Sent: 15 July 2020 18:41
> To: tools-discuss@ietf.org; rfc-interest@rfc-editor.org
> Subject: [rfc-i] contributors section & tools
> 
> Is there any tool from e.g.: the IETF or Arkko publishing houses that
> actually deparses names
> in a contributors section and does something with that information ?
> (aka: allows recognition stats like they are done for authors) ?
> 
> I could not find anything in RFC 7749 that would allow me semantic tagging
> of contributors,
> Am i wrong ?
> 
> If not, then parsing would have to be difficult and heuristic, and i
> therefore fear the answer to my
> above question is NO ?
> 
> Wasthere not a time when we wanted to make contirbutors better
recognizeable
> ?
> 
> Thanks
>     Toerless
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest

-- 
---
tte@cs.fau.de

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