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

Jim Fenton <fenton@bluepopcorn.net> Fri, 23 April 2021 16:17 UTC

Return-Path: <fenton@bluepopcorn.net>
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 669723A14B1 for <terminology@ietfa.amsl.com>; Fri, 23 Apr 2021 09:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 5nX5a3vmh2JP for <terminology@ietfa.amsl.com>; Fri, 23 Apr 2021 09:17:13 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D90B53A14AF for <terminology@ietf.org>; Fri, 23 Apr 2021 09:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=WUeVd3t6m+TzcVHOPBWyO0VZWH1kh4auCqZi+8KRtys=; b=Xr29578trIKzpH180dKo399pGl 0AYIVILHMzsRxKgseX3Za5M5C6HVatz4QbTdOKhz1o85IpaGMv/LRPP/0YBHJIoTSiGaTsMRw2GFo XYmcyhzjR3sOyTYz2X15Y1EVCEDzoZZ/H1AYoYZXOsEMBJHMTRwo5hOinFfg+wCdmZnU=;
Received: from [2601:647:4400:1261:6495:2e8f:7704:a1a2] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1lZyUQ-0005Gb-Vg; Fri, 23 Apr 2021 09:17:11 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: terminology@ietf.org
Date: Fri, 23 Apr 2021 09:17:09 -0700
X-Mailer: MailMate (1.14r5757)
Message-ID: <AEDA405C-EA7A-4B16-A7B1-9F4224D2422C@bluepopcorn.net>
In-Reply-To: <219fd089-1d7c-88f9-c3c6-80872fd86319@cs.tcd.ie>
References: <161918836800.7390.6996403788262551415@ietfa.amsl.com> <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org> <219fd089-1d7c-88f9-c3c6-80872fd86319@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/HWEZwITFJosUcuRqikPyn61BDJg>
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: Fri, 23 Apr 2021 16:17:18 -0000

On 23 Apr 2021, at 8:03, Stephen Farrell wrote:

> Hiya,
>
> In general I support this.
>
> I think it's a mistake to craft or point at a curated
> list of bad terms as I've said before but I seem to be
> in the rough on that, which is ok.

I’m not sure you are “in the rough” on that. I would much rather 
see the WG craft a set of principles with respect to document 
inclusiveness than to curate a blocklist of bad terms or reference 
someone else’s list. It would be fine to include some non-normative 
examples to illustrate what is being talked about, however. IMO it’s 
possible to use certain of the frequently-discussed words without being 
non-inclusive, and it’s definitely possible to be non-inclusive 
without using any of those words.

Before someone points out that this is only to be an Informational RFC, 
a lot of people don’t see the “informational” label. I can point 
to informational RFCs that government agencies have mandated deployment 
of, and at least one agency is already pointing to 
draft-knodel-terminology-01 as “IETF”, illustrating how easy it is 
to have these things over-interpreted.

-Jim