@jsuereth I'm fine keeping it open, I don't think it's necessary though:

The only change from what we recommend today is to stop recording handled exceptions and stop reporting exception.escaped attribute. AFAIK OTel instrumentations in general don't report handled exceptions anyway.

The exception.escaped attribute has even lower risk:

• Java does not use it in core repo, does not set it in -instrumentation or -contrib
• .NET does not use it, not used in the contrib either
• JS does not use it, also not used in the js-contrib
• Python sets this attribute, but incorrectly (always to string "False" and there is nothing that ever calls this method in contrib providing this flag)
• Go does not set it for obvious reasons
• I don't see any mention beyond definition in C++ (core or contrib) or in Rust.

So I think the guidance just catches up with existing practice and vendors don't need to change anything. I'll announce it at the Maintainers call on Mon 1/13 and Spec call on 1/14 to make sure everyone is aware.

Unless there is some pushback, I'm going to merge it on ~1/15.