-
Notifications
You must be signed in to change notification settings - Fork 931
Closed
Labels
area:data-modelFor issues related to data modelFor issues related to data modelarea:semantic-conventionsRelated to semantic conventionsRelated to semantic conventionsspec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec labelspec:resourceRelated to the specification/resource directoryRelated to the specification/resource directorytriage:accepted:readyReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsorReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
Description
We need to update: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md#semantic-conventions-stability
Right now this calls out which fields are considered "stable" for semantic conventions. However, the way resource is called out, and what semantic conventions can actually enforce are problematic.
With the addition of "entities" we'll be able to enforce stability on appropriate components within the SDK, we need to update the specification here once the data model specification is laid out.
See this comment
arminru
Metadata
Metadata
Assignees
Labels
area:data-modelFor issues related to data modelFor issues related to data modelarea:semantic-conventionsRelated to semantic conventionsRelated to semantic conventionsspec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec labelspec:resourceRelated to the specification/resource directoryRelated to the specification/resource directorytriage:accepted:readyReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsorReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
Type
Projects
Status
Spec - Closed
Status
Done