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

tom petch <daedulus@btconnect.com> Wed, 14 April 2021 11:44 UTC

Return-Path: <daedulus@btconnect.com>
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 75A543A07BE for <rats@ietfa.amsl.com>; Wed, 14 Apr 2021 04:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=btconnect.onmicrosoft.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 6RtJ4IzUuw9k for <rats@ietfa.amsl.com>; Wed, 14 Apr 2021 04:44:21 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04on0718.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0d::718]) (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 DDC213A07AE for <rats@ietf.org>; Wed, 14 Apr 2021 04:44:20 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CxoXHWfRQkiNDUnmELgCp4pRu7s7JeCT1U/eFFS38WvYEJNRXRkJFqy2cVIQ8Y2buP/LNgjILl35oBnU6rumCrDrVvat/2QjjJdDRLoFfUT+RjFHzDDZtjctABaJ4UhBY/aonsRYZNBuoJSmBqtRP0Rs9CTWm6mBvGokCtivr6M3K8wf333+KKn+XoILEB6033KeZ9GJarJcKlSjxIcNAsPawLKDFqW6EnWPEouKmL/oKYaX7NjPyXUf3EM66qewFEPUc/1L4paNKlRVkooOQ2R8sdnQc0g9r0NaSLZlpZvC1V+oUI08CWJRNfcPBZuSX+D9v5H88FIV3ZrS55GmOg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=i6shB+LUYbd81qw+PuGCi+Z76POYCvKv+1LsSTIEhig=; b=mag9O3Rk1DEgv3X5oHyePLLX0r+BlZ1QX2maMEIrDimlAq1hinUnVv9NSXpDLeoAJlSa1DXO7ZARkicdPTi2MVU9uMJAZ+fPABjmXBqASCf974UKVuy+wD3eAwgAf03+hL4jJ9v9uQTD73iByQab8Y1iTa8A+RLUfAT9PB5+JIO+BqdYEQPLRX2NpEGGH7MdkStvhGQ9PxXwrWKnrkadumTL0PjKkdp09N2Y0CzU2DHU0Qn4yOpCYNXFD68irb6C+HBUNDQc51ed+dK78XepbLmE04Q/NPOvrVQNEhvacvOWyD0GVoMHOBqXuRtFTNpJVOQArfi1FnTsn64I4mMgXA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=i6shB+LUYbd81qw+PuGCi+Z76POYCvKv+1LsSTIEhig=; b=WlALQD7Tb8JkWmPmBvTRBuCP4dpCQoDQP6qL4FBlsbNcDN2KFQ46vLxnUNIBEQahk6zTgiGF0YTFa3H0D5LhT3bwi7X7u4QN7yC9jQkuRlMf+4IQpHTQ1P4SQV8ayyELq1k5Mmwt+d1hnGzzA+/RcpfU9hXctCZgmxMI3zCXK/k=
Authentication-Results: rfc-editor.org; dkim=none (message not signed) header.d=none;rfc-editor.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB6270.eurprd07.prod.outlook.com (2603:10a6:800:139::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.6; Wed, 14 Apr 2021 11:44:17 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877%9]) with mapi id 15.20.4042.016; Wed, 14 Apr 2021 11:44:17 +0000
To: Michael Richardson <mcr+ietf@sandelman.ca>, rats@ietf.org, rfc-interest <rfc-interest@rfc-editor.org>
References: <10996.1618327990@localhost>
From: tom petch <daedulus@btconnect.com>
Message-ID: <6076D58B.3030403@btconnect.com>
Date: Wed, 14 Apr 2021 12:44:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <10996.1618327990@localhost>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.155.147.182]
X-ClientProxiedBy: LO4P123CA0303.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:196::20) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.155.147.182) by LO4P123CA0303.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:196::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4020.22 via Frontend Transport; Wed, 14 Apr 2021 11:44:17 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 8ce59758-e11e-4df5-44c5-08d8ff3aa2ac
X-MS-TrafficTypeDiagnostic: VI1PR07MB6270:
X-Microsoft-Antispam-PRVS: <VI1PR07MB62703BD5FE09D6953A5DEDE4C64E9@VI1PR07MB6270.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: fH8wMra/qhF6gz+aGHBWBlKSJJLGABvRtnlHWMbVFyH8b3TAgd9r9fLXPKEb7Zf5nieHpX9CxLrS65uSYL1RR2b40Kqd5BuN9XvSpik8oGmtRTCjf7SJ1lgU7aPYkRsR+NGLjs5gV/VCsyxggLbow96kY9bfYa3VhtEBKIFTyleIPQFp2ozcQFyxKXKCJsm7OXxyJ8TV1EQQFkE26RRTYAcY23shU9ag3uV0/Yw74iuQYg9AMUeI90XpsdWhFiCJYloewhTSxwHOcEGLSIl23DVOvCzc/5+Y9gx8xYRMsQBmYBpFb7QpkZVjNUFBWos4+/brh6r7aApihseZs1mxwzYkzMvHIUPFxMUZ6qm1uqXxBKA95wN4pV6JpKTv6teS2d24X2FrJKXHRt5vYuYa3xDdl4YamVQqv41VWsLQI77Zd9O0rBDskfIY7pNh4dzAcR0usRIH2zSqVqu4NtRkMNdtNF6tpIdVmeDyKHuC18R+NCDjUXa55+bZjQpfeO4YMaEA4PuR0lq1EepHhkJSPuhp9o4ArUiK847DgkbQ5kdKrBT31/3YjFcbWEyHE1++GDHJme1t5IGW3l+hHLaEvQ1sMAEjoeXV8bltefCz8yg3hHRpCDXVByBbsjd4Hu6G0Xz5ddl3UGUiUt+ll0UpNgm/UOrMm16H4wrqXZDBGJUloYlkz4Vq7+UTmCtBBiOs7QPH76vXXCsVrheTcWEOuHcaKDXr0zEt9TNV9SiEiR4=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(39860400002)(376002)(136003)(396003)(346002)(366004)(6666004)(8676002)(53546011)(52116002)(186003)(66476007)(5660300002)(66556008)(87266011)(26005)(16526019)(66946007)(38350700002)(478600001)(110136005)(8936002)(2616005)(966005)(2906002)(316002)(6486002)(33656002)(86362001)(38100700002)(16576012)(956004)(36756003); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: =?Windows-1252?Q?g2OcUuCehzHNMe68i91tj4YhaI45KyX0oeIIkCj8olToXm+MozITov07?= =?Windows-1252?Q?6tEdvaQ6WA5HmSphDsuLSj/Ohf0O34ylaiEGf8JytN7uCTr6M9OvUD4M?= =?Windows-1252?Q?vYM9B79eFJHUUvCxVmB31jKh4eM0SaSDW+pvHL9GnbNC0bLN4m6IfqQ7?= =?Windows-1252?Q?XvFd5CyXdp/7cnEeQi1g1GRM+4w1dUHq1vBVcXVHZgwxWYChqWyZqVOD?= =?Windows-1252?Q?KhPZMNsbGQIO+S7oKd3ZLwBS/q6DvIj8zA4+GkO0IHLecVqQkZ9h4P17?= =?Windows-1252?Q?V0qGIVaCa1DxRytciILzjkZebGbPWcizx5/iqpo9Pu2IaNePiUJE4Jl6?= =?Windows-1252?Q?VWumwv3LL++ZnUVLMSmwerAe5u802wgGbvTfp2jJBsJRT9lt4bMnFkWj?= =?Windows-1252?Q?bCisELDoGvlWgvrwU+Qc5r3UQfMEF45s+5kcihjbubxrrsmUEzXU/B9G?= =?Windows-1252?Q?n8N1SddnuLEXjP2CRSxdo6Zr+gUnl/QLyEKy0uyWIfJZ/RpKA6inMxkS?= =?Windows-1252?Q?tWG6NGGLLa0hSVd6vfMV+IJBwQGJikEOmNP9b9zMAd0MrhVz7My+Ev2a?= =?Windows-1252?Q?wGawbJMXq4ymaks8XcS/CTDPEenc4A39d2aF12pFptObR1esIdCD3oUF?= =?Windows-1252?Q?sUQRV3y+kysXB/EC4h42DHRcWzLk+AogiSZlhbXHXa1rpwbxxE7blDx9?= =?Windows-1252?Q?XMSYBWBHCE06YLDYHM+2H1wXveeisRZaeBDRGvBHudFLUQ4NrQEd0pKn?= =?Windows-1252?Q?DkbOCx6oIqUi0JJ4ZEk+rAaw9C9m8ZNdD8RO425qpc1vkgvTLChgAnm2?= =?Windows-1252?Q?N3NxygRq6bPsWJTbxC9/+ehThKHVHXyGQY/IMHNumQw3ThGAXX9kl2M2?= =?Windows-1252?Q?BrNOZXpVInhPBhJUgRumyTjhgVWIh4JpSi1TUMGK6y/XFOqYiza0MU67?= =?Windows-1252?Q?4iObinRbdVnncYTKflo556p/nz9nOq05TRsNPTnVWLDYcYn1102WN5V/?= =?Windows-1252?Q?uZUyNpbRqj4Y3TunXe0LS8xMTQ08zGpNUGQCQe63KEXH1gU6dUrblYP6?= =?Windows-1252?Q?b/YndS4qkLlfJAgitSDw+QWOPPaYp+qGhZXTGwLvAaBqiSN+Y3IMoUzp?= =?Windows-1252?Q?djY818UPmtHU3EzD6hUELrIcbtDRTlT3U1QL4ol5zxCY9fjQzKb6nFaB?= =?Windows-1252?Q?sChsPagbKGN34oO5rRx2GXHzIw39VYsMf43rNF0GMMZWlJ0GpMmnWbFL?= =?Windows-1252?Q?eyg/Wvq76ujSSYqNXjJtRB15g66/e6gOWOuxrlP0koSKNkJf36MdyaUS?= =?Windows-1252?Q?tL4B5U6vImVce6JKZ3qcwuGWrI31mwKAKBopWmV5VwvYYmvckysSISFW?= =?Windows-1252?Q?8rv5vvhA73WT4Ho6C+rhAjIafSW7/bLAHwR2DaZ7JuHJ1ZDL7iexMyJ8?=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8ce59758-e11e-4df5-44c5-08d8ff3aa2ac
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Apr 2021 11:44:17.6604 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: jmpAGLUtcubgmwhrEAoCwToLtSlB/YZ//yz1b/lwv43chvJMO4xqN+DbafHkN6UOmn7K54qIp0taA5UJPCM+4w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB6270
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/WA4gpsJL5urWm4xswsOAiyGV9ic>
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 11:44:26 -0000

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
>