Hi All, Regarding the below point, I disagree that “traditional” is the clearest option. I noticed this during my earlier review, but didn’t have a better option to offer. It now occurs to me that “past” works, and may age better, too.
I need to give a little more thought to “native”. I also noticed that during my review, but at the time I elected to pass over it because the past work that led to this document already used the term, and the term is so deeply embedded in the document itself. (On the other hand, “traditional” is only used once.) —John > On Mar 3, 2025, at 10:50 PM, Aijun Wang <wangai...@tsinghua.org.cn> wrote: > > 22) <!-- [rfced] Please review the "Inclusive Language" portion of the online > Style Guide > <https://urldefense.com/v3/__https://www.rfc-editor.org/styleguide/part2/*inclusive_language__;Iw!!NEt6yMaO-gk!DqpnPk3V7idH3H-750alGYS2sPJULmOJu1OFdLx6XRjm5-MIzg472RGtwH2MPQWLYqV07Jw7kjSTgS4S-Ohxeg$ > > > and let us know if any changes are needed. Updates of this nature typically > result in more precise language, which is helpful for readers. > > For example, please consider whether the following should be updated: > - traditional > - native > -->[WAJ] There is no other more suitable words to have the similar meaning of > the "traditional", "native" word. The recommended words in > https://urldefense.com/v3/__https://web.archive.org/web/20250214092458/https:/*www.nist.gov/nist-research-library/nist-technical-series-publications-author-instructions*table1__;LyM!!NEt6yMaO-gk!DqpnPk3V7idH3H-750alGYS2sPJULmOJu1OFdLx6XRjm5-MIzg472RGtwH2MPQWLYqV07Jw7kjSTgS7HmHKonQ$ > is more difficult for the readers. Let's keep it then? And we should notice > that in cloud area, the "cloud native" has been widely accepted. -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
