STDOUT exporter format is unspecified

CHANGELOG.md

@@ -13,12 +13,21 @@ release.
 
 ### Traces
 
+- Clarify STDOUT exporter format is unspecified.
+  ([#3935](https://github.com/open-telemetry/opentelemetry-specification/pull/3935))
+- Recommend documentation of the STDOUT exporter format.
+  ([#3935](https://github.com/open-telemetry/opentelemetry-specification/pull/3935))
+
 ### Metrics
 
 - Remove implementation specific specification from metric API.
   ([#3890](https://github.com/open-telemetry/opentelemetry-specification/pull/3890))
 - Formalize the interaction between cardinality limit and overflow attribute.
   ([#3912](https://github.com/open-telemetry/opentelemetry-specification/pull/3912))
+- Clarify STDOUT exporter format is unspecified.
+  ([#3935](https://github.com/open-telemetry/opentelemetry-specification/pull/3935))
+- Recommend documentation of the STDOUT exporter format.
+  ([#3935](https://github.com/open-telemetry/opentelemetry-specification/pull/3935))
 
 ### Logs
 
@@ -28,6 +37,10 @@ release.
   ([#3852](https://github.com/open-telemetry/opentelemetry-specification/pull/3852))
 - Add support for empty values.
   ([#3853](https://github.com/open-telemetry/opentelemetry-specification/pull/3853))
+- Clarify STDOUT exporter format is unspecified.
+  ([#3935](https://github.com/open-telemetry/opentelemetry-specification/pull/3935))
+- Require documentation of the STDOUT exporter format.
+  ([#3935](https://github.com/open-telemetry/opentelemetry-specification/pull/3935))
 
 ### Resource
 

specification/logs/sdk_exporters/stdout.md

@@ -10,6 +10,11 @@ linkTitle: Stdout
 Exporter](../sdk.md#logrecordexporter) which outputs the logs to
 stdout/console.
 
+The output format of the exporter is unspecified. The exporter MUST be
+documented that its output is not a standardized format across OpenTelemetry
+nor is it a stable format. The documentation SHOULD suggest the OTLP exporter
+for users that want a stable and standarized output format.
+
 [OpenTelemetry SDK](../../overview.md#sdk) authors MAY choose the best idiomatic
 name for their language. For example, ConsoleExporter, StdoutExporter,
 StreamExporter, etc.

specification/metrics/sdk_exporters/stdout.md

@@ -10,6 +10,11 @@ linkTitle: Stdout
 Exporter](../sdk.md#push-metric-exporter) which outputs the metrics to
 stdout/console.
 
+The output format of the exporter is unspecified. The exporter SHOULD be
+documented that its output is not a standardized format across OpenTelemetry
+nor is it a stable format. The documentation SHOULD suggest the OTLP exporter
+for users that want a stable and standarized output format.
+
 [OpenTelemetry SDK](../../overview.md#sdk) authors MAY choose the best idiomatic
 name for their language. For example, ConsoleExporter, StdoutExporter,
 StreamExporter, etc.

specification/trace/sdk_exporters/stdout.md

@@ -10,6 +10,11 @@ linkTitle: Stdout
 Exporter](../sdk.md#span-exporter) which outputs the spans to
 stdout/console.
 
+The output format of the exporter is unspecified. The exporter SHOULD be
+documented that its output is not a standardized format across OpenTelemetry
+nor is it a stable format. The documentation SHOULD suggest the OTLP exporter
+for users that want a stable and standarized output format.
+
 [OpenTelemetry SDK](../../overview.md#sdk) authors MAY choose the best idiomatic
 name for their language. For example, ConsoleExporter, StdoutExporter,
 StreamExporter, LoggingExporter etc.