We should be clear what functionality works only with OpenTelemetry and either document it clearly or physically separate it in unique namespaces and assemblies. Today I see references in these assemblies:

I assume documentation will be less disruptive than refactoring, and I wouldn't object to it, but I do think it comes with some consequences:

1. Some dependency sensitive developers may avoid all functionality in these assemblies, even if the specific type or scenario they are interested never runs any OTel code.
2. Because of (1) there is now a tradeoff that needs to be considered when adding any new non-OTel specific functionality to the assembly. Implicitly in my head, these assemblies are currently 'OTel extension assemblies' and not 'general purpose telemetry assemblies'.
3. There is always a little extra risk of misuse/confusion if naming doesn't make the dependency obvious.