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

[Christian Huitema <[e-mail]>]

On 4/29/2021 1:50 PM, Brian E Carpenter wrote:
> On 30-Apr-21 08:17, Keith Moore wrote:
>> On 4/29/21 3:45 PM, Nick Doty wrote:
>>> 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
>>> <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
>>> <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
>> I could _almost_ support just using this document, especially if it
>> would get IETF out of the business of trying to write its own.   Then we
>> could all just get back to work.
> Yes. The IESG could suggest to the RFC Editor team to add an informative
> reference to the NIST document to the style guide, and remind the IETF
> that Internet-Drafts should aim to adhere to the RFC style guide,
> and we're done.
>
> (Clearly NIST is not international in scope, and the IETF is, but since
> our shared working language is more or less American English, it seems
> reasonable.)

+1. One of the best ways to make progress quickly.

-- Christian Huitema