Alexander Wert

> @AlexanderWert are you able to continue this work, or should one of us take over? I'll update the PR with your proposal

@joaopgrassi updated this PR I think we need both releasing and updating the weaver version AND build tools, right?

@joaopgrassi @lmolkova @lquerel Updated my PR. PTAL, I also changed the order of the generated groups to make sure deprecated attributes are always listed at the end (instead of pure...

@lmolkova The compatibility check still fails. That has been actually fixed in these PRs, but we did not have a build-tools release since then: https://github.com/open-telemetry/build-tools/pulls?q=is%3Apr+display_name+is%3Aclosed So, I guess we need...

@christos68k please do the change in the corresponding yaml file: https://github.com/open-telemetry/semantic-conventions/blob/ed7d3e0f939cbdcd6c0b6093d157d3f5e8bbc9bd/model/registry/host.yaml#L8 The tables in markdown files are generated from the model yaml files. So once you did the change in...

@open-telemetry/semconv-system-approvers @open-telemetry/semconv-container-approvers PTAL

> Looking into https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime, we'd make some breaking change if we attempted to make them consistent with general semantic conventions requirements: > > * metrics would be renamed (`process.runtime.dotnet.*` ->...

I like the proposal, it simplifies things. @lmolkova Can we limit the valid values of an attribute when used in a concrete context to a subset of the overall allowed...

@bripkens Good point! Actually there are many more namespaces still missing in the registry. I extended the description of this issue above to list all the missing namespaces I found.

I like the proposal! We need to have meaningful guidelines on the following though: - When to split into sub-groups (which also implies sub-sections in the corresponding registry readme) vs....