Re: [Terminology] WG Review: Effective Terminology in IETF Documents (term)

Keith Moore <moore@network-heretics.com> Fri, 23 April 2021 15:14 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 576253A1173 for <terminology@ietfa.amsl.com>; Fri, 23 Apr 2021 08:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 FU6tv3ezHGB7 for <terminology@ietfa.amsl.com>; Fri, 23 Apr 2021 08:14:47 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5C553A11EA for <terminology@ietf.org>; Fri, 23 Apr 2021 08:14:43 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id AFE89151C for <terminology@ietf.org>; Fri, 23 Apr 2021 11:14:40 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 23 Apr 2021 11:14:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=1PjdJf gLvZCwX7z4YRTTCWup5RPTpRTIP0G78twX8AM=; b=rHgqfrlN2kwBERVCKHwEio TK4vbAniAbFk4am0Kk+Vssiev7Tu6eDNjab8b+NkphLGlmH9mEe6wM/3WV9nG7d1 2jQAbf4kZeCe6T85P12nUmRi7HZhLqnkRJ5IvSaq3oEldxJ1w7/Cqjh0Ar9k0/v3 27VgmKSwvlQbwdsNqZTpY6ZcQB/1w8bLVvN2Uvsjfw20/rnflVl2Jm2XkiC+moVc VbAxXsOcjRJ/7jR/osVckKf02X5B/OCaV9MkDueIzHacpo1OVlX/oYbDz0ZVzA4h NWFkMCy9xR/uOErK9TMR8XAm/YFB+DVokjeMtXXIQwL+9UNcdM1vWn0Xn6XOnvkQ ==
X-ME-Sender: <xms:X-SCYCILKlB8WMLsLji5yZxA-jX7ieG-E2-K7HzJNqtOlUon5Hpgvg> <xme:X-SCYKJlNe9F-OdHh6JL9vR2cfObsMPTyvHTykWpfO05aqSGAP34Z_qARvnpwmqg9 TjO4UywdPjL7Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdduvddgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefheenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepveegheefhfdthe etudeuhfetvdekledufffhteeuvdekheeujefggfduieehtdefnecuffhomhgrihhnpehi vghtfhdrohhrghenucfkphepjeefrdduudefrdduieelrdeiudenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhk qdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:X-SCYCsqxPfZ20UZqsf9XnTCzwbNc2Sy7W4KEhIRPWg2rRqpXLjt_Q> <xmx:X-SCYHYC8CoA4qEqJKnJ-y2vsTbR5nOLKpcHP6cUGujZriI5qXbxIw> <xmx:X-SCYJbUcr8m4Bk3f2RkBiWcNg7AToUSiLQADjrYeczYA5QCIGRobg> <xmx:YOSCYJqeTjx0apY914uDrQmB-danhSQYiSjiXmr4vMBfS_ub60zTZQ>
Received: from [192.168.30.202] (c-73-113-169-61.hsd1.tn.comcast.net [73.113.169.61]) by mail.messagingengine.com (Postfix) with ESMTPA id AFF9324005D for <terminology@ietf.org>; Fri, 23 Apr 2021 11:14:39 -0400 (EDT)
To: terminology@ietf.org
References: <161918836800.7390.6996403788262551415@ietfa.amsl.com> <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <9ba2a315-e0ab-b8bf-415f-38c0a24500fa@network-heretics.com>
Date: Fri, 23 Apr 2021 11:14:38 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org>
Content-Type: multipart/alternative; boundary="------------BE098CB29018EFF1EB496412"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/Q9qEi94TL364kUJkmfD7tj6y26s>
Subject: Re: [Terminology] WG Review: Effective Terminology in IETF Documents (term)
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Apr 2021 15:14:52 -0000

I continue to believe that using a WG to address this problem would be 
unwise, as WGs are structurally ill-suited for this kind of problem.   
It's an important problem, but I recommend that IESG find another 
mechanism to address this issue: one that meets for a short time, 
deliberately solicits wide input (perhaps even inviting participants 
from other standards bodies) and is less confrontational or promotes 
quicker resolution of conflicts than is typical for mailing list 
discussions.   An IAB workshop (if IAB is willing) or a workshop with a 
similar style even if someone other than IAB hosts it, seems like a 
better choice.   (Granted, it's probably helped that IAB workshops have 
in the past, to my knowledge, always been face-to-face meetings, which 
might not be feasible in the near term.)

If IESG decides to go ahead with this, I recommend (a) taking all words 
about "exclusionary" out of the charter; and (b) explicitly stating that 
the WG will be shut down if it doesn't produce a draft by X date and 
finish WGLC by Y date.   (I recommend X = July 31 and Y = Oct 31).

