Clarification on what an Event is, and what the event.domain and event.name attributes represent

CHANGELOG.md

@@ -21,6 +21,8 @@ release.
 
 - Add environment variables for configuring the `BatchLogRecordProcessor`.
   ([#2785](https://github.com/open-telemetry/opentelemetry-specification/pull/2785))
+- Remove language around uniqueness of event names within a domain
+  ([#2848](https://github.com/open-telemetry/opentelemetry-specification/pull/2848))
 
 ### Resource
 

semantic_conventions/logs/events.yaml

@@ -12,7 +12,7 @@ groups:
         examples: ['click', 'exception']
       - id: domain
         brief: >
-          The domain identifies the context in which an event happened. An event name is unique only within a domain.
+          The domain identifies the context in which an event happened.
         type:
           allow_custom_values: true
           members:
@@ -27,6 +27,5 @@ groups:
               brief: 'Events from Kubernetes'
         requirement_level: required
         note: |
-          An `event.name` is supposed to be unique only in the context of an
-          `event.domain`, so this allows for two events in different domains to
-          have same `event.name`, yet be unrelated events.
+          Events across different domains may have same `event.name`, yet be
+          unrelated events.

specification/logs/semantic_conventions/events.md

@@ -11,11 +11,10 @@ event names.
 | Attribute  | Type | Description  | Examples  | Requirement Level |
 |---|---|---|---|---|
 | `event.name` | string | The name identifies the event. | `click`; `exception` | Required |
-| `event.domain` | string | The domain identifies the context in which an event happened. An event name is unique only within a domain. [1] | `browser` | Required |
+| `event.domain` | string | The domain identifies the context in which an event happened. [1] | `browser` | Required |
 
-**[1]:** An `event.name` is supposed to be unique only in the context of an
-`event.domain`, so this allows for two events in different domains to
-have same `event.name`, yet be unrelated events.
+**[1]:** Events across different domains may have same `event.name`, yet be
+unrelated events.
 
 `event.domain` has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.