[chore] move event to registry (#907)

Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -35,6 +35,7 @@ body:
         - area:dns
         - area:enduser
         - area:error
+        - area:event
         - area:exception
         - area:faas
         - area:feature-flag

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -28,6 +28,7 @@ body:
         - area:dns
         - area:enduser
         - area:error
+        - area:event
         - area:exception
         - area:faas
         - area:feature-flag

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -37,6 +37,7 @@ body:
         - area:dns
         - area:enduser
         - area:error
+        - area:event
         - area:exception
         - area:faas
         - area:feature-flag

docs/attributes-registry/README.md

@@ -43,6 +43,7 @@ Currently, the following namespaces exist:
 * [Disk](disk.md)
 * [End user](enduser.md)
 * [Error](error.md)
+* [Event](event.md)
 * [Exception](exception.md)
 * [FaaS](faas.md)
 * [Feature Flag](feature-flag.md)

docs/attributes-registry/event.md

@@ -0,0 +1,15 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: Events
+--->
+
+# Event
+
+## Event Attributes
+
+<!-- semconv registry.event(omit_requirement_level) -->
+| Attribute  | Type | Description  | Examples  | Stability |
+|---|---|---|---|---|
+| `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+
+**[1]:** Event names are subject to the same rules as [attribute names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.31.0/specification/common/attribute-naming.md). Notably, event names are namespaced to avoid collisions and provide a clean separation of semantics for events in separate domains like browser, mobile, and kubernetes.
+<!-- endsemconv -->

docs/general/events.md

@@ -55,7 +55,7 @@ that identify the class of Events but not the instance of the Event.
 <!-- semconv event -->
 | Attribute  | Type | Description  | Examples  | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
 |---|---|---|---|---|---|
-| `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | `Required` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| [`event.name`](../attributes-registry/event.md) | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | `Required` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 
 **[1]:** Event names are subject to the same rules as [attribute names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.31.0/specification/common/attribute-naming.md). Notably, event names are namespaced to avoid collisions and provide a clean separation of semantics for events in separate domains like browser, mobile, and kubernetes.
 <!-- endsemconv -->

model/logs/events.yaml

@@ -1,19 +1,8 @@
 groups:
   - id: event
     type: attribute_group
-    prefix: event
     brief: >
         This document defines attributes for Events represented using Log Records.
     attributes:
-      - id: name
-        type: string
-        stability: experimental
+      - ref: event.name
         requirement_level: required
-        brief: >
-          Identifies the class / type of event.
-        note: >
-          Event names are subject to the same rules as [attribute names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.31.0/specification/common/attribute-naming.md).
-          Notably, event names are namespaced to avoid collisions and provide a clean
-          separation of semantics for events in separate domains like browser, mobile, and
-          kubernetes.
-        examples: ['browser.mouse.click', 'device.app.lifecycle']

model/registry/event.yaml

@@ -0,0 +1,18 @@
+groups:
+  - id: registry.event
+    prefix: event
+    type: attribute_group
+    brief: >
+      Attributes for Events represented using Log Records.
+    attributes:
+      - id: name
+        type: string
+        stability: experimental
+        brief: >
+          Identifies the class / type of event.
+        note: >
+          Event names are subject to the same rules as [attribute names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.31.0/specification/common/attribute-naming.md).
+          Notably, event names are namespaced to avoid collisions and provide a clean
+          separation of semantics for events in separate domains like browser, mobile, and
+          kubernetes.
+        examples: ['browser.mouse.click', 'device.app.lifecycle']