try registry inside domain

model/general/general.yaml

@@ -0,0 +1,119 @@
+groups:
+  - id: client
+    type: attribute_group
+    brief: >
+      General client attributes.
+    attributes:
+      - ref: client.address
+      - ref: client.port
+  - id: server
+    type: attribute_group
+    brief: >
+      General server attributes.
+    attributes:
+      - ref: server.address
+      - ref: server.port
+  - id: source
+    type: attribute_group
+    brief: >
+      General source attributes.
+    attributes:
+      - ref: source.address
+      - ref: source.port
+  - id: destination
+    type: attribute_group
+    brief: >
+      General destination attributes.
+    attributes:
+      - ref: destination.address
+      - ref: destination.port
+  - id: peer
+    type: attribute_group
+    brief: "Operations that access some remote service."
+    attributes:
+      - ref: peer.service
+        requirement_level: recommended
+  - id: identity
+    type: attribute_group
+    brief: >
+      These attributes may be used for any operation with an authenticated and/or authorized enduser.
+    attributes:
+      - ref: enduser.id
+        requirement_level: recommended
+      - ref: enduser.role
+        requirement_level: recommended
+      - ref: enduser.scope
+        requirement_level: recommended
+  - id: thread
+    type: attribute_group
+    brief: >
+      These attributes may be used for any operation to store information about a thread that started a span.
+    attributes:
+      - ref: thread.id
+      - ref: thread.name
+  - id: code
+    type: attribute_group
+    brief: >
+      These attributes allow to report this unit of code and therefore to provide more context about the span.
+    attributes:
+      - ref: code.function
+      - ref: code.namespace
+      - ref: code.filepath
+      - ref: code.lineno
+      - ref: code.column
+      - ref: code.stacktrace
+        requirement_level: opt_in
+  - id: url
+    brief: Attributes describing URL.
+    type: attribute_group
+    attributes:
+      - ref: url.scheme
+      - ref: url.full
+        tag: sensitive-information
+      - ref: url.path
+      - ref: url.query
+        tag: sensitive-information
+      - ref: url.fragment
+  - id: session-id
+    type: attribute_group
+    brief: >
+      Session is defined as the period of time encompassing all activities performed by the application and the actions
+      executed by the end user.
+
+      Consequently, a Session is represented as a collection of Logs, Events, and Spans emitted by the Client Application
+      throughout the Session's duration. Each Session is assigned a unique identifier, which is included as an attribute in
+      the Logs, Events, and Spans generated during the Session's lifecycle.
+
+      When a session reaches end of life, typically due to user inactivity or session timeout, a new session identifier
+      will be assigned. The previous session identifier may be provided by the instrumentation so that telemetry
+      backends can link the two sessions.
+    attributes:
+      - ref: session.id
+        requirement_level: opt_in
+      - ref: session.previous_id
+        requirement_level: opt_in
+  - id: network-core
+    type: attribute_group
+    brief: >
+      These attributes may be used for any network related operation.
+    attributes:
+      - ref: network.transport
+      - ref: network.type
+      - ref: network.protocol.name
+      - ref: network.protocol.version
+      - ref: network.peer.address
+      - ref: network.peer.port
+      - ref: network.local.address
+      - ref: network.local.port
+
+  - id: network-connection-and-carrier
+    type: attribute_group
+    brief: >
+      These attributes may be used for any network related operation.
+    attributes:
+      - ref: network.connection.type
+      - ref: network.connection.subtype
+      - ref: network.carrier.name
+      - ref: network.carrier.mcc
+      - ref: network.carrier.mnc
+      - ref: network.carrier.icc