It's not clear if these should be pulled in, or if client.* and server.* effectively replace them.
One tangential concern is that currently HTTP messaging semconv has attributes under messaging.source.* and messaging.destination.*, which would conflict if we also adopt the concept from ECS of nested namespaces.
cc @AlexanderWert
It's not clear if these should be pulled in, or if
client.*andserver.*effectively replace them.One tangential concern is that currently HTTP messaging semconv has attributes under
messaging.source.*andmessaging.destination.*, which would conflict if we also adopt the concept from ECS of nested namespaces.cc @AlexanderWert