[Terminology] Getting terminology wrong can result in serious business costs...
Phillip Hallam-Baker <phill@hallambaker.com> Sat, 30 July 2022 02:35 UTC
Return-Path: <hallam@gmail.com>
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 88E72C15C523 for <terminology@ietfa.amsl.com>; Fri, 29 Jul 2022 19:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.468
X-Spam-Level:
X-Spam-Status: No, score=0.468 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XCQQRKEQyh7X for <terminology@ietfa.amsl.com>; Fri, 29 Jul 2022 19:35:00 -0700 (PDT)
Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D41B8C15C529 for <terminology@ietf.org>; Fri, 29 Jul 2022 19:35:00 -0700 (PDT)
Received: by mail-ot1-f42.google.com with SMTP id z12-20020a056830128c00b0061c8168d3faso4475535otp.7 for <terminology@ietf.org>; Fri, 29 Jul 2022 19:35:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yF6TZWCxnehmgGWzjXFsSnIZ+BoJA7o+JumJtKcE/JU=; b=vwk8OZTiSgev1gK6lEVeML2QQyVROQdqLVP0xwfWI3hOOCJMS/duznopn712sLGXb0 dsexXTx3Ed65bOdOfT7DLeyC5O0E0FGG+0FiAVknHjwPXw2lCnP3YKgPmlZIMu1nZKI+ kNN3WnRD1ZxObpmg2uTN7KeiNn8mfkZ64XX2yGcXBNLQ+uaCu1Jki3/UG5AqMNnlIubq l4Buw+z3Q6rVt9TpnZj+C2TCbtbpblXb/DlUyCI0u0oYpLBntMVEsBlWuHopvZD9XjpV TOTNNH5J2pMsww1MdqnQJz4I9ux/urIq6kWWHXksXOceoPkeVOzILxtD3PCGojhMLe0A ve7g==
X-Gm-Message-State: AJIora9yxFxtCbfpc7008CrgVZsmsUTm0zZ3OLxrqzCcjIJT65dznR2B LMbL/Zmr0UBu4YNeiZ08fNwut+I/qKNBhqEcOj2qtpbVjr/mrA==
X-Google-Smtp-Source: AGRyM1sSXQ+0Uq42PDa0tg1MmFQVDVJMc238gYloYfYflmIOvdVNjnFwwz1olRNMwFUoOP8saI3CRDVRDpGUXKU1cWU=
X-Received: by 2002:a05:6830:34a6:b0:61c:a7e8:e59b with SMTP id c38-20020a05683034a600b0061ca7e8e59bmr2557164otu.194.1659148499622; Fri, 29 Jul 2022 19:34:59 -0700 (PDT)
MIME-Version: 1.0
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 29 Jul 2022 22:34:48 -0400
Message-ID: <CAMm+Lwjv4R8k1p3J6ukxxDmdedOVHbMj0=G24yPdmdQaZTnBgQ@mail.gmail.com>
To: terminology@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f3210705e4fc9cbb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/yMOVZeykLljs4Atl_uFZYXOx-Zg>
Subject: [Terminology] Getting terminology wrong can result in serious business costs...
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 30 Jul 2022 02:35:01 -0000
Incident from the UK, TSB is a very large bank there. I am not sure that we discussed the risk that bad language choices leak through into the user experience but we clearly should. "So apparently the TSB banking app is failing, and users are being presented with an error message “Not enough good slaves” - which, to non-technical users, is unexpected." https://twitter.com/gwire/status/1552956857102340100
- [Terminology] Getting terminology wrong can resul… Phillip Hallam-Baker
- Re: [Terminology] Getting terminology wrong can r… Mallory Knodel
- Re: [Terminology] Getting terminology wrong can r… Bron Gondwana