Re: [Terminology] [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)
Keith Moore <moore@network-heretics.com> Thu, 29 April 2021 20:19 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 47F0E3A0C5F for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 13:19:53 -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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=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 mSyYviX17bSn for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 13:19:48 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E06823A0C5E for <terminology@ietf.org>; Thu, 29 Apr 2021 13:19:48 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 0250DFA4 for <terminology@ietf.org>; Thu, 29 Apr 2021 16:19:46 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 29 Apr 2021 16:19:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=oa5GoPSYmFveIH5eqs7XRycJiq4roxpeVqHlAVfIk EM=; b=EM4C5qZ79N/YI2Le25wS5BiYtV74d6e4AYymwatZXmNPG5A4N5NC/qUko 1mHkeOd//rv34qhBwUlcaI9caNTLY3UsX35uBlV33NzOdFMPQ9Nk20oVeAZsqr/y 3nQ7b3yUL4n3Rd64O9a62n4ihqNOQ6nqN3sjobaH/14ka1ZOUUSkycn8xbVkd/zx 7ZmpUnl0p02u4n03jEVeqAbF/L6dvc0kAEdojJYOjPLGgchVR5oJqtFkFCqw0pQI 9aoj1MqZda7bMFz1g1cpUBmeLN7hR4SrkA81UDysVOO5JbQnDQp4pCdw1/pe+Ap4 56euZEnEnXg8OTLJHUGgfrVY9qbZw==
X-ME-Sender: <xms:4RSLYDqDKxdEGIHBqRh2ot7m_Bd1zaUhShc_Ot6Xl_0g9Ac1_0ElJw> <xme:4RSLYNoX24IvGavsHiEXmCkQeYAkUMUORKjFJr_chMBky8rdpFEEqss6VFw_eV5DH vAq6pDlGqp_BA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvgedgudehtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedthe efgfefgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppeejfedr uddufedrudeiledriedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:4RSLYANcD48j2B97nn5mG1qLk1WaZzTT8Zuq2-UZ4sw3SOrGQw5YYw> <xmx:4RSLYG5L3Gd_voyoKj_UpB7BnJCfH3hq7rS2b9eEw8osvBKEw9KkXQ> <xmx:4RSLYC62PE5_gtJhvnnO_Bo56WOpE9c_YUZ8O8CcGtPPTEzeL8mchQ> <xmx:4hSLYBJ_s8nHB7-SUEf3KJPnSe5Fd3J52Gpahnf2VQ7-E08KPr2ZPA>
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 for <terminology@ietf.org>; Thu, 29 Apr 2021 16:19:45 -0400 (EDT)
To: terminology@ietf.org
References: <7f159ab8-2b21-95ce-56d9-20e45a78ade8@lounge.org> <F0C32F0D-7026-47C8-B2AF-29BB8E87C3D8@ietf.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <1f02e8a8-110a-9f26-83d9-0cc8d8302aae@network-heretics.com>
Date: Thu, 29 Apr 2021 16:19:45 -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: <F0C32F0D-7026-47C8-B2AF-29BB8E87C3D8@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/mBzic1_nf7k9Qap-3O7GSi0OFTg>
Subject: Re: [Terminology] [Gendispatch] 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: Thu, 29 Apr 2021 20:19:53 -0000
On 4/28/21 3:02 AM, Jay Daley wrote: (In response to Dan, I believe) > I’m struggling to understand how it’s possible to suggest certain > words are problematic, and therefore imply they should be avoided, > while attacking the principle of avoiding problematic words. Perhaps > I’m mistaken but you appear to agree with the principle that specific > words have uncomfortable meanings for specific groups and that they > should be avoided as a result. I can't speak for Dan, but I wonder if the apparent contradiction is due to differing ideas about rigidity and specificity. There are a few words that are better avoided under the vast majority of circumstances. There are other words that are problematic in certain contexts, but perhaps not problematic in others. Just to pick an often debated example, the word "master" may be problematic for some if it's being used to express a control relationship (especially in relation to "slave"), but not problematic at all if used to indicate its traditional English meaning of "teacher" or some degree of expertise (e.g. "master craftsperson"). As for "uncomfortable meanings for specific groups", I wonder how large, or significant, or perhaps marginalized, a group needs to be to be worth forbidding or discouraging the use of a word. Or under what situations causing such discomfort is considered responsible or even laudable, versus situations in which causing discomfort is seen as irresponsible or reprehensible. I have found in the past that some people who insist on policing others' language are quite willing to cause distress among people who respectfully see things from a different point-of-view, even to the point of subjecting them to vituperative public criticism and working publicly and privately to malign their reputations, with no apparent concern for either the targeted individuals' discomfort or the potential reasonableness of the targeted individuals' points of view. I also wonder why there seems to be a concern for members of specific groups who might be uncomfortable, but less so for individuals who are so not easily categorized, as if the only thing that matters about an individual is the way people use superficial characteristics to pigeonhole them. So while I don't think any of us should be trying to make any RFC readers uncomfortable, I wonder about the reasonableness of a standard of "must/should not make members of specific groups uncomfortable". Keith
- [Terminology] WG Review: Effective Terminology in… Lars Eggert
- Re: [Terminology] WG Review: Effective Terminolog… Carsten Bormann
- Re: [Terminology] [Gendispatch] WG Review: Effect… Stephen Farrell
- Re: [Terminology] WG Review: Effective Terminolog… Keith Moore
- Re: [Terminology] WG Review: Effective Terminolog… Maisonneuve, Julien (Nokia - FR/Paris-Saclay)
- Re: [Terminology] [Gendispatch] WG Review: Effect… Andrew Campling
- Re: [Terminology] [Gendispatch] WG Review: Effect… Jim Fenton
- Re: [Terminology] WG Review: Effective Terminolog… Eliot Lear
- Re: [Terminology] WG Review: Effective Terminolog… Andrew Campling
- Re: [Terminology] [Gendispatch] WG Review: Effect… Lloyd W
- Re: [Terminology] [Gendispatch] WG Review: Effect… Stephen Farrell
- Re: [Terminology] [Gendispatch] WG Review: Effect… reynolds
- Re: [Terminology] [Gendispatch] WG Review: Effect… Lloyd W
- Re: [Terminology] [Gendispatch] WG Review: Effect… Stephen Farrell
- Re: [Terminology] [Gendispatch] WG Review: Effect… Lloyd W
- Re: [Terminology] [Gendispatch] WG Review: Effect… Pete Resnick
- Re: [Terminology] [Gendispatch] WG Review: Effect… Eliot Lear
- Re: [Terminology] WG Review: Effective Terminolog… Mallory Knodel
- Re: [Terminology] WG Review: Effective Terminolog… Eliot Lear
- Re: [Terminology] WG Review: Effective Terminolog… Keith Moore
- Re: [Terminology] WG Review: Effective Terminolog… Mallory Knodel
- Re: [Terminology] [Gendispatch] WG Review: Effect… Niels ten Oever
- Re: [Terminology] [Gendispatch] WG Review: Effect… Mallory Knodel
- Re: [Terminology] [Gendispatch] WG Review: Effect… Salz, Rich
- Re: [Terminology] [Gendispatch] WG Review: Effect… Niels ten Oever
- Re: [Terminology] WG Review: Effective Terminolog… Bron Gondwana
- Re: [Terminology] WG Review: Effective Terminolog… Jim Fenton
- Re: [Terminology] [Gendispatch] WG Review: Effect… Dan Harkins
- Re: [Terminology] [Gendispatch] WG Review: Effect… Lloyd W
- Re: [Terminology] [Gendispatch] WG Review: Effect… Jay Daley
- Re: [Terminology] [Gendispatch] WG Review: Effect… Bron Gondwana
- Re: [Terminology] [Gendispatch] WG Review: Effect… Jay Daley
- Re: [Terminology] [Gendispatch] WG Review: Effect… Lloyd W
- Re: [Terminology] WG Review: Effective Terminolog… Mallory Knodel
- Re: [Terminology] [Gendispatch] WG Review: Effect… Dan Harkins
- Re: [Terminology] WG Review: Effective Terminolog… Viktor Dukhovni
- Re: [Terminology] [Gendispatch] WG Review: Effect… Vittorio Bertola
- Re: [Terminology] WG Review: Effective Terminolog… Keith Moore
- Re: [Terminology] WG Review: Effective Terminolog… Keith Moore
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] [Gendispatch] WG Review: Effect… Salz, Rich
- Re: [Terminology] [Gendispatch] WG Review: Effect… Salz, Rich
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] WG Review: Effective Terminolog… reynolds
- Re: [Terminology] WG Review: Effective Terminolog… Brian E Carpenter
- Re: [Terminology] WG Review: Effective Terminolog… Jim Fenton
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] WG Review: Effective Terminolog… Dan Harkins
- Re: [Terminology] WG Review: Effective Terminolog… Christian Huitema
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] [Gendispatch] WG Review: Effect… Niels ten Oever
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] [Gendispatch] WG Review: Effect… S Moonesamy
- Re: [Terminology] [Gendispatch] WG Review: Effect… Salz, Rich
- Re: [Terminology] [Gendispatch] WG Review: Effect… Keith Moore
- Re: [Terminology] [Gendispatch] WG Review: Effect… Salz, Rich