Re: [Rats] [rfc-i] document conventions around Capitalization of Terminology

Henning Schulzrinne <hgs@cs.columbia.edu> Wed, 14 April 2021 14:19 UTC

Return-Path: <hgs10@columbia.edu>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E46763A0D00 for <rats@ietfa.amsl.com>; Wed, 14 Apr 2021 07:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level:
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=columbia.edu
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 igUC0yMsFb-I for <rats@ietfa.amsl.com>; Wed, 14 Apr 2021 07:19:00 -0700 (PDT)
Received: from mx0a-00364e01.pphosted.com (mx0a-00364e01.pphosted.com [148.163.135.74]) (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 A1B0D3A0CFE for <rats@ietf.org>; Wed, 14 Apr 2021 07:19:00 -0700 (PDT)
Received: from pps.filterd (m0167069.ppops.net [127.0.0.1]) by mx0a-00364e01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 13EE5mM5021881 for <rats@ietf.org>; Wed, 14 Apr 2021 10:19:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=columbia.edu; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=pps01; bh=7kaSj1xFZV2U/cdw1Wr8G+QSPzDh3If/Gx7KEb+/awM=; b=ABj4RBHNo1Mv9a8MSdYwyO1QFvbEfeBFIEELtzV4/qHAoPeAiz9BKBt8TCd2TlhxoIWQ WtxWsFx9o/kbrB+mi1YuCXL376Eb8yba5J3Vpwd5QsZACwrWUPVqRl6Qz2opP8eYDMe1 O7D4cIbyjc2qv2S2N+n3fA+tQyBwY9+bt+lYmlodHPLZIwgCfPCgk9JdqusDjWbqsOxX ZcLn1+Mt9Lv9AqbKxUXn3Gpd+IYrmLvtmJBGSLdUR1PZiEDuTSwQ6i/6vFsA2v+UwVRt yQizTHS+wQHzBfdP16HDZBjggj6xYbqn5mEQbQ2sdjMli9QELceDwSTApFfq1Z3WndRV fw==
Received: from sendprdmail22.cc.columbia.edu (sendprdmail22.cc.columbia.edu [128.59.72.24]) by mx0a-00364e01.pphosted.com with ESMTP id 37u51n9f6y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <rats@ietf.org>; Wed, 14 Apr 2021 10:19:00 -0400
Received: from mail-qk1-f199.google.com (mail-qk1-f199.google.com [209.85.222.199]) by sendprdmail22.cc.columbia.edu (8.14.7/8.14.4) with ESMTP id 13EEIvXx025922 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <rats@ietf.org>; Wed, 14 Apr 2021 10:18:58 -0400
Received: by mail-qk1-f199.google.com with SMTP id 14so12435260qkf.0 for <rats@ietf.org>; Wed, 14 Apr 2021 07:18:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7kaSj1xFZV2U/cdw1Wr8G+QSPzDh3If/Gx7KEb+/awM=; b=TMOpmvhq9jEP0uXJvNcpOhSfggmjA/fd5DxQfGGL2BpYfjp/0O43d3DhQ9gNbXp0Cv Z3dRp/U3tKj/FR4fFO1+xcumhpuHG7XkcMxrO5bRyTsjZbEtDGNUacyHEyTWJnULfr/1 cWFZINMfekxKYgekBCl/JdrNBt5lRrSn40aWg/EyH9yX2Wlx5zMbWZSoiFfzxVnfpFjM ljwrWTKndqeMbDtq2RTZeTvEXCGroPw/fbXUhYjZomFQxEEuzBdn175oT4Ks/GJKfjy7 q2TZXnj2ti7AzQ2yhXkJvXJqJHDthWzqat5Dt3RvZFTccGWZpb76d9ab9c/EAHpVwKU4 UajQ==
X-Gm-Message-State: AOAM532WidwlmzNZvmymgYGt0GzxY3TH6Is2uzpObnEHed2VvmcdQtw/ FOKo1bLPZDDIkjnNgn6337cqSTlOAiXZD5OuYG5smBrynB4fmHOK9IbnoeK0VMvHau5u+lmkHAX f78nXf0Bwe71i19Ns8S8let6PJcRD
X-Received: by 2002:a0c:c581:: with SMTP id a1mr38475506qvj.34.1618409937370; Wed, 14 Apr 2021 07:18:57 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJyfTWNeBJvrupVcAJb1axQ125r6Sdno9Lze29RXDO1oJ3t2TBG6mUnNxvVIul31e6NH6NjQSA9XcitcwlbMw+c=
X-Received: by 2002:a0c:c581:: with SMTP id a1mr38475479qvj.34.1618409936963; Wed, 14 Apr 2021 07:18:56 -0700 (PDT)
MIME-Version: 1.0
References: <10996.1618327990@localhost> <6076D58B.3030403@btconnect.com>
In-Reply-To: <6076D58B.3030403@btconnect.com>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Wed, 14 Apr 2021 10:18:30 -0400
Message-ID: <CACgrgBbOrAbGb=pSFPtSVTctCcSa3_=WHjt=Ja4CVJnyTRJO4g@mail.gmail.com>
To: tom petch <daedulus@btconnect.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, rats@ietf.org, rfc-interest <rfc-interest@rfc-editor.org>
Content-Type: multipart/alternative; boundary="00000000000064e10405bfef6db4"
X-Proofpoint-GUID: 92bZuf2FVCm0_uCUcnBK8WWSWJaG9Tei
X-Proofpoint-ORIG-GUID: 92bZuf2FVCm0_uCUcnBK8WWSWJaG9Tei
X-CU-OB: Yes
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-04-14_07:2021-04-14, 2021-04-14 signatures=0
X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 clxscore=1011 impostorscore=10 bulkscore=10 priorityscore=1501 mlxlogscore=909 adultscore=0 phishscore=0 mlxscore=0 spamscore=0 malwarescore=0 lowpriorityscore=10 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104140097
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/Sk9rqNkNQrzQO7Pmf7dw8Z28GDk>
Subject: Re: [Rats] [rfc-i] document conventions around Capitalization of Terminology
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote ATtestation procedureS <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 14:19:06 -0000

Capitalization of terms that are not proper names is often considered a bad
idea and bad style - this is English, not German, after all. Most standard
style guides in science and technology writing frown on this.

On Wed, Apr 14, 2021 at 7:44 AM tom petch <daedulus@btconnect.com> wrote:

> On 13/04/2021 16:33, Michael Richardson wrote:
> >
> > In the RATS Architecture document we have spent some time (maybe too much
> > time), making sure that if we define some Term, that it is consistently
> > rendered like a Proper Noun. That is capitalized.
> > There are some terms which have renderings in both capitalized (our
> > definition), and uncapitalized (not exactly our definition).
> >
> > In a document of mine (BRSKI) which has now entered AUTH48, the RPC has
> > lower-cased all our in-document defined terminology.  I was very
> surprised by this.
>
> If this happened to me, I would be more than suprised, I would be
> furious and wondering how to take my revenge:-)
>
> I looked at the Style Guide and page 6 has a section on Capitalization
> [sic] but it only covers titles, section headings and the like, nothing
> about using capitalisation in text to indicate a technical term, which
> for me is an essential part of making our output easier to understand.
>
> Tom Petch
>
> > I have asked to have that reversed, and I imagine that my wish will be
> granted.
> >
> > But, I am wondering about convention, and I wonder if there is some magic
> > keyphrase that needs to go into a Terminology Section such to indicate
> that
> > to the editors and the readers that we are following that convention.
> > Or if we should make up such a phrase.
> >
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT
> consulting )
> >             Sandelman Software Works Inc, Ottawa and Worldwide
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > rfc-interest mailing list
> > rfc-interest@rfc-editor.org
> > https://www.rfc-editor.org/mailman/listinfo/rfc-interest
> >
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>