Robert Pająk

@XSAM, please use a newer version of the spec when checking the compliance. There has been important changes since the issue was created.

SIG meeting notes: AI @XSAM: Clarify the specification so that the following is in SDK spec and not the API spec: > If unspecified the implementation SHOULD set it equal...

Closing as https://github.com/open-telemetry/opentelemetry-specification/issues/4481 is also resolved.

Reopening as the signature for `Enabled` is changing: https://github.com/open-telemetry/opentelemetry-go/pull/6825

I think after we land https://github.com/open-telemetry/opentelemetry-go/issues/7034 this audit compliance should be redone. Therefore, marking it as blocked.

What about standard error and and file as output destinations?

@martinjt, what about people following https://12factor.net/logs? > A twelve-factor app never concerns itself with routing or storage of its output stream. It should not attempt to write to or manage...

> Pushing to a file is a very different idea, and has different usecases like offline access I agree with you. However, notice that sending to `stdout` is not against...

> @pellared We already have file exporting, that's the otlp file exporter. This is about stdout rather than files. If someone want's file we support that, just not via piping...

https://github.com/open-telemetry/opentelemetry-specification/issues/3817 status has been changed to accepted by @open-telemetry/technical-committee based on community feedback. Therefore, I think we can continue reviewing this PR.