Resource Semantic Convention Stabilization Issues

[jsuereth]

Area(s)

area:other

What happened?

Description

Resource semantic convention stabilization is not in the model. If you look at https://github.com/open-telemetry/semantic-conventions/blob/main/model/resource/service.yaml - It is not marked as stable.

However, if you look in the markdown: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/resource/README.md#service it is marked as stable.

Additionally, we have an odd section added that somehow stabilizes version attributes without defining them: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/resource/README.md#version-attributes

Given the progress in the Entities WG - I'd like to propose the following:

• We stabilize service group as is.
• We move telemetry resource group to telemetry.sdk and stabilize the YAML group.
• Any actions/updates performed by Entities + Resource WG will need to pull along these stable groups.
• An updated to backwards compatibility requirements to guarantee stable attribtues are not removed from these stable resource groups.

Give the state of open-telemetry/oteps#264 and direction of the group - I think we can agree we already have telemetry.sdk and service as stabilized "entities" or "resource groups". What we do NOT have is programatic access to that stability for rule enforcement, break detection, etc. Let's fix that.

Semantic convention version

v1.27.0

Additional context

No response