Update 0000-span-spec

text/0000-span-spec

@@ -4,6 +4,14 @@ Specifying the structure of trace and metric data in logs.
 
 ## Motivation
 
+
+Joshua MacDonald Jun 11 22:24
+HI all, I've been thinking about how this Logging sub-project could help more with tracing and metrics. I was thinking that before beginning to work on Logging API design, we could try to standardize the translation from Span and Metric events into structured logging events. This was requested as a feature for the metric SDK (open-telemetry/opentelemetry-specification#617), and I think the same could be said of spans. Right now many OTel repos are including standard-output exporters for both trace and metrics, but there are no standard conventional data formats for them to use, so it's a bit arbitrary what you get. I think it would be great if we had a standard structured log form for both metrics and spans.
+I would add that the OTel metrics API was conceived as a logging API from the start. The data model describes metric events, which can be recorded as a faithful way to capture metrics, so we would just need to standardize how they are structured as log records. Here's the event structure: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/metrics/api.md#metric-event-format
+
+
+https://github.com/open-telemetry/opentelemetry-specification/issues/617
+
 Why should we make this change? What new value would it bring? What use cases does it enable?
 
 ## Explanation