You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OTel spec does not even have the "Members" and "Property" distinction reflecting W3C definitions. I would even say that the OTel spec "properties" reflects "members" in W3C which makes it very confusing.
If for some reason it is intended to NOT handle properties (also known as metadata) like in W3C then it would be good to call it out in the specification.
Discussed in the 4/2/24 Spec SIG meeting and determined we ought to improve the spec. We currently do mention properties / metadata, but only for the Set Value operation, and we only mention that it is an opaque value. We should:
Expand the API to add getters for accessing properties / metadata
Add helper functions so that properties / metadata isn't opaque. I.e. give helpers for reading / writing multiple entries.
pellared
changed the title
Baggage API: Define "properties" from W3C
Baggage API: Expand the API to add getters for accessing metadata
Apr 2, 2024
CC @open-telemetry/dotnet-approvers @open-telemetry/python-approvers @open-telemetry/cpp-approvers (as the API does not even accept the metadata)
pellared
changed the title
Baggage API: Expand the API to add getters for accessing metadata
Baggage API: Expand the API for accessing metadata
Apr 2, 2024
What are you trying to achieve?
The OTel spec does not even have the "Members" and "Property" distinction reflecting W3C definitions. I would even say that the OTel spec "properties" reflects "members" in W3C which makes it very confusing.
If for some reason it is intended to NOT handle properties (also known as metadata) like in W3C then it would be good to call it out in the specification.
Additional context.
Related PR: open-telemetry/opentelemetry-go#5132 (comment)
The text was updated successfully, but these errors were encountered: