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

Andrew Campling <andrew.campling@419.consulting> Fri, 23 April 2021 15:32 UTC

Return-Path: <andrew.campling@419.consulting>
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 A3F4E3A127E for <terminology@ietfa.amsl.com>; Fri, 23 Apr 2021 08:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netorgft5189650.onmicrosoft.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 wKsXoGV5WOCQ for <terminology@ietfa.amsl.com>; Fri, 23 Apr 2021 08:32:06 -0700 (PDT)
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (mail-eopbgr110055.outbound.protection.outlook.com [40.107.11.55]) (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 C3CC43A1275 for <terminology@ietf.org>; Fri, 23 Apr 2021 08:32:05 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=k2oZob5rk37gYBlWdOsrjzIGJeeo6fjX5RXh17q//lbBOXUep225+pMRMfiPYRBOfS+vLz2X8pvuoYXHSnr9N7qE/eyi8f/QrpJZX1PizNT0onrYcXfhwjgwZCGAJi2+3auaYzGTgm9Bx4qBzNjArBhnRQIfYWSlFY7crHXkgejDqPtuGaM4TQbd2rXvOdRJwVikGdDzmL7S1u5pi9rvB6A6ZQMSseFjXsJOVeV4ON9TBX8Xz1MW4Eq51ST1C9AAZRhB9qf6/bthL2KaAzXdQxHRTFralEuQrl0+8ktWVvlLm7c0Gt37HToXiWbJ4ZrMJN3/nJSnKNzclF1sg3SSjA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KMbWZUwdYURZRZTdZkKABfauwNdbmNkh1LpP6uTFDeE=; b=iQx6jp82IrSmMOp///ppugtHH7dyj0EROmaDeAgUtjP4Uf0YcnPZywjH7t095eLHXvvOIfQqLgHmFgsw9cvfBCL+8UfgHK2Hb6ca9g+3wPWyghA25MtUKnw0JIcfP6ZPPBaZPgUK0wrA8slp9RbX+UKKojmDvFTf3LOqrbSB2tksHo8tMtoJZxN3lTr3pipCiHeqzi6W5rf8CyytMb5QwAolCAhSs3RTXQH2BPRRIWOJzf/iu7NzfyqlGMpFe27oLo2yj/Z6Igq8zTGo6rUhlQJmF0XJWbmDvnWnp4gd2Z2DN3ggkSLOQP3KHgvf78BuqTZJ6VYaxsMvgsMaoJKxaw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=419.consulting; dmarc=pass action=none header.from=419.consulting; dkim=pass header.d=419.consulting; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT5189650.onmicrosoft.com; s=selector1-NETORGFT5189650-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KMbWZUwdYURZRZTdZkKABfauwNdbmNkh1LpP6uTFDeE=; b=CHg0bHPmnaW5H7lbMPXVFxPISnvNsaws/QGMWk5puP6PQUxyH4nVlaOR/Lq2+3yhxInRC67f8aWnG67Pae/XLpHAkg3y0MTluNSduQj9Z9nWz3gYSx9cU7loNd9ldRLUrOsSyIZ4g9n3rJ+c+Ytpbnb9V9BiVGFlUnXYvtpBAeo=
Received: from LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:67::18) by LO2P265MB0575.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:64::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.22; Fri, 23 Apr 2021 15:32:02 +0000
Received: from LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM ([fe80::3cdc:773c:a0:88f7]) by LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM ([fe80::3cdc:773c:a0:88f7%6]) with mapi id 15.20.4042.024; Fri, 23 Apr 2021 15:32:02 +0000
From: Andrew Campling <andrew.campling@419.consulting>
To: "terminology@ietf.org" <terminology@ietf.org>
CC: "lars@eggert.org" <lars@eggert.org>
Thread-Topic: [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)
Thread-Index: AQHXOFHRmDKEbCj7A0mWXchNBhaLKqrCN7yw
Date: Fri, 23 Apr 2021 15:32:02 +0000
Message-ID: <LO2P265MB039970E083D941777895E46BC2459@LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM>
References: <161918836800.7390.6996403788262551415@ietfa.amsl.com> <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org>
In-Reply-To: <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=419.consulting;
x-originating-ip: [86.144.96.8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 145573f5-3906-4fcb-d254-08d9066cf197
x-ms-traffictypediagnostic: LO2P265MB0575:
x-microsoft-antispam-prvs: <LO2P265MB05758EE9617C29149149035BC2459@LO2P265MB0575.GBRP265.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: GIIAA0KFW29AQgIm+uE5w3g4bdx41IzOPzrC39jSW8YcE3gHTUFXhFNulH+Vr7tC4H69ac+jdYre6DLHa7bIpP4ANt5wKANNe9NEmaPamtgx6El+UlYUuxEzz+OLrkRqtd8i0xgMj+AIhl+06RaBJZr42HdTigbXrufy+LvA5MgTQiV5HCmEWQC3Mz59bzi57jfUE0nEbccsRgMJpg3YmhTJc5VN2Bqtf6ittUayfSQ4VLTfqN+teDEfZXmBu8bp1y4SJO9wFSy2OQ09g8NLXF5ylnO5uK9Ye+eciA0pA6m4DrKdW8mneqQ+NYAX5C9U2FUi7s0qNt0chRkU/9mBBmeArDg3V2C24D9nAoib5/LqY+4hPw9ZQOGlb0jlzSfoq+oPNguLpZLrJUw2UssXeSEgZcZddjyJljh+FRD/H5Ei3sdb0d9AhSmCcwuBqcgvzb+HEdyy3L4EuOGZiSEjG2eExWTEuPqiNpzTJZYiH9mMfS97EIj1QWvbsJHgbwWgtthRCyGmNE9113MVNqANCRtoZXkAXL+fRsPrTJQCRm+5Z/gc+gL3Mv8vdSjXlRZzKSyH7UO5Y/rOk57khjMSkWa0xKCjpqZFefXAHf8rdkHyiMt+4Z/CZm73OyBgISzhyHETurSrSk+jyM1lN4RfIFU5SJu4UoGJoUpfpMT6IElamr335m0Qa4wsLNpzCwKT6eGGQYbobxzHNdlGd+GwyfXfJzvCysm5t0cU8lcnc2k=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(346002)(396003)(366004)(376002)(39830400003)(136003)(316002)(66946007)(26005)(66446008)(166002)(71200400001)(5660300002)(64756008)(66476007)(478600001)(33656002)(9686003)(8676002)(66556008)(6916009)(55016002)(44832011)(186003)(52536014)(83380400001)(4326008)(6506007)(7696005)(2906002)(86362001)(76116006)(8936002)(66574015)(38100700002)(53546011)(122000001)(966005)(46492009); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: d2HESZsejASvGwbl1Jm3bKSzB7KRbnGE8sgdg62ZK5jyYZ/B2PvICzZlWcJc2I0Mr05ILFC5GCmU4H3M/T7u9ojvgbmUs+z4P4St3wqT6EVUMHkatMNvFWeKq7E0LqLO0L9LLvof/1TF+nWMjfXp/XjapuXaxXJQgoMP4LvUHOUk4GuHq6FaMsiZlk++RWS9BmDMPnlERMYybfhfJZHOT7UMiAGMQkwTKMNymDayHDNBifxoSgiRTpDVgiwz1Q2dHRaxGDDY9/S8Yeq78f6AT/9MXnOMynxXlqIwljKDoOjwAOZe2B0NBi61pQH8QJ5lfTnrbW9Ll5Vqw9AbKCStRXsJnQah+ziX80HU9t6kn/EYGFXcV8qGQldltXlGDXN8Sh6L6Wlvsa7K1pho7LbgjMgGtZ1LbWEjnu62m58TCCyIz0MQtKXajqk8tug8bBRlnVnCxpjqxmcf+i/2lOeMOKLBK+wAGIeIM6dCZ9ApKCkZu162kQPlmP3cDpn/oyUaA+vtGCvKJS3iV9fAhR7X5Jro9Rip086hroB9HtUMI7tE5qTeLjSf+BIQwNk1cO6qILPPh/he99NMoAYIKTLaKyPuDLISVMmdK+yx3SDmxvDlNUhXFm1xJTPvulxDG9GVpyPpAQ39n0TOiO1igCrI782UHnCLnnCuGrfgfZbjgodky24sEga1+t8EOMFcxuc556xfRp7iyV7wZ/fidcINnfr38VDSyKAosEPXYvcGdgVH+llgMkg+H5UfSkyfIL6Xaff+Ipyst4xsjbPmFkpfJ00eNIt7gkegdT55qylU5CsFXd6PFgHCUGfF4LgPGZnHDHt3frzu4ENUVUJe54dcfMbzLxZwL6/AF896UBBSvLcfFyZEzpFOUThkRMRX23DGcwrVU2DTwcXLAbTJKZfT5OTy00vlPkAwu73To3INmljrKboEbUpqZYnuHc3ihinHXXkwmr3zABOEZfs0gESePDoKTqc0W+BKEnDLKkdrVL3ZMv/CQTt4Ocm7oA4h9gEPrcg8Y1cPT7ueMfQ5XjnsFJPl5Zk3XM4yXPyPAOK+p42otwWduvFvPDZ/K1HeJYkDXhAcsjs3q0GiIkdA0mlymWdRYIBB4Wg+C0EbHxwVDmmSv18bnrl7pP1hj0d6B5lGSJkQCjxFgrfMLb9scv5S+mRDg45nDoaAb32wzWd/zs4Ufd/FhRq8xRKgAkN5Q8uddwqK8Dxyzx+PHz6HCJ72WZs6MTrL5jW+G/hUG6pknGTpGwIa77ZvYTkxiA/t7Y3hfwwv1Wjn/VYusR8NDNDWmedjgQ/m1avUQHUNdP4LCpU=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LO2P265MB039970E083D941777895E46BC2459LO2P265MB0399GBRP_"
MIME-Version: 1.0
X-OriginatorOrg: 419.consulting
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 145573f5-3906-4fcb-d254-08d9066cf197
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Apr 2021 15:32:02.8769 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9c2ced3e-7522-4755-87dc-f983abc66ec3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /Djl4rN+mqrOH3dWpeiFRttTstVcNd1HkUdsgeGzKpLJc51aKT4OCAPL64iM4keEsAnf31EjpdjuB+c2v1CjnxV6FONhDooJ/jEDjXxRu8Q=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P265MB0575
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/jV0wg9JU_6SQSv7lXvRK1uDLAc0>
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 15:32:11 -0000

On 2021-04-23, at 15:43, Lars Eggert <lars@eggert.org<mailto:lars@eggert.org>> wrote:

>

>> The WG will

>> identify and recommend external, independently updated resources

>> 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.



I'd add ", including those for whom English is not their first language." I know that the language element is arguably implied by the existing text but I believe that it should be made explicit as some of the previous list contributions have included input from those of both different cultures and languages, however these inputs often appear to have been overlooked.  The WG will not succeed if it focuses solely on what are largely US-centric political sensitivities (important though these may be to their proponents).

Andrew

From: Lars Eggert <lars@eggert.org>
Sent: 23 April 2021 15:43
To: terminology@ietf.org
Cc: ietf@ietf.org; gendispatch@ietf.org
Subject: [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)

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
 Archive: https://mailarchive.ietf.org/arch/browse/terminology/

Group page: https://datatracker.ietf.org/group/term/

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