move event attributes to the registry

docs/attributes-registry/events.md

@@ -0,0 +1,25 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: Events
+aliases: [docs/specs/semconv/general/events-general]
+--->
+
+# Semantic Conventions for Event Attributes
+
+<!-- semconv registry.event -->
+| Attribute  | Type | Description  | Examples  | Requirement Level |
+|---|---|---|---|---|
+| `event.domain` | string | The domain identifies the business context for the events. [1] | `browser` | Recommended |
+| `event.name` | string | The name identifies the event. | `click`; `exception` | Recommended |
+
+**[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.
+
+| Value  | Description |
+|---|---|
+| `browser` | Events from browser apps |
+| `device` | Events from mobile apps |
+| `k8s` | Events from Kubernetes |
+<!-- endsemconv -->
+
+[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/document-status.md

docs/general/events.md

@@ -43,18 +43,10 @@ that identify the class of Events but not the instance of the Event.
 <!-- semconv event -->
 | Attribute  | Type | Description  | Examples  | Requirement Level |
 |---|---|---|---|---|
-| `event.domain` | string | The domain identifies the business context for the events. [1] | `browser` | Required |
-| `event.name` | string | The name identifies the event. | `click`; `exception` | Required |
+| [`event.domain`](../attributes-registry/events.md) | string | The domain identifies the business context for the events. [1] | `browser` | Required |
+| [`event.name`](../attributes-registry/events.md) | string | The name identifies the event. | `click`; `exception` | Required |
 
 **[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.
-
-| Value  | Description |
-|---|---|
-| `browser` | Events from browser apps |
-| `device` | Events from mobile apps |
-| `k8s` | Events from Kubernetes |
 <!-- endsemconv -->
 
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/document-status.md

model/logs/events.yaml

@@ -5,28 +5,7 @@ groups:
     brief: >
         This document defines attributes for Events represented using Log Records.
     attributes:
-      - id: name
-        type: string
+      - ref: event.name
         requirement_level: required
-        brief: >
-          The name identifies the event.
-        examples: ['click', 'exception']
-      - id: domain
-        brief: >
-          The domain identifies the business context for the events.
-        type:
-          allow_custom_values: true
-          members:
-            - id: browser
-              value: 'browser'
-              brief: 'Events from browser apps'
-            - id: device
-              value: 'device'
-              brief: 'Events from mobile apps'
-            - id: k8s
-              value: 'k8s'
-              brief: 'Events from Kubernetes'
+      - ref: event.domain
         requirement_level: required
-        note: >
-          Events across different domains may have same `event.name`, yet be
-          unrelated events.

model/registry/events.yaml

@@ -0,0 +1,30 @@
+groups:
+  - id: registry.event
+    type: attribute_group
+    prefix: event
+    brief: >
+        This document defines attributes for Events represented using Log Records.
+    attributes:
+      - id: name
+        type: string
+        brief: >
+          The name identifies the event.
+        examples: ['click', 'exception']
+      - id: domain
+        brief: >
+          The domain identifies the business context for the events.
+        type:
+          allow_custom_values: true
+          members:
+            - id: browser
+              value: 'browser'
+              brief: 'Events from browser apps'
+            - id: device
+              value: 'device'
+              brief: 'Events from mobile apps'
+            - id: k8s
+              value: 'k8s'
+              brief: 'Events from Kubernetes'
+        note: >
+          Events across different domains may have same `event.name`, yet be
+          unrelated events.