As I said in earlier comments, it is imperative to choose chairs for 
this WG who are completely neutral about controversial topics (such as 
social theories), and who will discourage discussion of any topic not 
strictly consistent with "will use of this word improve or degrade the 
clarity or readability of IETF documents?"   (or something close to that)

The obvious lack of neutrality by gendispatch chairs has done a lot to 
undermine the credibility of that group, and this proto-WG is already 
tainted by that.

Keith

On 4/23/21 10:43 AM, Lars Eggert wrote:
> Hi,
>
> the latest version of the charter for TERM just went out for IETF-wide 
> review. This is the second such review cycle, which I deemed necessary 
> due to the number of changes to the charter text the first review 
> resulted in.
>
> Please send constructive comments on the charter for the proposed WG 
> to terminology@ietf.org <mailto:terminology@ietf.org>, or privately to 
> the IESG or even only to me as the responsible AD.
>
> To make sure that your feedback is taken into account on this latest 
> version of the charter text, I encourage you to send comments even if 
> you commented during the last IETF review cycle, or when the charter 
> was earlier discussed in GENDISPATCH.
>
> Thanks,
> Lars
>
>>
>> A new IETF WG has been proposed in the General Area. The IESG has not 
>> made
>> any determination yet. The following draft charter was submitted, and is
>> provided for informational purposes only. Please send your comments 
>> to the
>> IESG mailing list (iesg@ietf.org <mailto:iesg@ietf.org>) by 2021-05-03.
>>
>> Effective Terminology in IETF Documents (term)
>> -----------------------------------------------------------------------
>> Current status: Proposed WG
>>
>> Chairs:
>>  TBD
>>
>> Assigned Area Director:
>>  Lars Eggert <lars@eggert.org <mailto:lars@eggert.org>>
>>
>> General Area Directors:
>>  Lars Eggert <lars@eggert.org <mailto:lars@eggert.org>>
>>
>> Mailing list:
>>  Address: terminology@ietf.org <mailto:terminology@ietf.org>
>>  To subscribe: https://www.ietf.org/mailman/listinfo/terminology 
>> <https://www.ietf.org/mailman/listinfo/terminology>
>>  Archive: https://mailarchive.ietf.org/arch/browse/terminology/ 
>> <https://mailarchive.ietf.org/arch/browse/terminology/>
>>
>> Group page: https://datatracker.ietf.org/group/term/ 
>> <https://datatracker.ietf.org/group/term/>
>>
>> Charter: https://datatracker.ietf.org/doc/charter-ietf-term/ 
>> <https://datatracker.ietf.org/doc/charter-ietf-term/>
>>
>> The mission of the IETF as specified in BCP 95 is to produce high 
>> quality,
>> relevant technical documents that influence the way people design, 
>> use, and
>> manage the Internet. Contributions to the IETF, including 
>> Internet-Drafts and
>> RFCs, are most understandable and effective when they use terminology 
>> that is
>> clear, precise, and widely accessible to readers from varying 
>> backgrounds and
>> cultures. This maximizes the benefits the IETF derives from its central
>> principles, such as its open process and volunteer core.
>>
>> In the years leading up to the chartering of this working group, 
>> there has
>> been discussion in the IETF, in other standards organizations, and in the
>> broader technology industry about the use of certain terms of art in
>> technical writing and whether those and other terms have an exclusionary
>> effect. While opinions vary among IETF participants about this topic, 
>> there
>> is widespread agreement that the IETF community would benefit from advice
>> about using effective terminology that would improve clarity and
>> approachability.
>>
>> The TERM working group is therefore chartered to produce an 
>> Informational RFC
>> containing guidance to IETF participants on the use of effective 
>> terminology
>> that also minimizes exclusionary effects. The RFC will express general
>> principles for assessing when language is effective. The principles 
>> should be
>> derived considering input from a broad set of IETF participants. The 
>> WG will
>> identify and recommend external, independently updated resources 
>> containing
>> examples of potentially problematic terms and potential alternatives 
>> to IETF
>> participants for their consideration, to align its efforts with broader
>> activities by the technology industry.
>>
>> The TERM working group is a focused group aiming to produce a single
>> deliverable. It is designed to complement other efforts at fostering
>> inclusivity in the IETF and will liaise with appropriate external groups,
>> such as other SDOs or industry initiatives, to coordinate.
>>
>> The output of this WG will provide guidance to IETF participants and 
>> will not
>> restrict the type or content of contributions that can be made to the 
>> IETF
>> standards process. The output of this WG may inform a potential future
>> activity by the RFC Editor to establish terminology guidance for the 
>> overall
>> RFC series, but does not constrain any such future action.
>>
>> Milestones:
>>
>>  Jun 2021 - Adopt draft providing informational terminology 
>> recommendations
>>
>>  Dec 2021 - Submit informational terminology recommendations to IESG
>