Add Log Bridge API artifact naming guidance (#3346)

Resolves #3301.

---------

Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>

CHANGELOG.md

@@ -34,6 +34,8 @@ release.
   ([#3331](https://github.com/open-telemetry/opentelemetry-specification/pull/3331))
 - Ensure Logs Bridge API doesn't contain SDK implementation details
   ([#3275](https://github.com/open-telemetry/opentelemetry-specification/pull/3275))
+- Add Log Bridge API artifact naming guidance
+  ([#3346](https://github.com/open-telemetry/opentelemetry-specification/pull/3346))
 - Add log appender / bridge to glossary.
   ([#3335](https://github.com/open-telemetry/opentelemetry-specification/pull/3335))
 

specification/logs/bridge-api.md

@@ -18,6 +18,7 @@
 - [LogRecord](#logrecord)
 - [Optional and required parameters](#optional-and-required-parameters)
 - [Concurrency requirements](#concurrency-requirements)
+- [Artifact Naming](#artifact-naming)
 - [Usage](#usage)
   * [How to Create a Log4J Log Appender](#how-to-create-a-log4j-log-appender)
   * [Implicit Context Injection](#implicit-context-injection)
@@ -158,6 +159,15 @@ specific guarantees and safeties.
 
 **Logger** - all methods are safe to be called concurrently.
 
+## Artifact Naming
+
+The Logs Bridge API is not intended to be called by application developers
+directly, and SHOULD include documentation that discourages direct use. However,
+in the event OpenTelemetry were to add a user facing API, the Logs Bridge API would
+be a natural starting point. Therefore, Log Bridge API artifact, package, and class
+names MUST NOT include the terms "bridge", "appender", or any other qualifier
+that would prevent evolution into a user facing API.
+
 ## Usage
 
 ### How to Create a Log4J Log Appender