Josh Suereth

We briefly discussed this in 2025-02-27 Meeting. We see a few options going forward here: 1. Allow Go to violate spec for this 2. Allow 'empty id' entities where we...

TC Triage: This sentence should be clarified. There is enough information in this bug to denote the intent of that sentence and its importance in ensuring successful distributed context propagation....

So, do you have a way to still support the `testQuick` or test discovery use case? I think `testQuick` (incremental running of tests based on detected change) is pretty compelling...

It's sort of related. SO: 1. For testQuick, I'd like to try to isolate the "test needs to run" detection on a _test_ itself, not the entire class/source file. Remember...

@tigrannajaryan Optional attributes are OK, but there's a line here to pay attention to: > An instrumentation library should produce a consistent set of attributes for a given instrument. This...

> Is this nuance enforceable in practice? I feel that it is going to be tricky to both communicate this nuance in the spec clearly and as a developer it...

This LGTM once comments are addressed.

@braydonk - Can you get the @open-telemetry/semconv-system-approvers group to make a decision on this here? Regarding `cpu` vs `host.cpu` namespace, according to our new namespacing rules, `cpu` is reaosnably unique...

Unfortunately, this would be quite breaking. Although, I do think defaulting to UTF-8 would solve a lot of issues we have. The reality is we live in a weird ecosystem,...

We already specify that any non-valid UTF-8 string MUST be encoded as a bytes_value. I'm against the chaos that would ensue with forcing every string to be raw bytes with...