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

Mallory Knodel <mknodel@cdt.org> Tue, 06 April 2021 12:53 UTC

Return-Path: <mknodel@cdt.org>
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 1C95A3A24CC for <terminology@ietfa.amsl.com>; Tue, 6 Apr 2021 05:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 3XPgjbtreSzv for <terminology@ietfa.amsl.com>; Tue, 6 Apr 2021 05:53:42 -0700 (PDT)
Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC16C3A202A for <terminology@ietf.org>; Tue, 6 Apr 2021 05:52:47 -0700 (PDT)
Received: by mail-qv1-xf2e.google.com with SMTP id j17so6985194qvo.13 for <terminology@ietf.org>; Tue, 06 Apr 2021 05:52:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to; bh=gR18CSGzo9SOpPIqyGIuAwovZ2iMXW98xs2X0ZW3Dvk=; b=cWvxjA/VtQ2wOC16BQWs5x+i3VZZtdozBlog8bS1lpNPvwZWuMXyTv54LNRKpPgzR0 I35Me8OdkhAPpG80zx9vnQ8hHxTzJWJ3xrNr3xk3reEJ82mMAv7M6SiIUUasSSx9c/T7 zV/UgNR6q2VMtbkB05XE7FEjo/t4fa+EnzdMI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to; bh=gR18CSGzo9SOpPIqyGIuAwovZ2iMXW98xs2X0ZW3Dvk=; b=nd1ZC/xlcoNcalSVlHUl6gAuz/SKgUTZ7x65HkIzoqmn0uomn/UYQrsgjMGmx9Axbr sQXqSW3HcNSK2Izda+oegfH0HE6FRR2srrnknG51aCvIMzchWHEosM9Ruhj4hxOFxUq5 RuR7TkToiWXmrysLAFQejPED+4PmM7Y9uIclp/Vuwdnwc35KqmXqBOfsKuNSJn4jYNBK Bln1hF1bkjiZnxw4sJG8J02Zxg2jwG+gy0sImj00ArF8sGMOpQL8MTySzcm4e4P6xRPB FKNlcUiRgVJwEixB3x3E+z4IeFvJN8uH2PracrjhKP2AzNM1sTcecOITt2xBUOJXdZ9X 7psg==
X-Gm-Message-State: AOAM530yIz/IyDgS7BdzVBWW1Q+bZW7xzAlyv0cnqaENENtzGZ0++b08 Y3oceYg2DiiOCJSxTmI1XosuDg==
X-Google-Smtp-Source: ABdhPJz4HjsLM4waGO5Q6p4cbqDL0Ho8F63Kc0Mv9CVoI71eyGHZa/s/H88nzpHilHYAoF5RLBUqIA==
X-Received: by 2002:a0c:9cc2:: with SMTP id j2mr28771379qvf.2.1617713565176; Tue, 06 Apr 2021 05:52:45 -0700 (PDT)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with UTF8SMTPSA id v35sm14555486qtd.56.2021.04.06.05.52.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Apr 2021 05:52:44 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------cAl7Xiby3CBoDkDME0ts5S5z"
Message-ID: <97452adf-4177-c3d4-608b-9346f67b344e@cdt.org>
Date: Tue, 06 Apr 2021 08:52:43 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:87.0) Gecko/20100101 Thunderbird/87.0
Content-Language: en-US
To: Eliot Lear <lear@cisco.com>
Cc: Carsten Bormann <cabo@tzi.org>, "terminology@ietf.org" <terminology@ietf.org>, The IESG <iesg@ietf.org>
References: <161677836041.26846.148884814967107510@ietfa.amsl.com> <0b747dd8-f4f5-23a1-d09d-91ea30f525a7@cdt.org> <3E83A93B-2AD3-497B-B40E-EC2E0C4E2711@eggert.org> <CAGVFjMJaYjroPLL5-Ns50CeyAB33thH5HpLgh0EXxPmxob4CEg@mail.gmail.com> <4C9BFF1C-5BC3-4980-B1D7-92812086C976@tzi.org> <bbdc6b67-ed0a-0ee5-1606-263c7bdec485@cdt.org> <90270CD1-23BA-455D-A5E4-BB15577D1276@cisco.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <90270CD1-23BA-455D-A5E4-BB15577D1276@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/-e8__8a9Un6raiupZCbUm0mvUKk>
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: Tue, 06 Apr 2021 12:53:52 -0000

