Robert Pająk

> @pellared how will we distinguish between instruments scopes if attributes are added. They are a non-identifying field, they cannot be used in comparisons. From spec > Tracers are identified...

> How does that resolve the questions quoted? It is adjusting definitions to include logs in instrumentation scope references. The questions already exist for all signal types that use instrument...

Thanks. I will try to refine the specification as part of my work for OTel Go Logs.

Unfortunately (for the users), OTel Go shares internal packages between modules which causes problems like described. Because of this, currently, OTel Go packages are compatible only between the versions that...

> what do you think about a policy of releasing a major version I do not think it is worth going that path. It would be a big burden for...

I think this issue can be split into at least 2 issues: 1. Remove the dependencies on the internal package of different modules (probably via code generation and documentation) 2....

I created a "parent" issue https://github.com/open-telemetry/opentelemetry-go/issues/3846 that could address this bug for future releases.

@sk- I think documenting [here](https://pkg.go.dev/go.opentelemetry.io/otel/sdk/metric) the acceptable and/or invalid arguments of the instrument factories would be helpful. Do you want to work on it?

@dmathieu PTAL

I saw https://github.com/open-telemetry/opentelemetry-go/issues/3548 and now I have concerns. This kind of refactoring may introduce the same problem in future if we do breaking changes in `go.opentelemetry.io/otel/internal/env`. Maybe we should use...