[Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)

Nick Doty <npdoty@ischool.berkeley.edu> Thu, 29 April 2021 19:45 UTC

Return-Path: <npdoty@berkeley.edu>
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 6A7E73A097B for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 12:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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 (2048-bit key) header.d=ischool-berkeley-edu.20150623.gappssmtp.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 N8iPasFUQGv4 for <terminology@ietfa.amsl.com>; Thu, 29 Apr 2021 12:45:32 -0700 (PDT)
Received: from mail-pf1-x442.google.com (mail-pf1-x442.google.com [IPv6:2607:f8b0:4864:20::442]) (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 A79943A096C for <terminology@ietf.org>; Thu, 29 Apr 2021 12:45:32 -0700 (PDT)
Received: by mail-pf1-x442.google.com with SMTP id c17so12229892pfn.6 for <terminology@ietf.org>; Thu, 29 Apr 2021 12:45:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ischool-berkeley-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=AjQ8fBRxVhf5WYiV5qEBiYhLe4b+aGwBQdiwMc3/aeM=; b=Pq1XdbwCmCezoMfengqmGEGYMmfT9jxDGOhuU7MrdiLdUkxYMy1qti4bv4cmcs6+wW haO0Om/LBEphr0BbTlhMkw6TZ1VcjtlTANni2tNYgMjJRS5QwdySpjdh/9CqreUWN7xf WJ9Qou8aE1bOSSagD78iFqdX0Ru15dunnZCVwUHJxuOIcgPaLhsP0Knko7fKIv4YLR1C EWkBcs8wI4e7aUrnMJiCPPaiDvT814yLGMSnvmoYA77l98YshPdI+1r4jGHRhavM0AeQ +mop3lZXI6kY9g3jSrUa2XMKbrOlwlVCU5e68sKmyEz/EMCUEKpJzks5rO+PvUHS1QCy GD0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AjQ8fBRxVhf5WYiV5qEBiYhLe4b+aGwBQdiwMc3/aeM=; b=KAB9KpF/Ma/KVBcRJEUL5LTaxtjHF0l0A6+w4tvdo8fd/EdmQrsA9T1rM1wGgdMg+w LE9VsYnBWK1VPgyn1yU7Bo25eVt/xusWF8Zzx3vghh+EPavHLPW97xQ0ulOKf10FYBfS GX30VzVmZZn9AfHZyJFmvyEu8PO5dJVld+fINh8kvZ2M87s2XB2NTVyIG3XvmGJ/R76t gXpxizaFf4HPkttp4iyDjrrYVJcnxRao+qdwMl36GAjBaVmJodYMDC0VCzj76qEiLjwi PANEVFHV6M8f/iXUsNFoO1jCnG0xqPTNbYDjXGNxnoCBn4ZSRKQoOfxJbXgqNvhNB5kG 9vrw==
X-Gm-Message-State: AOAM531Bp0bN3vYW9YD/JAN5vx37V31+5w8WsZvsetbpDlEl8KL2Amdp tudUva1iyGAk7ctfn/+BqLypV9QGUXwdh3RkuNoo8oqxjK4ZLvE9
X-Google-Smtp-Source: ABdhPJyFpOh6BWer8/OmJbcgdYX0Npp0SEnACUpWvLl2KBf1v1EMkjiN0ok9y9ejFzTjfWdQpAOMWWh5ZfWJZzML5qw=
X-Received: by 2002:a62:3344:0:b029:24c:735c:4546 with SMTP id z65-20020a6233440000b029024c735c4546mr1316085pfz.1.1619725531084; Thu, 29 Apr 2021 12:45:31 -0700 (PDT)
MIME-Version: 1.0
From: Nick Doty <npdoty@ischool.berkeley.edu>
Date: Thu, 29 Apr 2021 15:45:20 -0400
Message-ID: <CAFfrZstRpSrbc5X6OhPsAiiER1srh3aHEuS1sLYsghUJz4PO5g@mail.gmail.com>
To: terminology@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ea1d3105c121bcba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/w_OoUaF6GVIzQIMoLUlrc8xq_rk>
Subject: [Terminology] Guidance for NIST Staff on Using Inclusive Language in Documentary Standards (NISTIR 8366)
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 19:45:37 -0000

Today, NIST has published this Internal Report on "using inclusive
language" publicly, in part because it may be useful to other standards
groups interested in clarity and inclusiveness of terminology.

Blog post/announcement:
https://www.nist.gov/news-events/news/2021/04/nists-inclusive-language-guidance-aims-clarity-standards-publications

NISTIR 8366:
https://doi.org/10.6028/NIST.IR.8366

I think both the blog post and the report itself do a good job of
describing the particular goals, including some examples (but not
especially long lists), and pointing to other resources that might be
useful for writing standards that are clear and respectful to a wide range
of readers.

Hope this helps,
Nick