Robert Pająk

> Hi, dear guys, I'm extremely interested in this feature lately. And I'm familiar with go programming but not very familiar with opentelemetry. Is there any thing I can do...

Logs API is implemented. Closing. The prototype may still be helpful in future (e.g. when implementing bridges).

> I'm not sure this is necessary. The `~` should already make us use the latest patch release within the specified minor. And we even additionally have `check-latest: true`

Blocked by https://github.com/open-telemetry/community/issues/1926

> This however, would be a breaking change, so we should discuss our options, and it might be better for now just to leave them as camel case. We could...

I think we can start with option 2 and work on 4 concurrently so that we can use the new feature when we will be generating `semconv/v1.25.0`.

@open-telemetry/go-approvers PTAL

The main use case of using `resource.NewSchemaless` is when the attributes do not even follow the semantic conventions (when one adds custom attributes).

I agree especially that https://pkg.go.dev/go.opentelemetry.io/otel/sdk/resource#example-New even shows how one can handle the conflict

Changing to draft after getting some very constructive feedback from @MrAlias. Basically it is about making the design doc more readable for non-maintainers. E.g. calling out some design decisions more...