Alex Van Boxel

I've opened a **draft** PR https://github.com/open-telemetry/opentelemetry-specification/pull/3775 on the proposed clarifications. It would be great to have some involvement for Google contributors.

I think a new compatibility section is a great idea. Does this mean that all the sections in the datamodel-appendix would move to the compatibility section?

> Additionally, the new attributes defined should probably be defined and added to the [semantic-conventions](https://github.com/open-telemetry/semantic-conventions). I don't think I've added anything new. I've used the semcon that was available (except...

@jsuereth I've moved it in the branch to the compatibility section

@jack-berg and @jsuereth doesn't it make sense to have a compatibility section in the logs directory itself and that all model-appendix move (one by one) to that directory?

Would you consider OpenAPI spec also as RPC metrics? This is because we're doing reverse mapping from Envoy Logs to OpenAPI metrics using the RPC semantics, with `operationId` as the...

The [OpenAPI](https://swagger.io/specification/) specification defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source...

I will; I'm slowly working myself in and plan to start joining the SIG meetings.

I've neglected some of my OpenTelemetry work for the last few months. I will refocus some of my time back on open source. I will pick it back up, including...

I can add the mapping in the collector README, but I feel the documentation should be either in spec/compatibility or either semconv/compatibiltity.