I develop and publish VS Code extensions targeting users of the InterSystems platforms. Occasionally an extension needs some support classes installed on the servers it works with. I propose establishing a naming convention for these classes, as follows:

1. First dot-piece of the package name should be vscode
2. Second dot-piece should be derived from the "publisher" property in the extension's package.json manifest, as follows:
   • If publisher is "intersystems-community" then use dc
   • Otherwise use the publisher string, transformed if necessary to conform to package-naming constraints (e.g. remove punctuation). Uppercase characters in the publisher string may be retained or folded to lowercase at the choice of the publisher, but the transformation should be applied consistently for all classes published by that publisher. For example, if the extension uses publisher ID Acme-Nadir their class names might begin vscode.AcmeNadir. or vscode.acmeNadir. or vscode.acmenadir.
3. Third dot-piece should be derived from the "name" property of the extension, using the same transform guidance as above.
4. Additional dot-pieces of the package name can be added at the choice of the extension author.
5. Classnames should follow the convention proposed by @Robert Barbiaux in this article, i.e. be upper camel case (aka Pascal case).

A case(!) for lowercase package names was made by @Evgeny Shvarov in his 2021 post at https://community.intersystems.com/post/naming-convention-objectscript-p...

Thanks all. I feel honoured to have been awarded a double first! I couldn't have done it without @Timothy Leavitt 's excellent Test Coverage Tool package. Many thanks Tim.