Re: [rfc-i] contributors section & tools

'Toerless Eckert' <tte@cs.fau.de> Wed, 15 July 2020 18:50 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 51A7C3A0C8F; Wed, 15 Jul 2020 11:50:39 -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=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 frnAdpIOWXCs; Wed, 15 Jul 2020 11:50:37 -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 1A1683A0E9D; Wed, 15 Jul 2020 11:50:37 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 859F8F4075C; Wed, 15 Jul 2020 11:50:32 -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 2B432F4075C for <rfc-interest@rfc-editor.org>; Wed, 15 Jul 2020 11:50:31 -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 BW6-_DnMqf_N for <rfc-interest@rfc-editor.org>; Wed, 15 Jul 2020 11:50:26 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) by rfc-editor.org (Postfix) with ESMTPS id 08187F40753 for <rfc-interest@rfc-editor.org>; Wed, 15 Jul 2020 11:50:25 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 8CE3E548068; Wed, 15 Jul 2020 20:50:23 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 866EF440043; Wed, 15 Jul 2020 20:50:23 +0200 (CEST)
Date: Wed, 15 Jul 2020 20:50:23 +0200
From: 'Toerless Eckert' <tte@cs.fau.de>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <20200715185023.GI38490@faui48f.informatik.uni-erlangen.de>
References: <20200715174047.GF38490@faui48f.informatik.uni-erlangen.de> <0b4801d65ad2$66a268c0$33e73a40$@olddog.co.uk> <20200715181233.GH38490@faui48f.informatik.uni-erlangen.de> <0b5a01d65ad5$1763aaf0$462b00d0$@olddog.co.uk>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <0b5a01d65ad5$1763aaf0$462b00d0$@olddog.co.uk>
User-Agent: Mutt/1.10.1 (2018-07-13)
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>
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>

On Wed, Jul 15, 2020 at 07:23:51PM +0100, Adrian Farrel wrote:
> 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.

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

Sounds like Jari is probably scraping the txt output. Fine.

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

Scanning through rfc7991 there seems to be no enhancements in this respect.

Cheers
    Toerless

> 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

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