What are you trying to achieve?

Clarify the definition of a Resource to explicitly account for auto-instrumentation (e.g., eBPF agents like OBI, Mermin, etc).

The current specification defines a Resource as a "representation of the entity producing telemetry." This is ambiguous when an observer/agent is producing telemetry on behalf of an observed service. I expect the specification to clarify that the Resource describes the observed entity (the service/process), not the technical producer (the agent).

Additional context.

In eBPF-based "auto-instrumentation," the agent technically produces the telemetry, but the Resource attributes describe the shimmed workload. This ambiguity makes it difficult to correctly apply semantic conventions like telemetry.sdk.name and telemetry.distro.name, as it's unclear if the "Resource" is the agent itself or the service it's watching.

Relevant documentation:

• https://opentelemetry.io/docs/specs/otel/resource/
• https://opentelemetry.io/docs/specs/semconv/registry/attributes/telemetry/