Extend the set of attribute value types

CHANGELOG.md

@@ -48,6 +48,8 @@ release.
   ([#4560](https://github.com/open-telemetry/opentelemetry-specification/pull/4560))
 - ⚠️ **IMPORTANT**: Extending the set of standard attribute value types is no longer a breaking change.
   ([#4614](https://github.com/open-telemetry/opentelemetry-specification/pull/4614))
+- Extend the set of attribute value types to support more complex data structures.
+  ([#4651](https://github.com/open-telemetry/opentelemetry-specification/pull/4651))
 
 ### OTEPs
 

oteps/4485-extending-attributes-to-support-complex-values.md

@@ -94,7 +94,7 @@ extending the standard attributes provides a more seamless and user-friendly API
 
 Currently, the SDK specification has a clause that says extending
 the set of standard attribute would be
-[considered a breaking change](/specification/common/README.md#standard-attribute).
+[considered a breaking change](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.44.0/specification/common/README.md#standard-attribute).
 
 We believe that removing this clause and extending standard
 attributes can be done gracefully across the OpenTelemetry ecosystem
@@ -123,24 +123,7 @@ Existing APIs that create or add attributes will be extended to support
 It's RECOMMENDED to expose an `AnyValue` type - the API representing complex or
 simple attribute value for type checking, ergonomics, and performance reasons.
 
-Exposing multiple types of attribute sets is NOT RECOMMENDED, such as having "ExtendedAttributes" in addition to "Attributes".
-
-OTel API MUST support setting complex attributes on spans, logs, profiles,
-span links, and as descriptive entity attributes.
-
-OTel API MAY support setting complex attributes on metrics, resources,
-instrumentation scope, span events, and as identifying entity attributes.
-
-> [!NOTE]
-> "MAY" is used here instead of "MUST" to give flexibility to dynamically
-> typed language APIs since there are no concrete use cases at this time
-> requiring complex attributes in these areas.
->
-> Most likely statically typed languages will choose to support
-> setting complex attributes uniformly everywhere.
->
-> This requirement level could change from "MAY" to "MUST" in the future
-> if we uncover use cases for complex attributes in these areas.
+OTel API MUST support setting complex attributes.
 
 API documentation and spec language around complex attributes SHOULD include
 language similar to this:
@@ -152,22 +135,7 @@ language similar to this:
 
 ### SDK
 
-OTel SDK MUST support setting complex attributes on spans, logs, profiles,
-span links, and as descriptive entity attributes.
-
-OTel SDK MAY support setting complex attributes on metrics, exemplars, resources,
-instrumentation scope, span events, and as identifying entity attributes.
-
-> [!NOTE]
-> "MAY" is used here instead of "MUST" to give flexibility to dynamically
-> typed language SDKs since there are no concrete use cases at this time
-> requiring complex attributes in these areas.
->
-> Most likely statically typed languages will choose to support
-> setting complex attributes uniformly everywhere.
->
-> This requirement level could change from "MAY" to "MUST" in the future
-> if we uncover use cases for complex attributes in these areas.
+OTel SDK MUST support setting complex attributes.
 
 The SDK MUST support reading and modifying complex attributes during processing
 whenever they are allowed on the API surface.

oteps/entities/0256-entities-data-model.md

@@ -139,7 +139,7 @@ MAY change over the lifetime of the entity. MAY be empty. These
 attributes are not part of entity's identity.
 <p>
 Follows <a
-href="../../specification/logs/data-model.md#type-any">any</a>
+href="https://github.com/open-telemetry/opentelemetry-specification/blob/v1.44.0/specification/logs/data-model.md#type-any">any</a>
 value definition in the OpenTelemetry spec - it can be a scalar value,
 byte array, an array or map of values. Arbitrary deep nesting of values
 for arrays and maps is allowed.
@@ -682,7 +682,7 @@ There are a couple of reasons:
 ### Attribute Data Type
 
 The data model requires the Attributes field to use the extended
-[any](../../specification/logs/data-model.md#type-any)
+[any](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.44.0/specification/logs/data-model.md#type-any)
 attribute values, that allows more complex data types. This is different from the data
 type used by the Id field, which is more restricted in the shape.
 

spec-compliance-matrix.md

@@ -199,7 +199,6 @@ Disclaimer: this list of features is still a work in progress, please refer to t
 | LoggerProvider.Shutdown |  |  | + |  | + | + |  | + |  | + | - |  |
 | LoggerProvider.ForceFlush |  |  | + |  | + | + |  | + |  | + | - |  |
 | Logger.Emit(LogRecord) |  |  | + |  | + | + |  | + |  | + | - |  |
-| Reuse Standard Attributes | X | + |  |  |  |  |  |  |  |  |  |  |
 | LogRecord.Set EventName |  | + |  |  |  |  |  |  | + | + |  |  |
 | Logger.Enabled | X | + |  |  |  |  |  | + | + | + |  |  |
 | SimpleLogRecordProcessor |  |  | + |  | + | + |  | + |  | + |  |  |

spec-compliance-matrix/cpp.yaml

@@ -357,8 +357,6 @@ sections:
         status: '+'
       - name: Logger.Emit(LogRecord)
         status: '+'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '+'
       - name: Logger.Enabled

spec-compliance-matrix/dotnet.yaml

@@ -357,8 +357,6 @@ sections:
         status: '-'
       - name: Logger.Emit(LogRecord)
         status: '-'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/erlang.yaml

@@ -357,8 +357,6 @@ sections:
         status: '?'
       - name: Logger.Emit(LogRecord)
         status: '?'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/go.yaml

@@ -357,8 +357,6 @@ sections:
         status: '?'
       - name: Logger.Emit(LogRecord)
         status: '?'
-      - name: Reuse Standard Attributes
-        status: '+'
       - name: LogRecord.Set EventName
         status: '+'
       - name: Logger.Enabled

spec-compliance-matrix/java.yaml

@@ -357,8 +357,6 @@ sections:
         status: '+'
       - name: Logger.Emit(LogRecord)
         status: '+'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/js.yaml

@@ -357,8 +357,6 @@ sections:
         status: '?'
       - name: Logger.Emit(LogRecord)
         status: '?'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/php.yaml

@@ -357,8 +357,6 @@ sections:
         status: '+'
       - name: Logger.Emit(LogRecord)
         status: '+'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/python.yaml

@@ -357,8 +357,6 @@ sections:
         status: '+'
       - name: Logger.Emit(LogRecord)
         status: '+'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/ruby.yaml

@@ -357,8 +357,6 @@ sections:
         status: '+'
       - name: Logger.Emit(LogRecord)
         status: '+'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/rust.yaml

@@ -357,8 +357,6 @@ sections:
         status: '?'
       - name: Logger.Emit(LogRecord)
         status: '?'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '+'
       - name: Logger.Enabled

spec-compliance-matrix/swift.yaml

@@ -357,8 +357,6 @@ sections:
         status: '?'
       - name: Logger.Emit(LogRecord)
         status: '?'
-      - name: Reuse Standard Attributes
-        status: '?'
       - name: LogRecord.Set EventName
         status: '?'
       - name: Logger.Enabled

spec-compliance-matrix/template.yaml

@@ -234,8 +234,6 @@ sections:
       - name: LoggerProvider.Shutdown
       - name: LoggerProvider.ForceFlush
       - name: Logger.Emit(LogRecord)
-      - name: Reuse Standard Attributes
-        optional: true
       - name: LogRecord.Set EventName
       - name: Logger.Enabled
         optional: true