Go semver seems not be consistant with otel semver spec

[aygalinc]

Go semver seems not be consistant with otel semver spec

[MrAlias]

@aygalinc heads up, the semconv package linked from open-telemetry/opentelemetry-collector-contrib#31255 is not the same as https://pkg.go.dev/go.opentelemetry.io/otel/semconv

[aygalinc]

Discover with : open-telemetry/opentelemetry-collector-contrib#31255

[MrAlias]

Can you please provide specifics of your issue? What semantic conventions are you missing?

We generated v1.21.0 using the v1.21.0 version of semantic conventions. There shouldn't be anything missing.

[aygalinc]

By semantic conv i refer to : https://opentelemetry.io/docs/specs/semconv/http/http-spans/ .
It seems thatsome part of the info can be fined inl : https://github.com/open-telemetry/semantic-conventions/blob/main/model/http-common.yaml (the http.response.status_code for example) and specific tracing part in https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/http.yaml .

If i look the several code generation at some point the directory http and net start to deasepear in the opentelemtry-go repo.
Maybe reference model used by your generator have been moved.

I am not a go developer but happy to help if i can do something to restore this.

[MrAlias]

The evolution of semantic conventions is managed here: https://github.com/open-telemetry/semantic-conventions

They have made breaking changes in many of their subsequent releases. We package release version within their own Go package. Please refer to the appropriate semconv package that contains the things you need.

[MrAlias]

I'm going to close this as it seems like the issue here is a misunderstanding about the upstream semantic convention stability policy and how that is implemented in the Go project.

If you find an issue where one of our semconv packages does not contain a semconv value from the upstream repository please open a new issue targeted at that value.

[aygalinc]

Oh sorry i Mixed the packagé when i navigate