* Use MUST consistently instead of shall.
* Update specification/trace/semantic_conventions/messaging.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Adapt messaging semantic conventions to include the operation in the span name
* Specify that the operation name must match the respective attribute if the suggested span name format is used
* Update span names in examples
* Consolidate definition of operation names into a separate section
* Consolidate capitalization
* Reference Conversation ID definition
* Consolidate MD syntax
* Organize definitions
* Organize definitions
* Reference definitions
* Allow artificial destinations as span name if neither destination name nor conversation ID are suitable
* Do not use conversation IDs for span name
* Wording
Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com>
* Fix typo
* Add more links and guidance on messaging.operation
* Fix changelog
Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com>
I'm not sure what this should have to do with vendors, according to the examples, this would be the actual system names themselves. Otherwise the vendor for kafka would probably be "Apache", for example.
Reiley Yang