Josh Suereth

So far, most semconv maintainers I've heard from think that `.` vs. `_` has meaning in our model. We may want to discuss this all together on the maintainers call...

> One question though - should we enforce then a presence of this property for registry? Once we get the rule-engine/checker working in weaver, this is a simple configuration for...

@AlexanderWert Yes - I think that change (and propagation of its value) should be what you need to do in weaver. There's also a TemplateGroup: https://github.com/open-telemetry/weaver/blob/main/crates/weaver_forge/src/registry.rs#L29 Once you have Group...

Given the status of Entities WG and updates to semconv, this PR can now make progress and be submitted. It has the following: 1. A well defined resource "name" /...

I'm way late to the party, but I think we need to back out the resource-attribute portion of this change. See: https://github.com/open-telemetry/semantic-conventions/issues/1181#issuecomment-2229168814 for rationale. If I had caught this earlier...

Given activity happening in Entity SIG - I think it's best to "wait" on major changes to resource related attributes. My own opinion on this Pr is that: 1. Yes,...

My take here - We can give users flexibility in the Status Code -> Span Status mapping. However, at a macro level - 1. Server-side spans should only default failure...

This can move to semconv repository after https://github.com/open-telemetry/semantic-conventions/pull/1000 is merged.

Should be able to update: - https://github.com/open-telemetry/semantic-conventions/blob/main/templates/registry/markdown/attribute_table.j2 - https://github.com/open-telemetry/semantic-conventions/blob/main/templates/registry/markdown/attribute_namespace.md.j2 I think the later is the important one, as it gives us the ability to anchor-link to the attribute registry.

I think it's fair to leave the *registry* docs the same as they were and put the opt-out redaction as an augmented description for http semconv.