Hi,

On 4/6/21 1:01 AM, Eliot Lear wrote:
> The whole point of that text, as far as I am concerned, was to keep 
> engineers from trying to get into language games, for which not one of 
> us is equipped to properly answer.  If anything, to me the original 
> text isn’t restrictive enough, because almost nobody else in the 
> industry is properly equipped to answer the question being asked. 
>  The compromise is that we have *one*, and not *multiple*, arguments 
> about which list to use.  Perhaps we can even find one or two people 
> who know what they are talking about when they create such a thing.
>
>> On 5 Apr 2021, at 16:34, Mallory Knodel <mknodel@cdt.org 
>> <mailto:mknodel@cdt.org>> wrote:
>>
>> I removed restrictions to the text. Your point about IETF creativity 
>> on these terms may be right 99% of the time, and suggest that this be 
>> a major consideration whenever recommendations are made. But to 
>> restrict the charter at this stage seems like it would be unhelpful 
>> possibly in the future.
>>
>> On 4/5/21 10:26 AM, Carsten Bormann wrote:
>>> Sorry I didn’t pay attention to this discussion yet.
>>> I don’t think the IETF should become creative in what terminology 
>>> it wants to shun.
>>> The proposed charter text was exactly right as it was.

I don't see why the IETF shouldn't demonstrate leadership, where needed. 
In the case of the draft Niels and I wrote, we didn't come up with those 
arguments or the term pairs and their replacements. Other people did 
that. But what we did was coalesce research and draw conclusions in the 
form of arguments tailored to the IETF. Is that external?

See also: https://github.com/ietf/terminology

This is really useful, even if it might eventually prove to be 
duplicative effort. In the beginning, it was the right step because as 
an exercise it demonstrated scale to the IETF audience. Other groups are 
doing the same thing, but it's not always clear what will emerge in 
perpetuity (independently updated). Something like the Inclusive Naming 
Initiative cites our draft, so is that objectionably self-referential?

It is the TERM group who should be grappling with these questions 
through it's /work/, not the wider group's discussion of the charter.

-Mallory

>>>
>>>
>>>> On 2021-03-30, at 22:55, Mallory Knodel <mknodel@cdt.org 
>>>> <mailto:mknodel@cdt.org>> wrote:
>>>>
>>>> Sure, change this sentence:
>>>>
>>>> The WG will identify and recommend an external, 
>>>> independently-updated resource containing examples of potentially 
>>>> problematic terms and potential alternatives to IETF participants, 
>>>> in order to align its efforts with broader activities by the 
>>>> technology industry.
>>>>
>>>> To:
>>>>
>>>> The WG will identify and recommend language resources on inclusive 
>>>> terminology and potential alternatives to problematic terms to IETF 
>>>> participants, in order to align its efforts with broader activities 
>>>> by the technology industry.
>>>>
>>>> Best,
>>>> -Mallory
>>>>
>>>> On Monday, March 29, 2021, Lars Eggert <lars@eggert.org 
>>>> <mailto:lars@eggert.org>> wrote:
>>>> Hi Mallory,
>>>>
>>>> thanks for the feedback!
>>>>
>>>> On 2021-3-26, at 19:11, Mallory Knodel <mknodel@cdt.org 
>>>> <mailto:mknodel@cdt.org>> wrote:
>>>>> 2) Acknowledge that in some cases it will make sense for the IETF 
>>>>> to be the authority on certain terminology as it relates to the 
>>>>> IETF mandate, whereas others will need to be external given the 
>>>>> mandates of other bodies. In other words, I don't think the IETF 
>>>>> should abdicate all of its responsibility for setting standards 
>>>>> with the best terminology, as it sees fit.
>>>> Could you make a suggestion for what text changes you'd like to see 
>>>> to address this?
>>>>
>>>> Thanks,
>>>> Lars
>>>>
>>>>
>>>>
>>>> -- 
>>>> Mallory Knodel
>>>> CTO, Center for Democracy and Technology
>>>> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>>>>
>>>>
>> -- 
>> Mallory Knodel
>> CTO, Center for Democracy and Technology
>> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>>
>> -- 
>> Terminology mailing list
>> Terminology@ietf.org <mailto:Terminology@ietf.org>
>> https://www.ietf.org/mailman/listinfo/terminology
>
-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780