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

Mallory Knodel <mknodel@cdt.org> Tue, 30 March 2021 20:55 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 E42273A0CB1 for <terminology@ietfa.amsl.com>; Tue, 30 Mar 2021 13:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 EX4_U80aW0DF for <terminology@ietfa.amsl.com>; Tue, 30 Mar 2021 13:55:17 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 3EF583A0CB7 for <terminology@ietf.org>; Tue, 30 Mar 2021 13:55:17 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id kr3-20020a17090b4903b02900c096fc01deso80960pjb.4 for <terminology@ietf.org>; Tue, 30 Mar 2021 13:55:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TSPydt/8CrDrdistQ/Oe15ST6mi8gQ9L9TllO/J32Kg=; b=DJInEomEiqQgStaSYixCB0CXtgla8RTMKiwVIVqgvd6FS7+V3nyiyGihQwHTB/DhSo xUQhNqP4tSr4HUxwUK6y4hNrOB+l1HdxSMwzktUbdNFVtEnPI0ZUzo7HvoJ0G7Pu+4gE Uq6w8S7Q1DcNcO8li4n3mTXFX2TwuM5pbHTZg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TSPydt/8CrDrdistQ/Oe15ST6mi8gQ9L9TllO/J32Kg=; b=AP9plQA/J6RovhXkjZptiAiR6WTvKxBlydZwML6PfxorvRSoSWoCQ5jJJE3tCSSaoJ QY1z+tc8ZP85zTrKlCdml9xYAEwVUOF0OUwrBfgiziQIpq7FEk+jjAsXU+RKhWaV/1cV efxoxcVOUfZ/VucUMRPHtIzVFWaQVxTV0v1zNKPScpUUT5wJm5ECGcqTLjJeDewipMWA sGZqIWGu10MgP3XMEwWb7FjXEj7H6ippa+4+dLUZRwDvdQfYoR/VjmevQ2X4cemWCI67 mUiVzxwPELH3O+uDgprjNRCfR0KKqmjdUSdyOVwqGLj23mSw640gG3kMeIs6C5ccZ0YI ha7Q==
X-Gm-Message-State: AOAM532QpWu4sW/3Hms4DiRuXacfZrHU/iU7LHvA1drwmU29rAqLo7QI kYtARlFf1o9xepQT/I62YkxYfG/h3j9khpsk8/Uq1w==
X-Google-Smtp-Source: ABdhPJzpso+Dge8J+4JD9DT63XnHtpbzvy93sXwLW0bYFNBfEexX5mtggP65EW7QraatIT+cnXttk5u4TETy+dAwcmA=
X-Received: by 2002:a17:902:7fc8:b029:e4:32af:32da with SMTP id t8-20020a1709027fc8b02900e432af32damr194240plb.24.1617137715022; Tue, 30 Mar 2021 13:55:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a05:6a10:40ce:0:0:0:0 with HTTP; Tue, 30 Mar 2021 13:55:14 -0700 (PDT)
In-Reply-To: <3E83A93B-2AD3-497B-B40E-EC2E0C4E2711@eggert.org>
References: <161677836041.26846.148884814967107510@ietfa.amsl.com> <0b747dd8-f4f5-23a1-d09d-91ea30f525a7@cdt.org> <3E83A93B-2AD3-497B-B40E-EC2E0C4E2711@eggert.org>
From: Mallory Knodel <mknodel@cdt.org>
Date: Tue, 30 Mar 2021 16:55:14 -0400
Message-ID: <CAGVFjMJaYjroPLL5-Ns50CeyAB33thH5HpLgh0EXxPmxob4CEg@mail.gmail.com>
To: Lars Eggert <lars@eggert.org>
Cc: The IESG <iesg@ietf.org>, "terminology@ietf.org" <terminology@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000ea78605bec73711"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/xucIOeBr_phGUroFada4RdGWOXU>
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, 30 Mar 2021 20:55:22 -0000

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> wrote:

> Hi Mallory,
>
> thanks for the feedback!
>
> On 2021-3-26, at 19:11, Mallory Knodel <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