Re: [rfc-i] contacts section?

Miek Gieben <miek@miek.nl> Fri, 26 February 2021 10:01 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 A276D3A10B5; Fri, 26 Feb 2021 02:01:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 (body has been altered)" header.d=miek-nl.20150623.gappssmtp.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 npsM-f-ly_pc; Fri, 26 Feb 2021 02:01:35 -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 B3CF93A0FD3; Fri, 26 Feb 2021 02:01:35 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 14233F4074D; Fri, 26 Feb 2021 02:01:24 -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 A64A7F4074D for <rfc-interest@rfc-editor.org>; Fri, 26 Feb 2021 02:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.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 EpM3IyboJ49Q for <rfc-interest@rfc-editor.org>; Fri, 26 Feb 2021 02:01:19 -0800 (PST)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) by rfc-editor.org (Postfix) with ESMTPS id DADA8F4074B for <rfc-interest@rfc-editor.org>; Fri, 26 Feb 2021 02:01:18 -0800 (PST)
Received: by mail-ej1-x636.google.com with SMTP id a22so13793557ejv.9 for <rfc-interest@rfc-editor.org>; Fri, 26 Feb 2021 02:01:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=FH5v5C7PiCP3o9mwt0P+2sbzNcxNfnWetxvab2F1OtI=; b=rr3T3Gcg9Zre/dvl9PvqEcRfVoBbQU8/qnJ8iNXe14SaxqSWkX//M63WIakoo8q++T kEq+zTbOT7BJms2zgkZNorMCn1WeEkFxfDHnwmpxyOD7ANoxUsQ+TRF2Xivr6QTxFxtH IK1Xe5jv3+OX3ZE1uCyt29qldbYnvY4yY2hmsgSqEWVxzeFDNgPz7YG8jW4XYE2x/g23 +NfoxUQJODvNVVOrS/jYgk6pUwxAyZOtaGwJnUPaxuzsrx+4Ir6w5hHGjWr371shbFtN zAPj5AvEuow3A3DORHUL4JAMXdOhP7yOLsXdZpl/R9GjOMKvUM+vcTpG/s3qhU71F1j9 FrsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=FH5v5C7PiCP3o9mwt0P+2sbzNcxNfnWetxvab2F1OtI=; b=taIlhKRS5SHreZTUBxJt/b6lcv4YmBC6kgirgVMjE6+w9h7SjQkzgSvTr0Vh98QEZC RjdjcOLFOLhdrTFZWyaVi9xdvD/bi8P/sU8gFUVnwdhJUbDC7pE+RxdYPM6XXUfnYkih 2QdeDyqOg00JA8stBTXfFLeNLNnH6GY9v4T7wHQhoEk/jl76Csj9zJAQQdrV/NrqC6oe +HRsJ5gSZeTGi15j7LGDLYLZm/hSX8DDvKW6AmwkiTba1zqNyN6vfmNmHCFBJgM2XmSf wDrF7GUseTbVZ2TJgwfQoMMoxi2ULqVRKT7nPeerTrQoU6yfbEKCBO3zvQCzK+oVh2lC xF+A==
X-Gm-Message-State: AOAM532DEcSkRLn+q53WwnUv384Xu7xnQuA1ylSXse6gfHeqWOZC4T46 tA5JbbqoCezTAd4TQSQCHMs9bA==
X-Google-Smtp-Source: ABdhPJyQEWNcpHA/4k5kvddnbaxuUmvOXKQMGUhe5qmo9XJI8VpptHP+O8mxlT9aUyu9VVw+7c3Vyg==
X-Received: by 2002:a17:906:9386:: with SMTP id l6mr2354398ejx.455.1614333685818; Fri, 26 Feb 2021 02:01:25 -0800 (PST)
Received: from miek.nl (dhcp-077-251-206-012.chello.nl. [77.251.206.12]) by smtp.gmail.com with ESMTPSA id n19sm5058026ejb.51.2021.02.26.02.01.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Feb 2021 02:01:20 -0800 (PST)
Date: Fri, 26 Feb 2021 11:01:16 +0100
From: Miek Gieben <miek@miek.nl>
To: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <20210226100116.GA8958@miek.nl>
References: <20210226092712.GA7967@miek.nl> <0bcd3cac-6fa4-b7e1-63ae-e81380bb07cf@gmx.de>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <0bcd3cac-6fa4-b7e1-63ae-e81380bb07cf@gmx.de>
Subject: Re: [rfc-i] contacts section?
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
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>

[ Quoting <julian.reschke@gmx.de> in "Re: [rfc-i] contacts section?..." ]
>><contact>. The txt and html rendering just show the full name of the
>>person as if I typed
>>that directly.
>
>That's what happens when you use <contact> inside a text flow. This was
>added relatively recently to allow non-ASCII characters in names.

Ok...

>The *original* intent was to <contact> to work exactly like <author>,
>except that you place it as a child element of <section> (and you could
>call that section anything you want). See
><https://greenbytes.de/tech/webdav/draft-iab-rfc7991bis-latest.html#element.contact>.

So the process then is that I add all the contacts in the text (if I need to reference
them in the text somewhere) and then create a section and add a (sub)set of contacts that
are then rendered differently?

This also means I can't put attribution here? I.e. "Sam wrote section 5", because that
would need to be in a <t> ?

>>I was (naively?) expecting a Contacts section, just like the "Author's
>>Addresses' that
>>lists some more information, or another way to see that more information
>>is available.
>
>There is no auto-generated section (and AFAICT, it's not needed).

Just generating such a section with all the given metadata would make the element more
useful (but IMO)

/Miek

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