Re: [rfc-i] [Tools-discuss] contributors section & tools

Carsten Bormann <cabo@tzi.org> Thu, 16 July 2020 22:45 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 3730B3A0DC9; Thu, 16 Jul 2020 15:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.862
X-Spam-Level:
X-Spam-Status: No, score=-0.862 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, LONGWORDS=2.035, MAILING_LIST_MULTI=-1, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 jYSK2oEN80rL; Thu, 16 Jul 2020 15:45:04 -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 C15373A0DC5; Thu, 16 Jul 2020 15:45:04 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5C45EF40742; Thu, 16 Jul 2020 15:44:58 -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 C991EF40742 for <rfc-interest@rfc-editor.org>; Thu, 16 Jul 2020 15:44:57 -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 R73u4dL6khsf for <rfc-interest@rfc-editor.org>; Thu, 16 Jul 2020 15:44:53 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 2A4D8F40741 for <rfc-interest@rfc-editor.org>; Thu, 16 Jul 2020 15:44:53 -0700 (PDT)
Received: from [192.168.217.105] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4B78TQ04DzzyVJ; Fri, 17 Jul 2020 00:44:58 +0200 (CEST)
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <69BD6664-8CC0-4400-83B6-4BD356F1E45F@tzi.org>
Date: Fri, 17 Jul 2020 00:44:57 +0200
Message-Id: <3CCFC1B7-06F7-4292-91FD-685535584E5B@tzi.org>
References: <69BD6664-8CC0-4400-83B6-4BD356F1E45F@tzi.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPhone Mail (17F80)
Subject: Re: [rfc-i] [Tools-discuss] 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-interest@rfc-editor.org>, Toerless Eckert <tte@cs.fau.de>, Warren Kumari <warren@kumari.net>, tools-discuss@ietf.org
Content-Type: multipart/mixed; boundary="===============4932708017367018744=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Or - - v 3 in XXL rfc if you call that directly

Sent from mobile, sorry for terse and autocorrect

> On 17. Jul 2020, at 00:37, Carsten Bormann <cabo@tzi.org> wrote:
> 
> You need the -3 flag in kdrfc
> 
> Sent from mobile, sorry for terse
> 
>>> On 16. Jul 2020, at 23:01, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>>> 
>> 
>> Carsten Bormann <cabo@tzi.org> wrote:
>>>>> On 2020-07-15, at 20:50, Toerless Eckert <tte@cs.fau.de> wrote:
>>>> 
>>>>> 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.
>> 
>>> It does.  They are not very well documented.
>> 
>>> Kramdown-rfc supports them by adding a YAML entry like the authors entry:
>> 
>>> contributor:
>>> - name: Peter Occil
>>> email: poccil14 at gmail dot com
>>> - name: Many More
>>> org: To do
>> 
>> Thank you, I very much like this.
>> I also noticed today that there was an IESG todo item:
>>    Warren Kumari to work on acknowledging shepherds, directorate
>>    reviewers in a more standardized/formal way.
>>    - Added 2019-10-10 (18 telechats ago)
>> 
>> so, I tried this.
>> 
>> I had a section called "Contributors" already, in the old textual form.
>> And it actually details some major contributions, so I didn't want to remove
>> it, so I have slightly renamed it. ("Notable Contributions")
>> 
>> With just name:/email:, I get many complaints from xml2rfc:
>> <string>: Line 1655: No declaration for element contact
>> <string>: Line 1655: No declaration for attribute initials of element contact
>> <string>: Line 1655: No declaration for attribute surname of element contact
>> <string>: Line 1655: No declaration for attribute fullname of element contact
>> 
>> I obviously know how to solve this by putting more stuff in.
>> But, the bigger problem seems to be:
>> 
>> <string>: Line 1614: Element section content does not follow the DTD,
>> expecting ((t | figure | texttable | iref)* , section*), got (name contact
>> contact contact contact contact contact contact contact contact contact
>> contact contact contact)
>> 
>> kramdown-rfc2629-1.3.8
>> xml2rfc 2.23.1
>> ... upgrading to 2.46.0.
>>    same result.
>> 
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>> -= IPv6 IoT consulting =-
> _______________________________________________
> 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