Re: [Xml-sg-cmt] contact element

Sandy Ginoza <sginoza@amsl.com> Wed, 04 August 2021 22:32 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F381E3A0EF9 for <xml-sg-cmt@ietfa.amsl.com>; Wed, 4 Aug 2021 15:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 NYzMLEv8LorE for <xml-sg-cmt@ietfa.amsl.com>; Wed, 4 Aug 2021 15:32:28 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E079E3A0EFA for <xml-sg-cmt@ietf.org>; Wed, 4 Aug 2021 15:32:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C220B389EF4; Wed, 4 Aug 2021 15:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKGZtbsWv5j9; Wed, 4 Aug 2021 15:32:28 -0700 (PDT)
Received: from 2603-8000-9603-b513-68a8-fa8b-ea8a-efd4.res6.spectrum.com (2603-8000-9603-b513-68a8-fa8b-ea8a-efd4.res6.spectrum.com [IPv6:2603:8000:9603:b513:68a8:fa8b:ea8a:efd4]) by c8a.amsl.com (Postfix) with ESMTPSA id 872CE389ECE; Wed, 4 Aug 2021 15:32:28 -0700 (PDT)
From: Sandy Ginoza <sginoza@amsl.com>
Message-Id: <28B1FC4B-BB9E-4468-8510-29C60A7421C2@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D410AAC1-9B87-4369-B320-A5A954502981"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 04 Aug 2021 15:32:26 -0700
In-Reply-To: <0a8914d2-12c5-4d71-5429-8859fde3ca4c@mozilla.com>
Cc: XML weed whackers <xml-sg-cmt@ietf.org>, John R Levine <johnl@taugh.com>
To: Peter Saint-Andre <stpeter@mozilla.com>
References: <777df480-1462-ea6d-2d40-deae7db4256b@mozilla.com> <fa413435-7154-2f6d-88ef-9036ed356c46@taugh.com> <237CB7B6-C6A7-43BE-BFD6-349C3B7B74CE@amsl.com> <39d4d6eb-db7f-63db-e505-6c69268f543e@mozilla.com> <A2ED6098-6AB8-4D25-8859-92A7E36DCEA5@amsl.com> <AC4643E5-6A74-4838-8E79-8C7633E55585@amsl.com> <44541e6d-ce08-d531-424d-7d57fb5195d1@mozilla.com> <05F2AB3A-EEB5-412E-89CE-681B328D50FB@amsl.com> <0a8914d2-12c5-4d71-5429-8859fde3ca4c@mozilla.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/5d9vII4YO0nAjanl5BmnU8SPZtE>
Subject: Re: [Xml-sg-cmt] contact element
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2021 22:32:34 -0000

Hi Peter, John,

> Did you two ever get a chance to write this up?

Finally getting back to this - sorry for the delay.  This is a clarification of item 2 on <https://www.rfc-editor.org/rse/wiki/doku.php?id=v3_guidance_received> and an attempt at building on Peter’s strawman text regarding how <contact> should be used.  

The following is based on how <contact> has been used in recent pubs from each stream.  

<contact> is recommended for the following:
names mentioned in the Acknowledgments and Contributors sections of documents. 
(not typically used for author names of draft itself, e.g., Author A would like to thank…)
individual names in the IANA registrations (e.g., contacts).
IAB members, workshop participants, and the program committee.
(not a list of names under position papers, as that is really about the referenced doc)
wherever needed to render names/organizations with non-ASCII characters correctly
The RPC will not proactively add the <contact> element to a document outside of the areas listed above, but authors are welcome to do so.  

The IAB workshop participants and program committee got thrown in because they usually contain one or more names with non-ASCII chars, so it seemed like we should use <contact> consistently within the section.  Based on the discussion below, would participants and committee members fall into the last category, where <contact> is only added where needed to display non-ASCII chars? 

These are a couple of recent RFCs from the IAB stream:
https://www.rfc-editor.org/rfc/rfc9075.html
https://www.rfc-editor.org/rfc/rfc8980.html


Thanks!
Sandy 

> On May 10, 2021, at 2:56 PM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
> 
> On 5/10/21 3:13 PM, Sandy Ginoza wrote:
>> You’re still incredibly fast with your replies! 
> 
> I'm either incredibly fast or incredibly slow. Not much in between. :-)
> 
>>> On May 10, 2021, at 1:30 PM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
>>> 
>>> That's a lot of contacts. :-)
>>> 
>>> Do we even have contact information for everyone who submitted position
>>> papers?
>> 
>> No, but we don’t necessarily have contact info for the individuals listed in the other sections either.
>> That said, I’m thinking that not using <contact> here makes sense in that a reader could go to the relevant reference and get the info from the paper directly. 
> 
> True.
> 
>> One problem with this approach might be if we need to use <contact> for names with non-ASCII characters.  Based on my quick spot check, I don’t think this is problematic for this document; the names seem to match what appears in the docs.  RFC 8980 included Stéphane Bortzmeyer, Moritz Müller, and Jörg Ott. 
>> 
>> Does it make sense to use <contact> in this section only for the names that contain non-ASCII chars?  Is it problematic that use of <contact> would be inconsistent? 
> 
> Hmm, well, <contact> is used for two purposes:
> 
> 1. Flagging that we have contact information for a person or entity.
> 
> 2. Kludging support for non-ASCII characters in the name of a person or
> entity.
> 
> :-)
> 
> Given that these purposes aren't consistent, I'm not sure that
> consistency in tagging is critically important.
> 
> Peter
> 
> -- 
> Xml-sg-cmt mailing list
> Xml-sg-cmt@ietf.org
> https://www.ietf.org/mailman/listinfo/xml-sg-cmt